I have three servers, who another Sys Admin worked on, that no one can access any of the Administrative Shares (c$, d$, IPC$) on. I get "The Network Path was not found". Trying to get info from the SA on what was done is like trying to speak tongues with them. Here is what I got.
- I am in the Administrator Group on the Box
- I have access this computer from the network rights
- I can terminal server into the box and access the c and d drives interactively "as I am not trying to get to them via the share" at that point.
- There is no registry setting to preclude accessing the admin shares IE (HKEY_Local_Machine\System
- File and Print Services are running
- Windows Firewall is NOT enable nor running
- Net Time to these servers fail (Z:\>net time \\servername
System error 53 has occurred.
The network path was not found.
- Ping and NBTSTAT work fine against these servers
- There are no errors in the event logs even close to this problem
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Ryansoto: I get the same thing by just putting in the \\servername. Additionally, if I add a network printer to this server (after starting the spooler svc on this server) I do not see it either when using the UNC path \\servername. Net Use, Net Time ... none of them work. I just found out this individual had gone into the registry and created two D:word values (HKEY_Local_Machine\System
(HKEY_Local_Machine\System
Then she noticed the Shares disappeared and set the values to 1 for each dword. Then the shares reappeared but could not be access. She had rebooted the server 3 times and then came to us. Removing both of these dword values also has no affect.
I had already looked at both of these articles. I cut their recommendation and put it below. This did not fix my issue. When I am on the Server, I see all the shares. When I do a "net use" from my workstation to these shares on the affected server I get the following:
Z:\>net use \\servername\c$
System error 67 has occurred.
The network name cannot be found.
Yet, I can ping the server by name, do a NBTSTAT and it resolves.
Microsoft KB Information
Examine the AutoShareServer and AutoShareWks registry values to make sure that they are not set to 0:
Click Start, click Run, type regedit, and then press ENTER.
Locate and then click the following registry sub-key: HKEY_LOCAL_MACHINE\System\
If the AutoShareServer and AutoShareWks DWORD values in the LanmanServer\Parameters sub-key are configured with a value data of 0, change that value to 1.
Note If these values do not exist, you do not have to create them because the default behavior is to automatically create the administrative shares.
Quit Registry Editor.
Restart the computer. Typically, computers that are running Windows Server 2003, Windows XP, Windows 2000, or Windows NT 4.0 automatically create the administrative shares during startup.
After the computer restarts, verify that the administrative shares are active. To examine the shares, use the net share command. To do this, follow these steps:
Click Start, click Run, type cmd, and then press ENTER.
At the command prompt, type net share, and then press ENTER.
Look for the Admin$, C$, and IPC$ administrative shares in the list of shares.
After digging further into this server, we identified that the SA team had installed Symantec Endpoint Software on that system. This installed a firewall which was blocking access to the hidden shares on that system. The answers submitted to this article would most certainly have fixed the issue had it not been an errant installation of the firewall. We re-installed the software correctly and it fixed the issue. The SAs had originally stated they had made no recent modifications to the system. I am guessing installing software did not meet their critera of a modification.
Business Accounts
Answer for Membership
by: ryansotoPosted on 2009-01-06 at 11:16:03ID: 23307922
did you try with server name\c$
Try with an Ip address and see