📎 AI Summary:
The thread is about mapped network drives that usually work via a stored/short UNC-style mapping but, sometimes, require entering the full server/share name instead. The key questions center on why the mapping intermittently fails despite basic checks (ports working, ping succeeds, and no obvious permission/lockout issues) and why it appears across servers from Windows Server 2003/2005 through 2008/R2. The overall sentiment from the initial post is troubleshooting-focused, and the discussion implies the cause is likely name-resolution or mapping-path handling rather than connectivity or access rights.
Thread Author
When mapping network drives for my work and co-workers I use Link Removed and ninety nine percent of the time this works. Randomly the network drives will require there full name as to be Link Removed would there be a reason for this? The ports all seem to be in working order, no rights or permissons lock outs, able to ping it. It is not consistant with a certain drive either, we are running server OS ranging from Windows Server 05 -Windows Server 08 R and R2. All the computers in the Office are running Windows 7 Professional.

Any suggestions on why this is happening would be helpful, so I can stop it from happening.

 

Click to expand...
You must log in or register to reply here.