B
Bob H
I'm using a Toshiba laptop with windows xp. When I travel,
I use my dial-up ISP to get my emails. I unfortunately let
windows do the automatic updates on XP. I have just notice
that once I dial up and hang up, I cannot re-establish
connection with my ISP. I can get the initial connection,
but the cannot get my password confirmed. I get an
error:619. This has been established to be a TCP/IP
problem. I cannot tell when this problem started to occur.
I have tried using "netsp int ip reset resetlog.txt", but
it does not reset the stack. I know this because if you
run this command directly after a fresh boot up, it runs,
and when it completes it drops to the command prompt and
you can type in exit. After the initial dial-up connection
and disconnect, if you type the command to reset the stack,
it just stays there in neverland. It does not complete the
reset and you cannot type in exit.
I cannot determine how far I need to roll back my computer
to get rid of whatever XP patch may have caused the problem
and I have too much on my computer to wipe the disk clean
and start over? Has anyone seen this problem or does
anyone have any suggestions?
I use my dial-up ISP to get my emails. I unfortunately let
windows do the automatic updates on XP. I have just notice
that once I dial up and hang up, I cannot re-establish
connection with my ISP. I can get the initial connection,
but the cannot get my password confirmed. I get an
error:619. This has been established to be a TCP/IP
problem. I cannot tell when this problem started to occur.
I have tried using "netsp int ip reset resetlog.txt", but
it does not reset the stack. I know this because if you
run this command directly after a fresh boot up, it runs,
and when it completes it drops to the command prompt and
you can type in exit. After the initial dial-up connection
and disconnect, if you type the command to reset the stack,
it just stays there in neverland. It does not complete the
reset and you cannot type in exit.
I cannot determine how far I need to roll back my computer
to get rid of whatever XP patch may have caused the problem
and I have too much on my computer to wipe the disk clean
and start over? Has anyone seen this problem or does
anyone have any suggestions?