Network connection to file server issues

  • Thread starter Thread starter Andy
  • Start date Start date
A

Andy

I am having trouble with at least a couple PCs on a
network of 25 PCs. I no that there have been some network
connectivity issues on this network before. Some of the
network jacks on the main network switch are dead.

My issue in Windows 2000 is this. When the users boot up
in the morning they attempt to access a folder on the
server. They then receive this error: Windows
An error occurred while connecting I: to \\Fileshare\Users
Microsoft Windows Network: The local device name is
already in use. This connection has not been restored.

Usually they can go out and then come back in either 5
min., 10 min. or more and can get in again. Also I have
tried using network places rather than mapped drives with
the same result. The folder list will show up fine bu
trying to access the folder will cause it to stall for
several seconds and then display the message above.

Any ideas?
 
Hi

Maybe this will help.

RESOLUTION
To resolve this problem, obtain the latest service pack for Windows 2000.
For additional information, click the following article number to view the
article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

The English-language version of this fix should have the following file
attributes or later:
Date Time Version Size File name
-------------------------------------------------------
08/02/2001 03:39PM 5.0.2195.4038 370,224 Mrxsmb.sys
08/02/2001 02:57PM 5.0.2195.4031 131,792 Rdbss.sys

NOTE: Install this fix on the client, not the server.

STATUS
=========
Microsoft has confirmed that this is a problem in the Microsoft products
that are listed at the beginning of this article. This problem was first
corrected in Windows 2000 Service Pack 3.

The information applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Professional SP1
- Microsoft Windows 2000 Professional SP2

In case you already have this installed, let me know the following

1. what anti-virus are you using
2. Are yo using any NAT device in your network.

Shilpa Sinha
This posting is provided "AS IS" with no warranties, and confers no rights.
 
I have already installed service pack 3. The virus
software IU was using was Norton Antivirus Corporate
Edition 7.6. I had already disabled the realtime systm
protection but still had the same problem. There is a
Cisco PIX Firewall on the network that I believe uses
NAT. She also got a similar message today when accessing
the same folders. It stated that "the specified network
name is no longer available". This happened as she was
trying to access a folderit became very slow and then
showed up with this error. Othewr times she can
accessfolders fine. I think they might have some network
issues. Someone else had similar probles a few months
back and I switched her to a new port and ran some new
wires. Sometimes the cursor just hangs when trying to
access a folder like there is some network issue and then
the errors will come up.
 
Hi

Maybe the following will be helpful.

Resolution:
==========
This could be because there are multiple clients trying to access the same
server across a NAT device. The source IP addresses from all clients will
be the same as the NAT device which causes problems on the server.

Apply the following post-SP2 Windows 2000 hotfix to address this issue:
Q301673 - SMB Server Does Not Allow More Than 1 Client Connection Over NAT
http://support.microsoft.com/default.aspx?scid=kb;en-us;301673

You Cannot Make More Than One Client Connection Over a NAT Device

SYMPTOMS
=========
When two client computers try to use the server message block (SMB)
protocol to connect to the same server across a network address translation
(NAT) device, the more recent client connection may reset the earlier
client connection. If a client and a server that use the SMB protocol over
a NAT device are copying files, that session may be reset when another
client uses the SMB protocol over the same NAT device to the same server.

Note This problem does not occur when the server is running Microsoft
Windows NT 4.0.

CAUSE
=====
When a new connection is established to a server, the server checks for
previous connections from the same client IP address and deletes any
previous connections. Because NAT acts as a proxy for the SMB protocol by
using the same IP address from the two client connection requests, the
earlier connection is terminated.

RESOLUTION
==========
To resolve this problem, obtain the latest service pack for Windows 2000.
For additional information, click the following article number to view the
article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix has the file attributes (or later) that are
listed in the following table. The dates and times for these files are
listed in coordinated universal time (UTC). When you view the file
information, it is converted to local time. To find the difference between
UTC and local time, use the Time Zone tab in the Date and Time tool in
Control Panel.

Date Time Version Size File name
----------------------------------------------------------
09-Aug-2001 17:35 5.0.2195.4110 1,685,696 Ntkrnlmp.exe
09-Aug-2001 17:35 5.0.2195.4110 1,685,312 Ntkrnlpa.exe
09-Aug-2001 17:36 5.0.2195.4110 1,705,984 Ntkrpamp.exe
09-Aug-2001 17:34 5.0.2195.4110 1,663,424 Ntoskrnl.exe
09-Aug-2001 17:34 5.0.2195.4110 237,104 Srv.sys
09-Aug-2001 17:37 5.0.2195.3805 73,488 Srvsvc.dll


STATUS
=======
Microsoft has confirmed that this is a problem in the Microsoft products
that are listed at the beginning of this article. This problem was first
corrected in Windows 2000 Service Pack 3.

MORE INFORMATION
=================
This fix applies only to the SMB protocol traffic over TCP NetBIOS port
139. The connectivity problem that is mentioned in this article still
occurs on client computers that are running Windows 2000 or later if you
make the connection with direct hosting on port 445. By default, Windows
2000 uses this port.

You can establish no more than one direct hosting client connection across
a NAT device. If you must have more than one simultaneous SMB protocol,
disable either direct hosting on the Windows 2000 file server or on all
clients behind the NAT device.

To disable direct hosting on the server:
1. Start Registry Editor.
2. Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NetBT\Parameters
3. Add the following registry value:
Value Name: SmbDeviceEnabled
Type: REG_DWORD
Value Data: 0

The default setting is 1 (enabled)

When you complete these steps, clients must use port 139 NetBIOS over
TCP/IP to make a connection.

Note To permit multiple connections over the NAT device, Microsoft
recommends that you use Web Distributed Authoring and Versioning (WebDAV).
With this technology, you can perform standard file operations on a remote
share. For additional information about how to install Windows 2000 and
Windows 2000 hotfixes at the same time, click the article number below to
view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

The information in this article applies to:

o Microsoft Windows 2000 Server SP1
o Microsoft Windows 2000 Server SP2
o Microsoft Windows 2000 Advanced Server SP1
o Microsoft Windows 2000 Advanced Server SP2
o Microsoft Windows 2000 Professional SP1
o Microsoft Windows 2000 Professional SP2


Or apply Windows 2000 SP3 on the server

Shilpa Sinha
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top