XP and 98 Ispoke too soon

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The connection is lost. After selecting NetBIOS on the IPX protocol
everything worked fine. I shutdown and estarted both computers, again
everything went fine. I posted my thank tou and went to bed. Ididnot turn off
either machine,just let them go to thier respective down modes. This morning
XP again doesn't see 98 on the network, but all the shares are listed in
Network places. I restarted both comps and 98 gave me this alert IPHLPAP.DLL
cannot start

This was last thing asked for
98 BASE2
CDiagnosis
Start diagnosis for
Full Targets

" ping %a"

Unknown host %a.


" net view %a"

The syntax is incorrect.
For help, type NET VIEW /? at the command prompt.

Ping Targets

" ping %a"

Unknown host %a.


End diagnosis for


XP Lddesk
CDiagnosis V1.31
Start diagnosis for LDESK
Full Targets LDESK 192.168.1.103 BASE2 192.168.1.101 127.0.0.1

"LDESK ping LDESK"



Pinging LDESK [192.168.1.103] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.103:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"LDESK net view LDESK"

Shared resources at LDESK

MAIN

Share name Type Used as Comment

-------------------------------------------------------------------------------
mainPrint Print HP DeskJet 670C
My Documents Disk
SharedDocs Disk
The command completed successfully.


"LDESK ping 192.168.1.103"



Pinging 192.168.1.103 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.103:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"LDESK net view 192.168.1.103"


"LDESK ping BASE2"

Ping request could not find host BASE2. Please check the name and try again.


"LDESK net view BASE2"


"LDESK ping 192.168.1.101"



Pinging 192.168.1.101 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"LDESK net view 192.168.1.101"


"LDESK ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"LDESK net view 127.0.0.1"


Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

"LDESK ping www.yahoo.com"



Pinging www.yahoo.akadns.net [216.109.117.204] with 32 bytes of data:



Reply from 216.109.117.204: bytes=32 time=17ms TTL=54

Reply from 216.109.117.204: bytes=32 time=17ms TTL=54

Reply from 216.109.117.204: bytes=32 time=17ms TTL=54

Reply from 216.109.117.204: bytes=32 time=16ms TTL=53



Ping statistics for 216.109.117.204:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 16ms, Maximum = 17ms, Average = 16ms


"LDESK ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=100ms TTL=53

Reply from 66.94.230.32: bytes=32 time=93ms TTL=53

Reply from 66.94.230.32: bytes=32 time=99ms TTL=53

Reply from 66.94.230.32: bytes=32 time=86ms TTL=53



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 86ms, Maximum = 100ms, Average = 94ms


"LDESK ping 192.168.1.1"



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 2ms, Average = 0ms


End diagnosis for LDESK
 
The connection is lost. After selecting NetBIOS on the IPX protocol
everything worked fine. I shutdown and estarted both computers, again
everything went fine. I posted my thank tou and went to bed. Ididnot turn off
either machine,just let them go to thier respective down modes. This morning
XP again doesn't see 98 on the network, but all the shares are listed in
Network places. I restarted both comps and 98 gave me this alert IPHLPAP.DLL
cannot start

This was last thing asked for
98 BASE2
CDiagnosis
Start diagnosis for
Full Targets

" ping %a"

Unknown host %a.


" net view %a"

The syntax is incorrect.
For help, type NET VIEW /? at the command prompt.

Ping Targets

" ping %a"

Unknown host %a.


End diagnosis for


XP Lddesk
CDiagnosis V1.31
Start diagnosis for LDESK
Full Targets LDESK 192.168.1.103 BASE2 192.168.1.101 127.0.0.1

"LDESK ping LDESK"



Pinging LDESK [192.168.1.103] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.103:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"LDESK net view LDESK"

Shared resources at LDESK

MAIN

Share name Type Used as Comment

-------------------------------------------------------------------------------
mainPrint Print HP DeskJet 670C
My Documents Disk
SharedDocs Disk
The command completed successfully.


"LDESK ping 192.168.1.103"



Pinging 192.168.1.103 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.103:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"LDESK net view 192.168.1.103"


"LDESK ping BASE2"

Ping request could not find host BASE2. Please check the name and try again.


"LDESK net view BASE2"


