anujgaur_88 0 Newbie Poster

sir i have manage a new windows server 2003 standard...i m accessing internet connection on mi domain controller but mi clients r not able to access it......i hav configure active directory ,,dns,,dhcp all,and one thing more in dhcp server wht ip shoud i give to router.....
1 the ip that is selected for dns server.
2 the ip that is public ip provided by isp


waiting 4 ur reply
anuj gaur
mcse ,ccna
network administrator
email id: <snip>
india

Dani AI

Generated

For : short practical answer first, then checks you can run.

  • DHCP should hand clients a private LAN gateway (the router's LAN IP on the same subnet), not the ISP public address. Clients use that LAN gateway to reach the internet; a public IP as the "router" option will not work from the LAN.
  • Point clients at the domain controller for DNS (DHCP option for DNS = DC IP). On the DC's DNS server configure forwarders to your ISP or a public resolver so external names are resolved.
  • Only set the DHCP gateway to the DC if the DC itself is providing NAT (RRAS/ICS). Running NAT on a domain controller is possible but not recommended for security and reliability reasons — a dedicated router/firewall is better.

Quick setup checklist

  • DC: give a static private IP and register it as the DNS server for the domain.
  • Router: WAN gets the ISP public IP; LAN gets a private IP (example 192.168.1.1). Enable NAT on the router.
  • DHCP scope: lease private addresses, set Router (default gateway) = router LAN IP, DNS = DC IP.
  • On DC DNS: configure forwarders to ISP DNS or public DNS (eg, 8.8.8.8).

Troubleshooting commands to run on a client

ipconfig /all
ping <gateway>
ping 8.8.8.8
nslookup www.google.com

Reference for private addressing and NAT basics: RFC 1918 and an overview of NAT concepts from .

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.