14thBaloo
i am not 100% sure on the McAfee firewall parameters, but this is a trick that worked with the older Zone Alarm corruption problems.
When someone had a firewall installed, and either got tired of it, or was a demo and expired. They would remove it from the computer, later when even the smallest change in network occured (in my case, a new ISP) nothing would work, but looking around in registry usually brings up the tell tale signs of a zone alarm install. The only way so far to fix this was to
1.)reinstall the firewall (no connection needed)
2.)Remove any - all of the old rule sets
3.)set any connection to "Allow All" or "Disabled" or similar parameters
reboot and try that.
McAfee's "web style" firewall, currently packaged with brand name computers, with that bunch of Zero Knowledge, is a difficult, and mostly un-user friendly, with lack of options to adjust it to the user. Although it does work once it is tailored to suit the system it was installed on.
If you have the other McAfee firewall, (store bought version)thats another story all together. As well i have a version of that here and could probably figure something out for you.
In any case, the Winsockfix, replaces Winsock keys in the registry, among other things. I don't think the Firewall installs as a LSP. If you want to test this out,
export these 2 registry keys to the desktop
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2
and
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock
Then install the firewall again, export the same keys out and compare them?
As well, if you install the Firewall, and can have it in a disabled mode, and your connection works..then Winsock is not to blame. It is a very difficult firewall to work with, let me know which one and version you have and i will see if I can duplicate your problem here
