Windows 2003 cannot connect to Internet
We have a Windows 2003 Server which has been running fine but seems to have lost its connection to the Internet. We can ping or browse to any LAN connection without an issue. It is also resolving DNS names fine.
So far, we have turned off the anti-virus, disabled the Firewall, downloaded and installed all the latest Microsoft patches and rebooted the machine several times to no avail.
Any help here would be greatly appreciated. We're at a loss on this one.
So far, we have turned off the anti-virus, disabled the Firewall, downloaded and installed all the latest Microsoft patches and rebooted the machine several times to no avail.
Any help here would be greatly appreciated. We're at a loss on this one.
ASKER
We did that last week before we were having this problem and, as a matter of practice, we always test all connectivity after doing so. This tells us that recently downloaded/installed patches are not the problem.
Make sure you proxy settings are off if you don't need it.
Control Panel - Internet options - Connection tab - LAN settings.
Control Panel - Internet options - Connection tab - LAN settings.
can you ping the gateway?
if so, can you do a trace route to 8.8.8.8 ?
if so, can you do a trace route to 8.8.8.8 ?
ASKER
Proxy settings are turned off; Internet Explorer Enhanced Security Configuration is not installed; have tried Firefox; can ping any IP on the LAN including the gateway with no issues. Tracert shows the following results:
U:\>tracert 8.8.8.8
Tracing route to google-public-dns-a.google
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms 50-196-70-198-static.hfc.c
.196.70.198]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
U:\>tracert 8.8.8.8
Tracing route to google-public-dns-a.google
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms 50-196-70-198-static.hfc.c
.196.70.198]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
ASKER
Another note: We have Logmein installed on this computer for remote access which has stopped working as well but we can connect remotely through an RDP connection.
can any machine get internet access?
have you tried power cycling your comcast modem?
once in a great while i have connection issues with comcast but after rebooting the modem it's fine
have you tried power cycling your comcast modem?
once in a great while i have connection issues with comcast but after rebooting the modem it's fine
ASKER
Yes, the Comcast modem has been power-cycled twice. There are 22 other computers in our environment, including our domain controller, and none of them are experiencing this problem.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Unbelievable! Changing the IP address worked. Never looked at the simple solution. Thank you for your help Seth... this has been driving us nuts!
how did you do this if you don't have internet access?