Home > IT Answers > Windows Server > Windows 2008 Server R2 and XP Clients don’t have Internet access
10011001101
15 pts.
 Windows 2008 Server R2 and XP Clients don’t have Internet access
Active Directory, D-Link DIR-655, DHCP, DNS, Domain Controller, Networking, Windows Server 2008 R2, Windows XP clients, Windows XP Professional SP2
I have a Windows 2008 r2 server w/AD, DNS & DHCP configured. The gateway is a D-Link DIR-655 w/DHCP disabled. The server has internet access, but authenticated XP clients don't. How to fix this? Dcdiag /test:dns /e /v test passed Server is Windows 2008 r2 -Server NIC set to Local DNS -Server has internet access -Local domain forwarders verified to ISP’s DNS Clients are Win XP Pro SP2 -Clients do not have internet access -Windows firewall enabled (no other firewall exists) -No Antivirus or security software enabled -Clients can ping DNS (127.0.0.1) -Clients can ping server IP (192.168.0.100) -Clients can ping gateway (192.168.0.1) -Clients can authenticate to AD & DHCP -Clients can see and write to file shares setup in AD Share



Software/Hardware used:
Windows 2008 r2
ASKED: June 23, 2010  8:29 PM
UPDATED: June 25, 2010  10:46 PM
RELATED QUESTIONS
Answer Wiki:
Pinging 127.0.0.1 only confirms it can ping itself not dns. ping tests just confirms it's able to talk to the other devices on the network. On your XP machine go the command line and type this: nslookup You should get something like: Default Server: name_dns_server_fully_qualified_domain_name Address: 192.168.0.100 now type: www.google.com What is your response? If you don't get the message above and something like server or you error out try this server=4.2.2.2 now type: www.google.com If this works, this means that your dhcp server may not be providing dhcp settings. Check your dhcp settings and confirm they are provided the local server for DNS settings. Your server should be providing as a dns settings as 192.168.0.100 and not 127.0.0.1 to your clients. On the server itself, it would be pointing to itself via ip 127.0.0.1 or better use 192.168.0.100.
Last Wiki Answer Submitted:  June 24, 2010  7:48 pm  by  Aguacer0   8,120 pts.
All Answer Wiki Contributors:  Aguacer0   8,120 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

Also, to check if the problem is DNS-related, from one of the clients try navigating to google using the ip address instead of the URL (ping http://www.google.com from your server, and use the resolved ip address to navigate from the client).

carlosdl
 63,535 pts.
 

Thanks!

I was receiving a server unknown message with nslookup and no response from server using 4.2.2.2 reference, so re-checked settings in DHCP server. Main server settings ok, but found one of the scopes had a DNS entry for 127.0.0.1 instead of 192.168.0.100.

Simple as that – it was fixed.

Thanks all!

10011001101
 15 pts.