RE: Network Path Lost

Good Morning

Let's take a look at some areas that may cause path not found.

1) Do you have Service Pack 2 installed on the machines ? If not ..visit the
Windows Update web page. open Internet Explorer >Tools pull down menu Windows
Update and install all updates

2) What manufacturer made your ethernet card..D-Link, RealTek...etc ? Visit
the manufacturers website and download the latest patch/driver for your model
of ethernet card. Then install it ...reboot. Some ethernet network cards are
known to cause this issue.

3)Make sure the Server service is set to Automatic and is running.

4)Control Panel >System>Hardware Tab>Device Manager>under Network Devices
select your Network Adapter...double click or right click properties Look for
a Tab named Power Management or sift through the different tabs and look for
a option that says "Allow computer to to turn off this device for power
saving". Make sure this option is not checked marked.

5) Control Panel > Network Connections > double click you LAN network
connection >properties> uncheck Notify me when this connection has limited or
no connectivity

6) Interesting Article - http://support.microsoft.com/kb/320819

7) By Default windows XP limits Max. TCP connections to 10 at one time.
Previous versions of the Windows OS 2000 and before, allows unlimited TCP
connections. Since your using XP as a replacement for a file server with tons
of network traffic. This could cause some slow downs and back ups. Lets do
some heavy duty configuration and unlock the TCP max connections from 10 to
100 and add hardening the TCP/IP stack by invoking SynAttack protection on
your computers.

Enter these settings on your main machine. If you are satisified then try
entering these options on the rest of your computers on the LAN.

Open your registry editor >start>run>Regedt32 ...add the following 4
registry settings.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\parameter
Right click right window pane .. New > Dword Value> TcpMaxHalfOpen >right
click on the new entry...modify > Under the Base heading select Decimal>
Value Data enter 100..click ok.

Description: This parameter controls the number of connections in the
SYN-RCVD state allowed before SYN-ATTACK protection begins to operate. If
SynAttackProtect is set to 1, ensure that this value is lower than the AFD
listen backlog on the port you want to protect(see Backlog Parameters for
more information) . See the SynAttackProtect parameter for more details.


....next entry

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\parameter
Right click right window pane .. New>Dword Value> SynAttackProtect >right
click on the new entry...modify > Value Data enter 2..click ok.

Description: Synattack protection involves reducing the amount of
retransmissions for the SYN-ACKS, which will reduce the time for which
resources have to remain allocated. The allocation of route cache entry
resources is delayed until a connection is made. If synattackprotect = 2,
then the connection indication to AFD is delayed until the three-way
handshake is completed. Also note that the actions taken by the protection
mechanism only occur if TcpMaxHalfOpen and TcpMaxHalfOpenRetried settings are
exceeded.


entry#3..

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\parameter
Right click right window pane .. New>Dword Value> TcpMaxHalfOpenRetried
right click on the new entry...modify > Under the Base heading select
Decimal> Value Data enter 80..click ok.

Description: This parameter controls the number of connections in the
SYN-RCVD state for which there has been at least one retransmission of the
SYN sent, before SYN-ATTACK attack protection begins to operate. See the
SynAttackProtect parameter for more details.

4th entry...

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\parameter
Right click right window pane .. New>Dword Value> TcpNumConnections
right click on the new entry...modify > Under the Base heading select
Decimal> Value Data enter 100..click ok.

Description: This parameter limits the maximum number of connections that
TCP can have open at the same time. Even thou you could allow unlimited
amount of TCP connections with this setting. I have read postings on having
more then 100 simaltanious TCP connections may cause XP to slow down or cause
Operating System corruption possibly leading to the blue screen monster.

Whew.. ok try all of these suggestions and let me know how it goes.

Have a good one Buster !
.

Relevant Pages

  • Re: Max Connections
    ... The OS controls TCP connections too, the same as named pipes. ... If SQL Server 2005 Express is running on Windows XP Home, ...
    (microsoft.public.sqlserver.clients)
  • Re: windows xp home edition taking ages to boot up
    ... access the net on the laptop my pc popped up with a windows message ... internet as well as giving network access to your daughter. ... that in network connections you have 1 local area connection is that ... You can access Event Viewer by selecting Start, ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Event ID: 1006 and multiple login screens
    ... > This means that from the Windows point of view, ... > server is making multiple RDP connections from the same IP ... > number of simultaneous username/password login screens. ... > using per-device licenses, the other is using per-user licenses. ...
    (microsoft.public.windows.terminal_services)
  • Re: winsock error 10060
    ... How to determine and to recover from Winsock2 corruption in Windows ... third-party add-ons hooking up on your beowser and causing the timing out! ... Connections>> Double click Internet Options, ... Click on General Tab and you will see a Button ...
    (microsoft.public.windowsxp.general)
  • Re: FreeBSD 7.0: sockets stuck in CLOSED state...
    ... In FreeBSD, as with all UNIX/Berkeley sockets systems, each socket is actually represented by a set of data structures representing different layers of abstraction. ... For example, if you close the file descriptor, freeing struct file, the socket and protocol state may persist for some time until the TCP connection closes. ... one is that TCP connections now appear in netstat in the CLOSED state for longer than before, and another is that open sockets that are associated with CLOSED TCP connections now count against the global resource limit on the number of simultaneous TCP connections. ...
    (freebsd-net)
Loading