Specified network name is no longer available??

  • Thread starter Thread starter Ben Blackmore
  • Start date Start date
B

Ben Blackmore

Hi,

We are experiencing some strange problems, we have a windows 2000 server,
running AD with a hard disk that has a 'public' share on it (mapped as P:
drive). Everyone in the company has full access to this share. Everything
has been working fine until this morning, when we've had several reports of
people not being able to access the public share, they receive the error
"The Specified network name is no longer available".

Has anyone got an idea why this is happening? I can't see anything wrong,
the share has full control for everyone, there are no denies in place, and
the users are logging onto the domain correctly.

Any help greatly appreciated.

Ben
 
This could be from any number of causes, and we really need a bit more info
to get a clearer picture of the problem, but take a look at the following to
see if it helps;
325487 How to Troubleshoot Network Connectivity Problems
http://support.microsoft.com/?id=325487

821464 Network Clients Cannot Connect to Network Shares
http://support.microsoft.com/?id=821464

Other things to investigate include;
1) errors in the clients event logs indicating possible secure channel,
name resolution, HW, or other problems.
2) are the clients affected by this all on the same subnet, switch, router,
etc that might indicate HW or configuration issues.
3) are all users, or just some users, etc being affected by #2.
4) is their connectivity random or consistantly failing, and when they are
unable to connect to that share are they still able to view/connect to other
shares on that server or another server. (manually not using the script -
mapping through either browsing, net use, or expolrer to map drive)
5) are the affected users all running the same OS or different.
6) what that happens are they still able to ping the server by dns name and
get a reply.


--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
 
David Brandt said:
This could be from any number of causes, and we really need a bit more info
to get a clearer picture of the problem, but take a look at the following to
see if it helps;
325487 How to Troubleshoot Network Connectivity Problems
http://support.microsoft.com/?id=325487

821464 Network Clients Cannot Connect to Network Shares
http://support.microsoft.com/?id=821464
Click to expand...

I'll have a look at those links, and test some of the other questions you
asked, these are the answers to some of them for now
Other things to investigate include;
1) errors in the clients event logs indicating possible secure channel,
name resolution, HW, or other problems.
Click to expand...

Will check this on the client PCs
2) are the clients affected by this all on the same subnet, switch, router,
etc that might indicate HW or configuration issues.
Click to expand...

All users in our network use 255.255.248.0 as a subnet, the users affected
are on different switches.
3) are all users, or just some users, etc being affected by #2.
Click to expand...

So far only a few
4) is their connectivity random or consistantly failing, and when they are
unable to connect to that share are they still able to view/connect to other
shares on that server or another server. (manually not using the script -
mapping through either browsing, net use, or expolrer to map drive)
Click to expand...

It seems to be only our P: drive (\\server\public) other drives on the same
server and even same volume are fine, i.e. \\server\users\jbloggs or
\\server\accounts can be accessed fine by the user, and are on the same
volume as the public share!
5) are the affected users all running the same OS or different.
Click to expand...

All users are running win2000 SP4
6) what that happens are they still able to ping the server by dns name and
get a reply.
Click to expand...

Will try this from the client machines, but I'd guess they would be able to
ping the server, as they can connect to other shares and can logon to their
account.

Cheers

Ben
 
Well I've visited the PCs with the problems, and I can ping the server from
them! I have copied the following events from the application log, the
security log was empty.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 13/01/2004
Time: 12:15:19
User: NT AUTHORITY\SYSTEM
Computer: GRICHARDS-L-2K
Description:
Windows cannot access the registry information at
\\triumph-international.gb\SysVol\triumph-international.gb\Policies\{0973937
9-D47E-43FA-BC87-BF3D7E185806}\User\registry.pol with (1351).


Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 13/01/2004
Time: 09:50:58
User: NT AUTHORITY\SYSTEM
Computer: GRICHARDS-L-2K
Description:
Windows cannot determine the user or computer name. Return value (1722).


Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 13/01/2004
Time: 08:35:06
User: NT AUTHORITY\SYSTEM
Computer: GRICHARDS-L-2K
Description:
Windows cannot access the registry information at
\\triumph-international.gb\SysVol\triumph-international.gb\Policies\{0973937
9-D47E-43FA-BC87-BF3D7E185806}\User\registry.pol with (1351).
 
Marina Roos said:
Go to www.eventid.net and look up the errormessages there.
Click to expand...

After reading that and doing 'NET HELPMSG 1351' I think there is a problem
with a profile on our domain controoler, net help says "Configuration
information could not be read from the domain controller, either because the
machine is unavailable, or access has been denied."

So I removed the PC from the domain then added it again, this fixed 1 of the
workstations, however, I did it on another and it worked for 5 minutes, then
the original error message popped up. As to weather it will happen to the
other PC again we will have to wait and see.
I can't see why its not doing it to all machines, or to all shared drives on
that volume, it doesn't make sence! I'm going to remove the workstation from
the domain now then delete the machine profile, then add it again!
 
Marina Roos said:
Are all servers and clients fully patched?
Click to expand...

Yes, I have setup a SUS server, so updates/patches are automatically
downloaded and installed.

Last night I removed the machine from the domain then renamed it, and added
it again, and it seems to be working for the moment. What I can't understand
is why its just the P: drive (public share) as everyone has full control
over it. If it was another drive, i.e. H: (home) or G: (group) which has
user restrictions on it I could understand, but its not they have access to
these fine, and all drives are on the same physical volume on the server.

One thing these machines do have in common is they are all Toshiba laptops,
although different models, one is a satellite pro 6000, other is a protégé
3110. I have checked Toshiba's site, and updated any drives/patches.

They have all been working fine for the past 6 months, until Monday
afternoon, when suddenly we had these 2 machines with in hours of each
other. No changes were made on the server, or the machines.

Ben
 
Back
Top