HELP NEEDED >> Windows XP Box Not Connecting to Internet

[pradeep1]

Hello guys,

I need your help. I recently built a C2D system and installed Windows XP on it and it was working fine, but yesterday, it stopped being able to connect to the Internet.

Here is my setup:

Comcast Cable Modem Service - Motorola Surfboard Modem
Linksys BEFSR41 wired router
Three computers hooked up to this router:

1. Windows 2000 Primary Workstation
2. Windows 2000 Secondary Workstation
3. Windows XP Core 2 Duo new build

All three machines were connecting to the Internet fine until yesterday, when the XP box suddenly stopped connecting to the Internet. The Win2K machines are networked together using a simple networking protocol (NetBUI) through the router. The XP box in not on the network, but was just using the internet connection.

So on to the XP box, I've tried the following:

1. Checked the NIC card (built into the mobo) and it seems fine. I reinstalled the drivers for it, and also installed another NIC card and tried to connect and it couldn't.

2. Checked to see if any stupid firewall was holding me up - Windows SP2 firewall is disabled and Zonealarm is working as normal.

3. I reset the modem, router, etc. to no avail. I rearranged the order of connection into the back of the router and no matter what I do, the Windows 2000 boxes connect, but the XP box doesn't.

4. I plugged the XP box directly into the cable modem bypassing the router, and same problem.

5. I went into the network properties and noticed that it is pulling nothing up for IP address, etc. When I checked local area connection status, nothing shows for the IP Address, Subnet Mask, Default Gateway. When I hit the "repair" button to rebuild the connection, it errors out and tells me that it "failed to query TCP/IP settings" of the connection and that it cannot proceed.

6. Tried to run ipconfig to see something, and nothing pulled up. Ipconfig just says something like "Windows IP Configuration" and stops. Ping doesn't work either.

7. Called Comcast tech support, and they told me to update the router's firmware (I don't think that is even possible, I've been using this same router since 2002 and it has served me well with a mix of computers over the years). Their final advice was to reinstall XP, go figure.

I hope there is something very simple that I am overlooking that one of you whizzes can help me find and correct.

Thanks in advance.

Pradeep

 

[sonoma1993]

try using a different Ethernet cable.

 

[JackMDS]

Try to disable ZA.

Otherwise, http://www.ezlan.net/debug.html

 

[pradeep1]

Originally posted by: sonoma1993
try using a different Ethernet cable.

Tried that, plugged it into the cable used by one of the Win2K boxes and it still doesn't work.

 

[pradeep1]

Originally posted by: JackMDS
Try to disable ZA.

Otherwise, http://www.ezlan.net/debug.html

Disabled ZA and tried, but no go. I'll look over the link and let you know what I find out.

Thanks,

Pradeep

 

[bruceb]

Google for WinsockfixXP .. usually at MajorGeeks
Run it ... that should resolve the issue

 

[phatrabt]

Try turning on and off the blocker for ZA. If that doesn't work, try uninstalling ZA. I've seen reports around the web of problems with ZA and even turning it off doesn't fix it, only an uninstall and reinstall.

 

[pradeep1]

I tried the following:

1. Uninstalled Zonealaram and tried to connect - no go.
2. Reinstalled ZA.
3. Ran WinSockFix - no go.
4. Ran LSP-Fix - says there are no problems
5. If I ping 127.0.0.1, I get response, so TCP/IP stack should be installed
properly and should be okay.

I am now working through manually resetting the Internet Protocol and other stuff:

http://support.microsoft.com/?kbid=299357
http://support.microsoft.com/kb/314067/
http://support.microsoft.com/kb/811259/

This sucks and I am getting frustrated. This problem should be easy to solve.

Pradeep

 

[pradeep1]

A few more factoids...

1. I have a 56k modem installed and it is on IRQ-19, my ethernet card on IRQ-23.

2. I cannot access the Linksys router configuration page by pointing the browser
of any computer on the network to http://192.168.1.1/

 

[pradeep1]

I manually did as much as I could using the Microsoft support links posted earlier to no avail. Computer still is dead in terms of connecting to the Internet.

Damn it! I don't want to re-install Windows XP after spending 20 hours on the bench getting it setup and configured.

 

[ChAoTiCpInOy]

Are you sure the connection properties have TCP/IP installed?

 

[pradeep1]

Originally posted by: ChAoTiCpInOy
Are you sure the connection properties have TCP/IP installed?

I pulled these pics from another site, but I too have the "Internet Protocol TCP/IP" installed and check.

http://www.ezlan.net/example/tcp.jpg

http://www.ezlan.net/example/tcp-ip.jpg

Recall, this computer was working fine and all was good for three days after I built it.

I am now thinking that maybe some overzealous anti-spyware program might have messed up my XP box. One of the Win2K workstations had some stupid spyware/trojan infection and it was cleaned up. Just to be cautious, I scanned this computer overnight on Friday running Spyware Blaster, Adaware, SUPERAntispyware, and Spyware Terminator. I don't recall exactly when, but sometime after those scans, I think my internet went dark.

Hmmm....Even if I disable all those programs and try to access the internet, no avail.

I also downloaded the update ethernet drivers from the mobo manufacturer's website and update those and that didn't do anything. My NIC is showing as working fine and operational. In the network connection setting, it says that I am connected to the LAN at 100 MB/s or whatever.

 

[Fardringle]

Assign a static IP address on the XP machine that matches the address information on the Win2K machines (same default gateway and DNS servers, same IP range but change the last number to an unused address) and see what happens then. You could also skip the NetBEUI test and just assign a static IP first if you want to.

