Cannot Copy File : The specified network name is no longer availab

[Guest]

This has started to crop up today on one of our windows 2000 servers. Is
happening on several workstations, only copying files to this server.

Seems to happen whether copying one file or many, small or huge.

Things I have tried.

Latest drivers for NIC on server, no difference.

Upgraded Bios on server, no difference.

Reapplied all security and permissions, no difference.

Deleted folders and files, recreated all and shares, no difference.

Disabled virus software, no difference.

Computers with problem, are on differant floors and switches, so rules out
the switch.

Have tried differant network cable on the server, and same problem happens.

Tried server on differant switch in comms room, same problem.

No errors appear in event viewer on server or clients.

When copying files, running a ping -t to server name, no time outs and
everything under 10ms response, yet above message still crops up.

Searched all through technet and google, and haven't found anything I
haven't tried yet.

Anyone got any ideas ?

Thanks

 

[Guest]

Any errors in event viewer on the source or destination? Also make sure you
have a duplex match for the server and the port it's plugged into. If the
server is hard coded to 100Mb full duplex, make sure the switch port is the
same and vice versa. Both ends should be identical.

 

[Wabbitt97]

Network name???

Check the DNS?

First think the worst then find ways around it.

 

[Guest]

DNS resolves fine. Doing traces and pings, name never times out or disconnects.

Ping DNS name when copying file, with -t. It doesn't time out and response
times remain constant. Yet still fails with same error.

 

[Guest]

No errors in event viewer on server or on source computers.

All computers running 100 mb full duplex, checked on switch and nic's.

Server running 100 mb full duplex, checked on switch and nic.

Tried new cable on server as well, which was working find on another server,

 

[Guest]

Run a network monitor capture. Then copy it to your workstation and open it
in ethereal. http://www.ethereal.com (free opensource) Analyze the traffic,
check "expert" under "Analyze". Look for excess collisions, etc. Report
findings.

 

[Guest]

Found out from person who used to look after this server, it is an
intermittent problem it has had for ages.

On a reboot, it is fine, can copy, whatever fine for a while. The all of a
sudden it just stops allowing you to copy files to it using normal ways.

Yet all web services running on it for development, never have problems,
people can access and update with no issues.

Also using ftp works without any error, you then try normal file copy it
errors as mentioned before. Use FTP again, and it works with no problems.

Really isn't looking like a network issue, as it is the only server with
this problem, differant NICs have been tried, differant cables, differant
ports, differant switches, and all combinations of duplex, half duplex, 10
and 100 mb. None of which resolve the error.

Had to reboot server after bios update, so problem gone for now
"temporarily".

We used a sniffer on it earlier, and were practically no collisions or
dropped packets.

To me it is looking more like server service connections cannot allocate
sessions, the thread that is responsible for allocating and cleaning up all
sessions, is blocked by a device driver during cleanup, at the same time
someone is trying to copy/move files around. Which should generate a 2022
error in eventviewer, which server doesn't have, hence why I came here, to
see if anyone had any other ideas.