Ken Wickes [MSFT]
April 10th 03, 09:01 PM
I have traced several of these problems to improperly configured winsock
LSPs. Run "winmsd" and go to Components/Network/Protocol. Look at the
names in the list, anything with "MSAFD" in it or the "RSVP xxx Service
Provider" should be fine. Anything else is suspect, and uninstalling the
owning program might help.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Joles" > wrote in message
...
> Hi All,
> Your help would be truly appreciated with this... I
> receive the error message listed in the subject line when
> I ping'd my computer 127.0.0.1 (as advised by my internet
> provider). The error code was "O" The main problem is I
> can get connected to the provider's website but the
> provider can't authenticate my comp. I don't know much
> about the inner workings of the computer so please
> respond with the kind of verbage one would read
> in "window sockets for dummies"
>
> thank you.
>
LSPs. Run "winmsd" and go to Components/Network/Protocol. Look at the
names in the list, anything with "MSAFD" in it or the "RSVP xxx Service
Provider" should be fine. Anything else is suspect, and uninstalling the
owning program might help.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Joles" > wrote in message
...
> Hi All,
> Your help would be truly appreciated with this... I
> receive the error message listed in the subject line when
> I ping'd my computer 127.0.0.1 (as advised by my internet
> provider). The error code was "O" The main problem is I
> can get connected to the provider's website but the
> provider can't authenticate my comp. I don't know much
> about the inner workings of the computer so please
> respond with the kind of verbage one would read
> in "window sockets for dummies"
>
> thank you.
>