Dear Administrators,
My query is very simple I've a connection of cable net which consist on domain controller I want share on my home network, I've already installed two Ethernet LAN cards, if possible then tell me in steps.
The following Device are available.

1. SYSLINK Switch 2. 2 Ethernet LAN card 3. Two home Client computers.

Cable net sever configuration.

IP:
Subnet:
DNS: Acer Host: LINKSYS

Home network configuration.
Home Server (which connected to Cable internet)

IP: Subnet:
Name: Client Server

Home Network Clients.
Subnet:
Name: Client1

Subnet:
Name: Client2

If you have any solution of my problem then kindly tell me you can also contact on my email address. .

Thanks for genius.

Dani AI

Generated

Practical, low-risk approach for ' topology: treat the domain controller as the internal DNS/DHCP/AD server and put a NAT device (either the server acting as NAT or, preferably, a small hardware router) between the cable side and the 10.0.0.0/24 LAN. Internet Connection Sharing (the Microsoft KB referenced by ) will work for tiny, non‑domain setups, but running ICS on a domain controller is fragile and can introduce DNS/DHCP conflicts. Prefer RRAS (Windows Server) or a dedicated router.

Recommended configuration (concise):

  • Identify NICs: “External” = link to the Linksys/cable gateway; “Internal” = link to the SYSLINK switch and clients.
  • Assign static addresses:
    External NIC: 192.168.0.2/24, Gateway: 192.168.0.1
    Internal NIC: 10.0.0.1/24, no default gateway
    Clients: 10.0.0.2–.3/24, Gateway: 10.0.0.1, DNS: 10.0.0.1
  • Server DNS/DHCP: make the DC’s primary DNS point to itself (10.0.0.1). Configure DNS forwarders on the DC to the ISP or a public resolver so external names resolve. If DHCP is used, set scope options to hand out 10.0.0.1 as gateway and DNS.

Services and software:

  • On Windows Server, enable RRAS and configure NAT on the External interface and mark the Internal interface as private. RRAS preserves AD/DNS behavior and is preferable to ICS for domain controllers.
  • If RRAS is unavailable and a router is not an option, ICS can be used as a last resort—expect the internal NIC to be reconfigured and watch for conflicts.

Quick checks and troubleshooting:

  • From the server: ipconfig /all, ping 8.8.8.8, and nslookup microsoft.com to confirm routing then name resolution.
  • From a client: ping the internal gateway (10.0.0.1), then 8.8.8.8, then a hostname. Common faults: wrong gateway on NIC, duplicate IPs, DNS on clients pointing to ISP (breaking AD name resolution).
    Security note: avoid exposing the DC directly to the internet. A hardware firewall/router between the cable modem and the DC is the safest, simplest long‑term fix.

The post by about bad sectors is unrelated to this thread.

Recommended Answers

All 2 Replies

I responded to this question on the 11th. It seemed from your first post that you did not want your home pcs to be able to access your other workgroup computers. Please don't repost the same question without responding to suggestions already given. If all you want is instructions on how to configure Internet Connection Sharing here is the whole thing from Microsoft.

Dear Friends,
Plz guide me about removing bad sector from partation.

regards;-
Ankush .A. Wagh.
Mo.9922329372.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.