Server 2008 R2 Windows XP client cannot access internet

[JonathanMortimer]

I have a Server 2008 R2 machine set up as the domain controller, it can access the internet through our draytec router fine, as can the other Server 2008 R2 machine which is joined to the domain.

A Windows XP client PC (which is joined to the domain) cannot access the internet, it's like there is no path from the client to the gateway, although in ipconfig it shows the gateway IP correctly, but the client cannot ping the gateway or

http://www.google.co.uk

(either by name or IP).

Any ideas what's going on here? I've also tried connecting an Ubuntu client but this gave the same results, tracerout didn't manage to leave the client.

 

[kmcferrin]

If tracert doesn't get past the client then the problem is on the client. What's the IPCONFIG /ALL look like? The default gateway may be configured correctly, but if the subnet mask is wrong then it may not be able to get there.

I'm assuming that you can ping the loopback address (127.0.0.1)?

________________________________________
CompTIA A+, Network+, Server+, Security+
MCTS:Windows 7
MCTS:Hyper-V
MCTS:System Center Virtual Machine Manager
MCTS:Windows Server 2008 R2, Server Virtualization
MCSE:Security 2003
MCITP:Enterprise Administrator

 

[JonathanMortimer]

Yes, loopback pings OK. Both client PCs I've tried previously worked normally when attached to another network, the Windows XP Pro client has been joined to the domain, the Ubuntu one was not (for obvious reasons) but still picked up the gateway correctly.

 

[NetworkTek]

Can you ping your gateway or anything else on the local subnet?

Network+ Inet+ MCP MCSA 2k3

 

[JonathanMortimer]

Last time I tried, no, could not ping the gateway, can't remember if I could ping the domain controller (I'm at a different site today, going to pick up on it again next week). It's confusing me now as the machine logs into the domain using a domain account, there is no 'offline files' icon in the notification area and I can remote desktop to the domain controller from this client PC.

 

[JonathanMortimer]

We are going to flatten the server next week anyway so we'll see if it's any better after that. Several attempts at installing Exchange 2010 on another server in this test domain has corrupted the Active Directory, which might explain the client problems.

 

[JonathanMortimer]

Hmm. Fresh installation of Server 2008 R2 with DNS, DHCP, and Active Directory roles installed and configured, but the XP client cannot browse the internet. It can ping the new 2008 R2 domain controller but not the gateway. The 2008 R2 server can browse the internet fine and ping the gateway.

ipconfig /all looks exactly as it should (compared to a normal working domain machine on another network) with Default Gateway etc filled in and correct.

Is there something extra that needs configuring to allow XP clients access to the internet? Thanks for any help on this!

 

[JonathanMortimer]

Btw the client has been successfully joined to the 2008 R2 domain. Also ipconfig shows DNS servers correctly (they are set to be the domain controller IP address, it should forward DNS requests as required to the router, this is how Server 2003 works at least).

 

[kmcferrin]

Nope. Your 2008 R2 server shouldn't affect the client's ability to get to the Internet unless it is configured as the router or proxy.

Do an IPCONFIG /ALL on the client. Verify that it has an IP address, subnet mask, and default gateway that are correct for the network. Verify that it has valid addresses listed for the DNS server.

Try an NSLOOKUP on

http://www.microsoft.com

or some other site from the XP client. Can it resolve correctly?

Then trying doing a tracert to that same site. You won't get pings back all the way through, but you will probably be able to get pings for the parts of your network that the traffic traverses.

Is there a software firewall turned on that could be blocking access?

Is there a configuration on the router that is blocking access to the IP address or IP address range that the XP workstation is using?

Is there a proxy server that other workstations are using that this workstation is not using?

________________________________________
CompTIA A+, Network+, Server+, Security+
MCTS:Windows 7
MCTS:Hyper-V
MCTS:System Center Virtual Machine Manager
MCTS:Windows Server 2008 R2, Server Virtualization
MCSE:Security 2003
MCITP:Server Administrator
MCITP:Enterprise Administrator