"LDESK ping 192.168.1.101"



Pinging 192.168.1.101 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"LDESK net view 192.168.1.101"


"LDESK ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"LDESK net view 127.0.0.1"


Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

"LDESK ping www.yahoo.com"



Pinging www.yahoo.akadns.net [216.109.117.204] with 32 bytes of data:



Reply from 216.109.117.204: bytes=32 time=17ms TTL=54

Reply from 216.109.117.204: bytes=32 time=17ms TTL=54

Reply from 216.109.117.204: bytes=32 time=17ms TTL=54

Reply from 216.109.117.204: bytes=32 time=16ms TTL=53



Ping statistics for 216.109.117.204:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 16ms, Maximum = 17ms, Average = 16ms


"LDESK ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=100ms TTL=53

Reply from 66.94.230.32: bytes=32 time=93ms TTL=53

Reply from 66.94.230.32: bytes=32 time=99ms TTL=53

Reply from 66.94.230.32: bytes=32 time=86ms TTL=53



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 86ms, Maximum = 100ms, Average = 94ms


"LDESK ping 192.168.1.1"



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 2ms, Average = 0ms


End diagnosis for LDESK
Click to expand...

Fred,

What I see above looks like garbled output from my CDiag code. Does CDiag maybe
need to be re installed per my previous post?

Having read your previous reports, I'm still unsure what protocols you have
installed or de installed. You might find your network works OK for a while
with extraneous protocols, or you might not.

I will here repeat my previous advice.

Installation of IPX/SPX or NetBEUI serves as a workaround when the problem is
related to the TCP/IP on the LAN (maybe a firewall misconfigured). If you have
physical connectivity issues, or if file sharing is not set up properly on one
or more computers, adding IPX/SPX or NetBEUI will not help. And if you don't
setup IPX/SPX or NetBEUI properly, it will simply hamper diagnosing the actual
problem.

Windows networking is built around TCP/IP, and uses NetBIOS Over TCP/IP as an
interface to file and printer sharing.

If there's a problem with TCP/IP, or with NBT, IPX/SPX or NetBEUI may provide a
workaround. But it will also add needless complexity, and may cause long term
stability problems.

If the problem being experienced is caused by authentication / authorisation,
IPX/SPX or NetBEUI won't resolve anything.

Fix the problem. Don't add to it.

Here are a couple good articles on the subject (remember, WinXP is WinNT V5.1):
<http://support.microsoft.com/?id=128233>
<http://www.networkmagazine.com/article/NMG20000517S0009>
<http://www.ultratech-llc.com/BrainWave/TechDocs/Resolution.html>

To start, you need to eliminate excess protocols from the list of items under
Local Area Connection Properties. You only need the following items in the
list:
Client for Microsoft Networks
File and Printer Sharing For Microsoft Networks
QoS Packet Scheduler (optional)
Internet Protocol (TCP/IP)

Then, make sure that NetBIOS Over TCP/IP is enabled on both computers. Local
Area Connection - Properties - TCP/IP - Properties - Advanced - WINS - Enable
NetBIOS over TCP/IP.

You specifically don't require IPX/SPX or NetBEUI.

And as you report your problem, continuing the same thread (if not more than
several days since the last post) works better than starting a new thread.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.
 
Ok I removed all but the list on ldesk(XP) this included Client server for
netware and Net work moniter driver. On Base 2(98) I removed MS family login,
NetBEUI, IPX/SPX. 98 machine does not have QOS but lists File and printer
sharing. NetBIOS over TCP/IP is enabled on both. Neither computer sees
anything. I reran cdiag, on the 98 machine cmd box says echo off out of env
space and bad command. note pad result is as follows

Diagnosis V1.31
Start diagnosis for
Full Targets

" ping %a"

Unknown host %a.
" net view %a"

The syntax is incorrect.
For help, type NET VIEW /? at the command prompt.

Ping Targets

" ping %a"

Unknown host %a.
End diagnosis for


FOR XP MAchine

CDiagnosis V1.31
Start diagnosis for LDESK
Full Targets LDESK 192.168.1.103 BASE2 192.168.1.101 127.0.0.1

"LDESK ping LDESK"



Pinging LDESK [192.168.1.103] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.103:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"LDESK net view LDESK"

