Peter S. Young said:
I just added a firewire card to a P4 running XP Pro. XP
gave normal installation notices automatically, and the
firewire card works fine.
Problem: All Winsock applications have lost access to the
TCP/IP protocol. I can't reach my router, let alone the
web.
I have disabled the network function of the firewire card
(since all I want is a data hub for my camera) - no joy.
Different slots, different brands of firewire cards,
different NICs - no joy.
Removed the firewire card - no joy.
Rolled the computer back with System Restore: all TCP/IP
functionality restored.
XP Pro is clearly the culprit. XP is installing software
drivers and making registry changes that are causing the
TCP/IP problem - otherwise, System Restore would not be
the total cure.
I see folks with similar issues posting here. Where is
the hotfix?
Thanks...
Peter Young
(e-mail address removed)
========================================================================
Your logic escapes me as to why it is XP Pro that is the culprit.
The problem develops after installing the firewire card right?
Does that include installing some driver for the card or does
XP Pro just install it with its own driver?
If you are installing some driver that came with the card, then
I would think that is what is causing the issue.
If you are not installing a driver that came with the card, then
I tend to think you probably have damaged winsock keys to
begin with and somehow installing that card pushes them over
the edge.
Have you ever scanned this system for spywares or viruses?
Are you running some third-party firewall program?
I saw a previous post regarding this issue where the resolution
was to rebuild damaged winsock keys in the registry. The winsock
keys usually get damaged from spyware or viruses or even by some
third-party firewall programs.
You could first try scanning for spywares or viruses or uninstall any
third-party firewalls prior to installing that firewire card again.
One good program for removing spyware is Ad-Aware 6.0 181:
Ad-aware 6.0 build 181
http://download.com.com/3000-2144-10214379.html?tag=list
Hopefully you have a functioning updated Anti Virus program.
If not you could scan for viruses here:
TrendMicro Houscall Anti Virus Scan
http://housecall.trendmicro.com/
Here is the method for repairing the winsock keys in the registry:
Make sure all XP critical updates are installed before proceeding.
Uninstall any third-party proxy software or firewall programs before proceeding.
Step 1: Delete registry keys
A)Open Regedit from the Run line (Start > Run - regedit)
B)Go to both of the following keys, EXPORT each of them, and then delete them:
(To export a key, you right click on it and choose "export" - you can choose where to export them to -
DESKTOP is handy -
and you need to type in a file name such as "exported Winsock key" / "exported WinSock2 key"
and then click on SAVE)
HKLM\SYSTEM\CurrentControlSet\Services\Winsock
HKLM\SYSTEM\CurrentControlSet\Services\WinSock2
C)Restart the computer
NOTE: It is important to restart the computer after deleting the Winsock keys.
Doing so causes the XP operating system to recreate shell entries for those two
keys. If this is not done, the next step does not work correctly.
Step 2: Install TCP/IP on top of itself
Go to Control Panel | Network Connections
A)Open the properties window of the network connection (Local Area Connection)
B)Click Install
C)Click Protocol, then Add
D)Click Have Disk
E)Type the path to the \%systemroot%\inf folder (usually C:\Windows\inf) and click OK
(if you try to click Browse, then browse to the \inf folder,
it may not show up in the list)
F)You should now see "Internet Protocol (TCP/IP)" in the list of available
protocols. Select it and click OK.
G)Restart the computer
When the computer reboots you will have functional Winsock keys.
If so, then be sure to delete the exported winsock and winsock2 reg files.
(You don't want to accidentally put them back in the registry)
Side effects and possible problems:
This method will restore basic functionality to the Winsock keys, but is not a
complete rebuild. On a default install of Windows XP the registry key:
HKLM\SYSTEM\CurrentControlSet\Services\Winsock2\
Parameters\Protocol_Catalog9\Catalog_Entries will have 11 sub-keys.
When applying this method, the Catalog_Entries will only have 3 sub-keys.
However, it works and there does not appear to be any side effects.
The missing entries relate back to the:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces key.
Also, third-party proxy software or firewalls may need to be reinstalled.
===========================================================================
