PCNNY
asked on
Mapped network drive not accessible
I have a Windows SBS 2008 domain. All client PCs are running Windows 7 Pro 32 Bit.We have setup drive mappings via the group policy and have 4 drives mapping to all users on the network. Two of the users cannot access one of the drives being mapped. The drive appears in their list of available drives, but it reports the following message when we attempt to open it:
F:\is not accessible - The handle is invalid
I have verified that there are no other drives taking that drive letter and that the users have full permissions to the directory and all child objects within it. I have no idea what is causing this issue. I have also disabled the firewall on the end users PCs, but that did not fix the problem.
F:\is not accessible - The handle is invalid
I have verified that there are no other drives taking that drive letter and that the users have full permissions to the directory and all child objects within it. I have no idea what is causing this issue. I have also disabled the firewall on the end users PCs, but that did not fix the problem.
Are the users mapping OTHER drives under different usernames to the same server?
ASKER
all users map the same drives. I have been notified that nobody can access the drive now. The only way I can view its contents is by loging in directly into the server as admin and opening the directory. Attempting to access via any PC over the network results in the error message I specified.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I did that. No difference. When I try to access the mapped drive over the network, I get:
directory name is invalid
directory name is invalid
Are you using a script to connect the network drives? If so have you tried to map it manually?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I tried everything, and the only thing that worked was eventually rebooting the server. I had to wait until after hours of course, but as soon as it came back up, the drive was accesible.
ASKER
The problem was solved after trying all recommended procedures and rebootingn server.
glad you eventually got it figured and thanks for the points!
Good stuff, thanks for the points - glad you are back up and running.
Anything in the windows event logs ?
I hope this helps !