Shared resources at LDESK

MAIN

Share name Type Used as Comment

-------------------------------------------------------------------------------
mainPrint Print HP DeskJet 670C
My Documents Disk
SharedDocs Disk
The command completed successfully.


"LDESK ping 192.168.1.103"



Pinging 192.168.1.103 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.103:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"LDESK net view 192.168.1.103"


"LDESK ping BASE2"

Ping request could not find host BASE2. Please check the name and try again.


"LDESK net view BASE2"


"LDESK ping 192.168.1.101"



Pinging 192.168.1.101 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"LDESK net view 192.168.1.101"


"LDESK ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"LDESK net view 127.0.0.1"


Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

"LDESK ping www.yahoo.com"



Pinging www.yahoo.akadns.net [216.109.117.106] with 32 bytes of data:



Reply from 216.109.117.106: bytes=32 time=17ms TTL=53

Reply from 216.109.117.106: bytes=32 time=18ms TTL=53

Reply from 216.109.117.106: bytes=32 time=17ms TTL=54

Reply from 216.109.117.106: bytes=32 time=18ms TTL=54



Ping statistics for 216.109.117.106:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 17ms, Maximum = 18ms, Average = 17ms


"LDESK ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=93ms TTL=53

Reply from 66.94.230.32: bytes=32 time=91ms TTL=53

Reply from 66.94.230.32: bytes=32 time=91ms TTL=53

Reply from 66.94.230.32: bytes=32 time=86ms TTL=53



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 86ms, Maximum = 93ms, Average = 90ms


"LDESK ping 192.168.1.1"



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


End diagnosis for LDESK


Chuck said:
The connection is lost. After selecting NetBIOS on the IPX protocol
everything worked fine. I shutdown and estarted both computers, again
everything went fine. I posted my thank tou and went to bed. Ididnot turn off
either machine,just let them go to thier respective down modes. This morning
XP again doesn't see 98 on the network, but all the shares are listed in
Network places. I restarted both comps and 98 gave me this alert IPHLPAP.DLL
cannot start

This was last thing asked for
98 BASE2
CDiagnosis
Start diagnosis for
Full Targets

" ping %a"

Unknown host %a.


" net view %a"

The syntax is incorrect.
For help, type NET VIEW /? at the command prompt.

Ping Targets

" ping %a"

Unknown host %a.


End diagnosis for


XP Lddesk
CDiagnosis V1.31
Start diagnosis for LDESK
Full Targets LDESK 192.168.1.103 BASE2 192.168.1.101 127.0.0.1

"LDESK ping LDESK"



Pinging LDESK [192.168.1.103] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.103:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"LDESK net view LDESK"

Shared resources at LDESK

MAIN

Share name Type Used as Comment

-------------------------------------------------------------------------------
mainPrint Print HP DeskJet 670C
My Documents Disk
SharedDocs Disk
The command completed successfully.


"LDESK ping 192.168.1.103"



Pinging 192.168.1.103 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.103:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"LDESK net view 192.168.1.103"


"LDESK ping BASE2"

Ping request could not find host BASE2. Please check the name and try again.


"LDESK net view BASE2"


"LDESK ping 192.168.1.101"



Pinging 192.168.1.101 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"LDESK net view 192.168.1.101"


"LDESK ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"LDESK net view 127.0.0.1"


Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

"LDESK ping www.yahoo.com"



Pinging www.yahoo.akadns.net [216.109.117.204] with 32 bytes of data:



Reply from 216.109.117.204: bytes=32 time=17ms TTL=54

Reply from 216.109.117.204: bytes=32 time=17ms TTL=54

Reply from 216.109.117.204: bytes=32 time=17ms TTL=54

Reply from 216.109.117.204: bytes=32 time=16ms TTL=53



Ping statistics for 216.109.117.204:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 16ms, Maximum = 17ms, Average = 16ms


"LDESK ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=100ms TTL=53

Reply from 66.94.230.32: bytes=32 time=93ms TTL=53

Reply from 66.94.230.32: bytes=32 time=99ms TTL=53

Reply from 66.94.230.32: bytes=32 time=86ms TTL=53



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 86ms, Maximum = 100ms, Average = 94ms