If the XP machine can access the Internet with a static IP address then the networking protocols are fine and you are likely dealing with a DHCP problem. Check to make sure the DHCP Client service is running (Start>Run>Services.msc). I have seen a few spyware programs that will disable or otherwise interfere with this service.

If the computer cannot access the Internet with a valid static IP address, install NetBEUI on the XP machine and give it the same workgroup name as the Win2K machines to see if it can see the other computers on the network. This won't resolve the issue, but it will help verify whether or not the network adapter in the XP machine is actually working.

 

[pradeep1]

Originally posted by: Fardringle
Assign a static IP address on the XP machine that matches the address information on the Win2K machines (same default gateway and DNS servers, same IP range but change the last number to an unused address) and see what happens then. You could also skip the NetBEUI test and just assign a static IP first if you want to.

If the XP machine can access the Internet with a static IP address then the networking protocols are fine and you are likely dealing with a DHCP problem. Check to make sure the DHCP Client service is running (Start>Run>Services.msc). I have seen a few spyware programs that will disable or otherwise interfere with this service.

If the computer cannot access the Internet with a valid static IP address, install NetBEUI on the XP machine and give it the same workgroup name as the Win2K machines to see if it can see the other computers on the network. This won't resolve the issue, but it will help verify whether or not the network adapter in the XP machine is actually working.

Fardringle,

Thanks for the useful info.

Okay, I manually set the TCP/IP properties and assigned a static IP address (with last number changed), DNS Gateways, subnet mask, etc. Rebooted. No go. Ipconfig would not show anything being pulled.

Then I checked to make DHCP was working, and it was running. I restarted it just to make sure. No go.

I then installed NetBEUI on the XP box, and it can see both my Win2K machines just fine, but still no internet access.

So far, we know that the network card is working, the router is working, the cable modem is working, and that the ISP service is up and running. Just my computer config is f*cked up somewhere.

What could possibly be wrong? This is too weird. I've been fooling with computers since 1981 and have dealt with network issues since the first networks I saw back in 1993. This is the first time I have not been able to diagnose a network problem in like 5 minutes and get on with my life.

 

[bruceb]

Try flushing the DNS and also do a Release of your IP
and then a Renew of the IP from the DHCP Server

From the command prompt: ipconfig /flushdns

ipconfig /release .. then ipconfig /renew

 

[pradeep1]

Originally posted by: bruceb
Try flushing the DNS and also do a Release of your IP
and then a Renew of the IP from the DHCP Server

From the command prompt: ipconfig /flushdns

ipconfig /release .. then ipconfig /renew

I did all three. It did not resolve this problem.

Seems like ipconfig on this machine is not running properly.

Whenever I type anything ipconfig, all it does is display this line:

Windows IP Configuration

and then it comes back to the command prompt without showing any other information.

I also ran ipconfig /registerdns and /displaydns and it gives me the same line as above with no further information.


XP has an utility built in that will scan the computer and pull up all the network info. I remember it was mentioned in one of the MS Articles. I am wondering if I cannot post that log for you guys to look at.

Pradeep

 

[pradeep1]

I was reading through the MS documents referenced earlier and was playing around with ping.

If I ping 127.0.0.1, then I get a loopback.

If I ping the Default Gateway - no response
If I ping the DNS Servers - no response
If I ping a remote server - no response

MS says that if the default gateway cannot be pinged, then there is some problem with the network adapter, the router or gateway device, the cabling, or other connectivity hardware.

We've confirmed the network adapter is okay, the router is okay (since other computers are using it okay), the cabling is not a problem since I've used different cables. What other connectivity hardware is there I can test?

Is it possible that the network card is having some other problem, in that, it could be connecting to the other computers using NetBIEU, but screwing up with the TCP/IP?

Oh, I installed another Linksys BEFSR41 router and tested all the computers again, and same results. The Win2K boxes connect, the XP box doesn't.

 

[pradeep1]

I went back to basics...

I reinstalled Windows Service Pack 2, thinking that would reset something - no go

I installed new NIC card and manufacturer's drivers - no go

I installed new CAT5 cable between computer and router - no go


Aside from reinstalling Windows outright, I don't know what else to do?

 

[bruceb]

Only thing left is to run a Repair Install of Windows .... you should not lose any personal
data if you do a repair the proper way .. this link tells how

http://www.michaelstevenstech.com/XPrepairinstall.htm

Also, did you run a Virus & Antispy scan in Safe Mode ? ? .. Perhaps something got in

 

[pradeep1]

Thank you everyone for your help and time. After spending too many hours in frustration, I decided to try the reinstall option as bruceb suggested, but it did not work. There were some disk corruption errors and a few of the critical files did not make it properly, so I just wiped the entire disk and reinstalled Windows XP.

Bad news is that, good news is that it now connects to the Internet without any problems.

Thank you once again.

Pradeep

 

[zagood]

Stories like this that give you a reason to image your working config. Guess I should open that TrueImage box that's been sitting around.

Rough experience, glad it worked out for you!

-z

 

[pradeep1]

Originally posted by: zagood
Stories like this that give you a reason to image your working config. Guess I should open that TrueImage box that's been sitting around.

Rough experience, glad it worked out for you!

-z

Yeah, the problem was that I had no really working config. Computer got built, XP installed, spent oodles of time getting everything right, computer has connectivity problem, reinstall windows.

I can see why sometimes people go over to Macs after experiences like this.

In any case, I'll check out TrueImage and see if that can be of use to me.

Thanks,

Pradeep