"no network provider accepted the network path" In

[user1002]

Thanks, Bill.

I managed to re-generate the problem. I followed the directions in Bill's post and ran the two netsh commands but the problem is still not solved.

i think netsh int it resetlog.txt is a typo. it's netsh int ip resetlog.txt


Is there a way to list the LSP providers? Is that the output of netsh winsock show cat?

thanks.

[Bill Castner]

Thank you for correcting my earlier typo. To see the LSP list:

1. Click Start, click Run, type Msinfo32, and then click OK.
2. Expand Components, expand Network, and then click Protocol.
3. You will have ten sections under Protocol. The section headings will include the following names if the Winsock2 key is undamaged:

• MSAFD Tcpip [TCP/IP]
• MSAFD Tcpip [UDP/IP]
• RSVP UDP Service Provider
• RSVP TCP Service Provider
• MSAFD NetBIOS [\Device\NetBT_Tcpip...
• MSAFD NetBIOS [\Device\NetBT_Tcpip...
• MSAFD NetBIOS [\Device\NetBT_Tcpip...
• MSAFD NetBIOS [\Device\NetBT_Tcpip...
• MSAFD NetBIOS [\Device\NetBT_Tcpip...
• MSAFD NetBIOS [\Device\NetBT_Tcpip...

If the names are anything different from those in this list, the Winsock2 key is corrupted, or you have a third-party add-on, such as proxy software, installed.

If you have a third-party add-on installed, the name of the add-on will replace the letters "MSAFD" in the list.

If there are more than ten sections in the list, you have third-party additions installed.

If there are fewer than ten sections, there is information missing.
Note These entries represent an installation with only the TCP/IP protocol installed. You can have a working Winsock and see additional entries if another protocol is installed. For example, if you install NWLink IPX/SPX, you will see 7 additional sections, for a total of 17. Below is an example heading of one of the new sections:
MSAFD nwlnkipx [IPX]

Also, each of the new sections that are created by installing NWLink IPX/SPX start with "MSAFD." Therefore, there are still only two sections that do not start with those letters.

Source and please see:
How to Determine and Recover From Winsock2 Corruption
http://support.microsoft.com/kb/811259

[user1002]

Thanks for the information.

I also get the following system event

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4321
Date: 6/9/2007
Time: 8:28:19 PM
User: N/A
Computer: DSKTP
Description:
The name "WORKGROUP :1d" could not be registered on the Interface with IP address
192.168.1.104. The machine with the IP address 192.168.1.100 did not allow the name to be
claimed by this machine."

Is it in anyway related to the problem at hand?

Thanks in advance.

[Bill Castner]

The messsage means the Master Browser on a segment refused to permit another computer to register as the Master Browser.

Check that you are not multi-homed -- with a wired connection to one network segment, and a wireless connection attempting to register on the same, or a different subnet or network segment. You need to take special steps in multi-homed workstation situations in order to successfully bind your workstation's Netbios name with Netbt. From your description and Event entries, it appears you already have an Host address bound to Netbios over TCP/IP and are attempting to bind a second Host IP.

[user1002]

Problem solved, I am quite confident. Yes, it's a firewall issue as Bill indicated in a previous post. The culprit is not Cisco VPN Client; it's Zone Alarm, the firewall, to be blamed, in my case at at least.
The other day I noticed that my computer would suddenly lose all internet connections going to port 80. Using Wireshark and Microsoft Network Monitor I traced what was happening to the packets. It turned out that all packets destined to port 80 were going to 209.87.208.60 [lockup.zonelabs.com].

After some google search, it turned out that that is a common problem when un-installing ZoneAlarm fails to remove all associated DLLs. This document http://lockup.zonelabs.com/downloads/SafeMode.doc offers a solution which worked with me. The solution basically involves deleting some registry entries and the remaining ZA DLLs and folders [vxdatant.dll and Internet Logs] in Safe Mode.
Make sure you turn off System Restore before deleting the files.

The thing that I don't understand is that I uninstalled ZoneAlarm about 7 months ago and the problem started to occur only about a month or so ago; before that everything was normal.

Thanks alot folks for your help.

Also thanks for http://forums.speedguide.net/showthread.php?t=207701

[chicagotech]

Thnak you for the feedback. This How to uninstall Zone Alarm may help,

Make sure that Zone Alarm Firewall and the Zone Alarm service are stopped before starting the uninstallation. Right-click on the Zone Alarm icon and ...
http://www.chicagotech.net/netforums/vi ... 8ab5cae921