"LDESK ping 192.168.1.1"



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 2ms, Average = 0ms


End diagnosis for LDESK
Click to expand...

Fred,

What I see above looks like garbled output from my CDiag code. Does CDiag maybe
need to be re installed per my previous post?

Having read your previous reports, I'm still unsure what protocols you have
installed or de installed. You might find your network works OK for a while
with extraneous protocols, or you might not.

I will here repeat my previous advice.

Installation of IPX/SPX or NetBEUI serves as a workaround when the problem is
related to the TCP/IP on the LAN (maybe a firewall misconfigured). If you have
physical connectivity issues, or if file sharing is not set up properly on one
or more computers, adding IPX/SPX or NetBEUI will not help. And if you don't
setup IPX/SPX or NetBEUI properly, it will simply hamper diagnosing the actual
problem.

Windows networking is built around TCP/IP, and uses NetBIOS Over TCP/IP as an
interface to file and printer sharing.

If there's a problem with TCP/IP, or with NBT, IPX/SPX or NetBEUI may provide a
workaround. But it will also add needless complexity, and may cause long term
stability problems.

If the problem being experienced is caused by authentication / authorisation,
IPX/SPX or NetBEUI won't resolve anything.

Fix the problem. Don't add to it.

Here are a couple good articles on the subject (remember, WinXP is WinNT V5.1):
<http://support.microsoft.com/?id=128233>
<http://www.networkmagazine.com/article/NMG20000517S0009>
<http://www.ultratech-llc.com/BrainWave/TechDocs/Resolution.html>

To start, you need to eliminate excess protocols from the list of items under
Local Area Connection Properties. You only need the following items in the
list:
Client for Microsoft Networks
File and Printer Sharing For Microsoft Networks
QoS Packet Scheduler (optional)
Internet Protocol (TCP/IP)

Then, make sure that NetBIOS Over TCP/IP is enabled on both computers. Local
Area Connection - Properties - TCP/IP - Properties - Advanced - WINS - Enable
NetBIOS over TCP/IP.

You specifically don't require IPX/SPX or NetBEUI.

And as you report your problem, continuing the same thread (if not more than
several days since the last post) works better than starting a new thread.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.
Click to expand...
 
I had this problem with win xp & win 98. the xp is a new dell with a
built in network adapter. what fixed it was to install an old network
card that I had laying around & disable the built in.
diagnostics on the built in card were ok however.
-Wayne
 
Ok I removed all but the list on ldesk(XP) this included Client server for
netware and Net work moniter driver. On Base 2(98) I removed MS family login,
NetBEUI, IPX/SPX. 98 machine does not have QOS but lists File and printer
sharing. NetBIOS over TCP/IP is enabled on both. Neither computer sees
anything. I reran cdiag, on the 98 machine cmd box says echo off out of env
space and bad command. note pad result is as follows
Click to expand...

Fred,

OK, it looks like CDiag won't run on Base2 because of environment space
limitations; it can't set any additional environment variables, so it doesn't
run properly.

From looking at the CDiag run on LDesk, there is one definite problem pretty
obvious. LDesk can't even ping itself. This has to be either a firewall
problem, or corrupt network components.

What AntiVirus product is running on LDesk?

This could be an LSP/Winsock / TCP/IP corruption problem.
http://support.microsoft.com/?id=318584
http://support.microsoft.com/?id=811259

If XP RTM or Service Pack 1:
1. Backup and delete the following registry keys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
2. Reboot.
3. Open the network connections folder, right click your network connection, and
click Properties.
4. Click Install | Protocol | Add.
5. Click "Have Disk...", type "\windows\inf" in the box, and click OK.
6. Click "Internet Protocol (TCP/IP)", then click OK.
7. Reboot.

If XP SP2:
1. Start - Run - "cmd".
2. Type "netsh winsock reset catalog" into the command window.

Give LSP-Fix <http://www.cexx.org/lspfix.htm>, WinsockFix
<http://www.tacktech.com/display.cfm?ttid=257>, or WinsockXPFix
<http://www.spychecker.com/program/winsockxpfix.html> a shot.

If no help yet, reset TCP/IP.
http://support.microsoft.com/?id=299357

Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into the command
window.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.
 
Back
Top