Hello All, Where I work we are having a peculiar problem with mapping one of our network shares as a mounted drive. Before I go any further I will give a little background info on our setup. We are running Windows Server 2008 R2 on our servers which users connect to via Oracle's Sun Ray Connector. Upon login we have a script that will use the current users credentials to map 3 network drives: one for personal storage, one for group storage, and one for software installations (small ones) and links to installer packages that they are allowed to install on their personal computers. Recently we have been getting reports of the group storage space not mapping at login and when we try and manually map said share we get the following error: Windows cannot access \\server\share Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose. Error code: 0x80070035 The network path was not found. Now for some reason this problem occurs randomly across our 49 servers that our users access and need this particular drive. For example, one week we can logon and off of all the servers and see that the problem is on server x, y, and z but the next week we logon to all of the servers again (without a reboot on any of them) and only server e will have the problem. Another observations that we made was that you can ping the server the that hosts the drive and can even go to the root of the shared folder by typing \\server\ into an explorer window but once you try and double click on the shared folder it gives the error above. A reboot seems to fix this problem but we don't want to have to reboot our servers every time we see that one is having troubles with this drive as some users run long simulations that can take days at a time. Thanks for any help that you can give. If you need more information just let me know and I will see what I can do. Gerad Bottorff
1) To check if a third party application is a cause, Boot in Safe Mode with Networking option and check if this issues still persists, if the issue is resolved, you need to perform a Clean Boot by following the steps mentioned in the following KB article to narrow down the exact source and isolate it: KB 929135 2) No firewall or security software blocks sharing The issue may be caused also by your security program such an anti-virus or a Windows Firewall /Defender which might have conflicting settings as to not to perform certain tasks. I suggest that you temporary disable the anti-virus and firewall and check the result again. You would need to turn on the security programs again which you had disabled. 3) Password Protected: OFF (unless you want to set up identical usernames and passwords on ALL computers in your Network) or you can try creating the same username and password on both the computers. Try pinging IP address of the computer from the other but not by machine name (PING each computer by IP address, and if successful, PING by name. You can obtain the IP address of a computer by opening a command prompt (DOS window) and typing IPCONFIG) 4) Ensure NetBIOS over TCP/IP is enabled on both computers 1) Go to “Control Panel - Network Connections”. 2) Right-Click on the connection and click Properties. 3) Find Internet Protocol (TCP/IP) Version 4 in the list. 4) Click Properties, and then click Advanced. 5) On the Advanced TCP/IP settings windows, go to “WINS” tab. 6) Under NetBIOS setting, click Enable NetBIOS over TCP/IP, and then click OK. 5) Disable IPv6 --- ONLY when in an ipv4 environment If the issue persists due to IPv6 deployed you might need to follow the steps mentioned in the KB article: How to disable certain Internet Protocol version 6 (IPv6) components in Windows Vista, Windows 7 and Windows Server 2008 Reference KB Article: 929852 If you have come to this point, then it indicates WINS or DNS lookups, even possibly the NBT setting in DHCP, more details about your setup is required and could be to do with your network equipment. protocol support/packet collisions.