Winsock Troubleshooting

[Guest]

Thank you for your time.

Is this a true statement?:
--Since I can dial up and access the Internet just fine, my Winsock is OK.

I ask this because I am working on a machine that was symptomatic of a
Winsock problem. (XP, cable connection). I used these newsgroups to run a
myriad of proggies that did not seem to work ... winsockxp fix, LSPfix, etc.
I have also deleted the registry entries as per MS guidelines and restarted.

One thing that might be important to mention. When I did an MSinfo32 I saw
that there were two entries on top of the domain stack .... this computer has
NewDotNet. I have run Spybot, Adaware, and aven NAV2005 (all updated) and
none remove this critter.

So I'd like to ensure that if the Winsock is OK, I can go troubleshoot the
connection itself. Thus my above statement.

Thanx for any help you are willing to provide.

Don
Tucson
AizA

 

[CZ]

AizA:
--Since I can dial up and access the Internet just fine, my Winsock is OK.
I ask this because I am working on a machine that was symptomatic of a
Winsock problem. (XP, cable connection).

Basically, there are two application interfaces to the transport layer:
NetBIOS
WinSock

IE and the ping cmd are examples of WinSock apps. So, if IE works, then
WinSock is functionally.


Per Google: "For information and removal instructions please visit
http://www.newdotnet.com "