TCP/IP problems in XP Pro

[dsdjnpfvf]

Hi,

I've got an unsual problem with TCP/IP in Windows XP.

Since I upgraded from Windows 2000 to XP Pro I have been unable to communicate to any other device via my NIC.

It's installed, and you can enable and disable it with Network Connections. It also detects whether the cable is connected or not. However, whether I use DHCP, or a manually configured IP address, the adapter will not show up in ipconfig at all.

It simply says:

C:\Documents and Settings\Tom>ipconfig

Windows IP Configuration


C:\Documents and Settings\Tom>


Also, if I check the Status tab of the network connection, all the settings such as Subnet, IP, DG, etc just say <Unavailable>.

This is very strange because in the TCP/IP settings for the NIC that I specify stay there fine.

The card just sits at 0 bytes sent/recieved.

I've tried removing and re-installing the network driver with no effect.

It's a VIA Rhine II Fast Ethernet adapter on-board a AT7-MAX2 mainboard.

It's seems to me that the NIC is for some reason not on the TCP/IP stack or something like that.

Any help greatly appreciated as I've exhausted all my ideas!

Many thanks,

Daniel Briley

 

[bcastner]

Try as a start the magic Winsock service repair utility I discuss here: faq779-4625

 

[dsdjnpfvf]

I'm afraid it didn't help, but i'll deffinately remember that utility.

Any other ideas?

Many thanks for your help,

Daniel

 

[dsdjnpfvf]

I have just remembered something. After reading your FAQ, it reminded me.

I used a search hijacker cleaning program to remove your-search.cc hijacker program from my computer earlier today.

All seemed to work fine afterwards, but when I updated to Windows XP was the first time I had reset since I used the utility.

Does this help?

Thanks,

Daniel

 

[bcastner]

Run WinsockFix again, and reboot.

One good thing about the utility is that it will under XP completely rebuild your Winsock service stacks in the registry.

If the problem persists, the next area to focus on is the driver set being used for the network adapter. If you could mention the exact make and model of your NIC I believe several here can help you find a more current driver set.