Network Name Is No Longer Available Error msg

[Phil]

I am running W2K SP3 advanced server as a PDC with a 8TB
array. XP clients are connected via a gigabit network
Intel NIC's and a Cisco Catalyst 4503 switch.

We use the network to transfer large files from the array
to the clients, during file transfers using windows
explorer we are getting "Network Name Is No Longer
Available" errors at intermittent intervals.

Any suggestions?

 

[Danny Slye - [MSFT}]

This could be caused by a number of things or a combination of things. I
would first eliminate the client and server NICs and the switch. You
probably want to hard-code the media type if any are using auto detect and
disable any Jumbo frame settings that might be enabled. Software running
on either the clients or the server could be a factor, especially anything
that might use open file handles such as Antivirus software or Backup
Agents.
See:
822219 You Experience Slow File Server Performance and Delays Occur When You
http://support.microsoft.com/?id=822219

--------------------

X-Tomcat-NG: microsoft.public.win2000.advanced_server

I am running W2K SP3 advanced server as a PDC with a 8TB
array. XP clients are connected via a gigabit network
Intel NIC's and a Cisco Catalyst 4503 switch.

We use the network to transfer large files from the array
to the clients, during file transfers using windows
explorer we are getting "Network Name Is No Longer
Available" errors at intermittent intervals.

Any suggestions?

__
Danny Slye
Microsoft Support Professional
MCSE

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!