Can ping but not start TCP connection

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

Hi,

I have a weird network problem on one of our Win2000 Pro workstation
systems.

Symptoms:

* Can ping other systems on the network (ip address only)
* Can map and use network drives
* Can't start TCP connections - this means that all services that use
the network (e.g. DNS) fail

In the output of "netstat -a" we can see the established TCP connections
to port 139 on the server (i.e. the mapped drives), however when we try
to telnet to the same port on the server we get connection refused.

Any ideas?


Dave.

 

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

Hi David - Try restoring your Winsock2 stack. From my Blog, Defending Your
Machine, here: http://defendingyourmachine.blogspot.com/


Download both a copy of LSPFIX here:
http://www.cexx.org/lspfix.htm

AND a copy of Winsockfix for W95, W98, and ME
http://www.tacktech.com/pub/winsockfix/WinsockFix.zip
Directions here: http://www.tacktech.com/display.cfm?ttid=257

or here for Win2k/XP
http://files.webattack.com/localdl834/WinsockxpFix.exe
Info and download here: http://www.spychecker.com/program/winsockxpfix.html
Directions here: http://www.iup.edu/house/resnet/winfix.shtm

The process of removing certain malware may kill your internet connection.
If this should occur, these programs, LSPFIX and WINSOCKFIX, will enable you
to regain your connection.

NOTE: It is reported that in XP SP2, the Run command

netsh winsock reset

will fix this problem without the need for these programs. (You can also try
this if you're on XP SP1. There has also been one, as yet unconfirmed,
report that this also works there.) Also, one MS technician suggested the
following sequence:

netsh int reset all
ipconfig /flushdns

See also: http://windowsxp.mvps.org/winsock.htm for additional XPSP2
info/approaches using the netsh command.

An alternative approach with necessary .reg files which will often work even
when the above doesn't is defined here, courtesy of Bob Cerelli:
http://www.onecomputerguy.com/ie_tips.htm#winsock_fix Recommended.


--
Regards, Jim Byrd, MS-MVP

"David Macdonald" <david.nospam.macdonald@unsw.nospam.edu.au> wrote in
message news:eyvzMc7SFHA.2124@TK2MSFTNGP14.phx.gbl
> Hi,
>
> I have a weird network problem on one of our Win2000 Pro workstation
> systems.
>
> Symptoms:
>
> * Can ping other systems on the network (ip address only)
> * Can map and use network drives
> * Can't start TCP connections - this means that all services that use
> the network (e.g. DNS) fail
>
> In the output of "netstat -a" we can see the established TCP
> connections to port 139 on the server (i.e. the mapped drives),
> however when we try to telnet to the same port on the server we get
> connection refused.
>
> Any ideas?
>
>
> Dave.

 

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

"The process of removing certain malware may kill your internet connection."

Interesting. The important detail that I neglected to include in my
original posting was that Microsoft Anti-spyware was used in the last
day or so on this machine.

Thanks for your help, I'll give it a go.


Dave.


Jim Byrd wrote:
> Hi David - Try restoring your Winsock2 stack. From my Blog, Defending Your
> Machine, here: http://defendingyourmachine.blogspot.com/
>
>
> Download both a copy of LSPFIX here:
> http://www.cexx.org/lspfix.htm
>
> AND a copy of Winsockfix for W95, W98, and ME
> http://www.tacktech.com/pub/winsockfix/WinsockFix.zip
> Directions here: http://www.tacktech.com/display.cfm?ttid=257
>
> or here for Win2k/XP
> http://files.webattack.com/localdl834/WinsockxpFix.exe
> Info and download here: http://www.spychecker.com/program/winsockxpfix.html
> Directions here: http://www.iup.edu/house/resnet/winfix.shtm
>
> The process of removing certain malware may kill your internet connection.
> If this should occur, these programs, LSPFIX and WINSOCKFIX, will enable you
> to regain your connection.
>
> NOTE: It is reported that in XP SP2, the Run command
>
> netsh winsock reset
>
> will fix this problem without the need for these programs. (You can also try
> this if you're on XP SP1. There has also been one, as yet unconfirmed,
> report that this also works there.) Also, one MS technician suggested the
> following sequence:
>
> netsh int reset all
> ipconfig /flushdns
>
> See also: http://windowsxp.mvps.org/winsock.htm for additional XPSP2
> info/approaches using the netsh command.
>
> An alternative approach with necessary .reg files which will often work even
> when the above doesn't is defined here, courtesy of Bob Cerelli:
> http://www.onecomputerguy.com/ie_tips.htm#winsock_fix Recommended.
>
>

 

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

YW, David - Let us know how you make out, please.

--
Regards, Jim Byrd, MS-MVP

"David Macdonald" <david.nospam.macdonald@unsw.nospam.edu.au> wrote in
message news:exYAOs7SFHA.2432@TK2MSFTNGP12.phx.gbl
> "The process of removing certain malware may kill your internet
> connection."
>
> Interesting. The important detail that I neglected to include in my
> original posting was that Microsoft Anti-spyware was used in the last
> day or so on this machine.
>
> Thanks for your help, I'll give it a go.
>
>
> Dave.
>
>
> Jim Byrd wrote:
>> Hi David - Try restoring your Winsock2 stack. From my Blog,
>> Defending Your Machine, here:
>> http://defendingyourmachine.blogspot.com/
>>
>>
>> Download both a copy of LSPFIX here:
>> http://www.cexx.org/lspfix.htm
>>
>> AND a copy of Winsockfix for W95, W98, and ME
>> http://www.tacktech.com/pub/winsockfix/WinsockFix.zip
>> Directions here: http://www.tacktech.com/display.cfm?ttid=257
>>
>> or here for Win2k/XP
>> http://files.webattack.com/localdl834/WinsockxpFix.exe
>> Info and download here:
>> http://www.spychecker.com/program/winsockxpfix.html Directions here:
>> http://www.iup.edu/house/resnet/winfix.shtm
>>
>> The process of removing certain malware may kill your internet
>> connection. If this should occur, these programs, LSPFIX and
>> WINSOCKFIX, will enable you to regain your connection.
>>
>> NOTE: It is reported that in XP SP2, the Run command
>>
>> netsh winsock reset
>>
>> will fix this problem without the need for these programs. (You can
>> also try this if you're on XP SP1. There has also been one, as yet
>> unconfirmed, report that this also works there.) Also, one MS
>> technician suggested the following sequence:
>>
>> netsh int reset all
>> ipconfig /flushdns
>>
>> See also: http://windowsxp.mvps.org/winsock.htm for additional XPSP2
>> info/approaches using the netsh command.
>>
>> An alternative approach with necessary .reg files which will often
>> work even when the above doesn't is defined here, courtesy of Bob
>> Cerelli: http://www.onecomputerguy.com/ie_tips.htm#winsock_fix
>> Recommended.

 

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

Jim Byrd wrote:
> YW, David - Let us know how you make out, please.
>

Success. I ran WinsockxpFix.exe only, and everything is working perfectly.

Thanks for your help.


Dave.

 

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

YW, Dave - Glad you got it straightened out.

--
Regards, Jim Byrd, MS-MVP

"David Macdonald" <david.nospam.macdonald@unsw.nospam.edu.au> wrote in
message news:%23JUKxcGTFHA.3308@TK2MSFTNGP14.phx.gbl
> Jim Byrd wrote:
>> YW, David - Let us know how you make out, please.
>>
>
> Success. I ran WinsockxpFix.exe only, and everything is working
> perfectly.
>
> Thanks for your help.
>
>
> Dave.