Mapped Network Drives in Remote Desktop Connection

I often use Remote Desktop Connection to get into my server to access a SQL database.  Server is old (Windows Server 2003 R2 Standard Edition).

When I RDC into the server from my work laptop, I can get in fine, access the SQL database fine and get into all the mapped network drives fine.

When I RDC into the server from my home computer, I can still get in fine, still access the SQL database fine but I can't get into the mapped network drives.  I get the message that the drive is not accessible and the device is not connected.  When I try to re-map the drives, it says I don't have permission to use the network resource.

Is there something I can update/change on either the server-side or my home computer so that I can access the network drives?

Who is Participating?
pony10usConnect With a Mentor Commented:
That would make sense. If you are not logged into the domain then you are not using the domain's DNS server so it wouldn't recognize the name of the system with the share. You should be able to get around that by adding an entry into the local host file.
This sounds like a permissions issue.  Are you using the same credentials at both locations?  


Otherwise I would check ACL's in the firewall/router/etc.

on MSTSC => options => Local resources  => Local Devices => Drives
Phish_HeadAuthor Commented:
It was due to not being logged into the domain.  When using my work machine on the network, I could see the drive as \\shareddrive\share; when not on the network, I had to use the IP of the drive.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.