Specified network name is no longer available
HELP! Back at work after the weekend - nothing changed from our perspective, suddenly none of us can access our LACIE NAS. We all use a mapped Z: drive to access it and have been happily doing that for literally years - today when we try and access it we get a SPECIFIED NETWORK NAME IS NO LONGER AVAILABLE error. Any ideas as to how to start diagnosing the problem? Thanks Ed.
Darius Ghassem
Can you ping the device? Can you connect by going to run typing \\IP address?
Here are some troubleshooting steps.
http://support.microsoft.com/kb/325487
http://support.microsoft.com/kb/961293
http://support.microsoft.com/kb/325487
http://support.microsoft.com/kb/961293
ASKER
Hello - thanks for getting in touch.
PING is OK.
\\IP ADDRESS = UNSPECIFIED ERROR: 0x80004005
I can connect to the share via FTP (it supports both FTP and Windows networking access) and I can see the files. So at least the data is still there.
PING is OK.
\\IP ADDRESS = UNSPECIFIED ERROR: 0x80004005
I can connect to the share via FTP (it supports both FTP and Windows networking access) and I can see the files. So at least the data is still there.
What OS are clients running and server running?
Make sure that you have removed any AV running on server for testing.
ASKER
Hi again
The server is a LACIE network attached storage device, so I'm not sure what OS it's running. The clients are a mixture of Win 7 and Win Vista plus a Mac which connects using SMB (it is having problems seeing the share as well).
Ed
The server is a LACIE network attached storage device, so I'm not sure what OS it's running. The clients are a mixture of Win 7 and Win Vista plus a Mac which connects using SMB (it is having problems seeing the share as well).
Ed
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Disable IPv6
ASKER
>> Are you fully patched on the Vista machines? and Windows 7 machines?
Yes we are.
>> If you reboot the LACIE is the problem still there?
Yes it is.
>> Disable IPv6.
Not sure how to do this - no on / off switch in the network adapter properties. In any case, why would IPv6 suddenly cause an error like this, when it has been working OK for so long??
Yes we are.
>> If you reboot the LACIE is the problem still there?
Yes it is.
>> Disable IPv6.
Not sure how to do this - no on / off switch in the network adapter properties. In any case, why would IPv6 suddenly cause an error like this, when it has been working OK for so long??
Uncheck IPv6 for testing.
ASKER
Guess what - not trusting the remote reboot feature and actually going to the rack and pulling the power cord did the trick. It's back again. Thanks for your help.
ASKER
Check that a remote reboot has actually happened - go to the device and pull the power cord.