Solved Closed

Not able to Access map drives over VPN

Hello everyone,

I am having trouble seeing my map drives over my VPN. When I am at the server location, I have no problems. But when I go to any of my remote locations, I can log into my laptop, But I can't access my map drives over my VPN. Can anyone point me into the right location?

Running Server 2012 standard
And using sonicwall as my firewall and vpn
14 answers Last reply Best Answer
More about access map drives vpn
  1. what error do you get? are you able to ping your map drive Location when your on a remote location?
  2. leonelurquiza said:
    what error do you get? are you able to ping your map drive Location when your on a remote location?


    I can ping are server just fine. I can't ping the map drives because they can't load. I am running logon scripts. So my maps won't even load.
  3. how do you currently have your shares map? can you share your logon script
  4. leonelurquiza said:
    how do you currently have your shares map? can you share your logon script


    I currently have each profile set to look for a specific one, since I have 4 different logon scripts. So I basically I do this, I go to the user profile, then profile tab, then I put the logon script name in the login script spot.
  5. CisloIT said:
    Hello everyone,

    I am having trouble seeing my map drives over my VPN. When I am at the server location, I have no problems. But when I go to any of my remote locations, I can log into my laptop, But I can't access my map drives over my VPN. Can anyone point me into the right location?

    Running Server 2012 standard
    And using sonicwall as my firewall and vpn


    Making some assumptions; this is probably a DNS resolution issue.

    When you log in at a remote location I'm presuming there is no domain controller available to validate your logon so you are using cached credentials. I'm also presuming that your login script isn't running at the remote locations though your network drives are still mapped from your last log in at the server location. You are then connecting your VPN up and when you try to access the network drive it doesn't work and maybe throws an error about it being unavailable.

    If the above is the case, then your problem is that the VPN connection doesn't have a DNS suffix associated with it. So when your computer tries to resolve your mapped drives, it fails because it doesn't realise that your single name references are intended for the domain.

    If you are using a VPN software other than the built in windows client you'll need to look up where to supply the DNS suffix. If you are using the windows client, then open the properties of your VPN connection. On the Networking tab select IPv4 and hit properties. Then Advanced. On the DNS tab supply your companies domain name in the 'DNS suffix for this connection' box - e.g. mycompany.com, whatever.local Reconnect and you should be good.

    If this isn't the issue, please try to provide more information regarding errors and specifics of what happens.
  6. noise said:
    CisloIT said:
    Hello everyone,

    I am having trouble seeing my map drives over my VPN. When I am at the server location, I have no problems. But when I go to any of my remote locations, I can log into my laptop, But I can't access my map drives over my VPN. Can anyone point me into the right location?

    Running Server 2012 standard
    And using sonicwall as my firewall and vpn


    Making some assumptions; this is probably a DNS resolution issue.

    When you log in at a remote location I'm presuming there is no domain controller available to validate your logon so you are using cached credentials. I'm also presuming that your login script isn't running at the remote locations though your network drives are still mapped from your last log in at the server location. You are then connecting your VPN up and when you try to access the network drive it doesn't work and maybe throws an error about it being unavailable.

    If the above is the case, then your problem is that the VPN connection doesn't have a DNS suffix associated with it. So when your computer tries to resolve your mapped drives, it fails because it doesn't realise that your single name references are intended for the domain.

    If you are using a VPN software other than the built in windows client you'll need to look up where to supply the DNS suffix. If you are using the windows client, then open the properties of your VPN connection. On the Networking tab select IPv4 and hit properties. Then Advanced. On the DNS tab supply your companies domain name in the 'DNS suffix for this connection' box - e.g. mycompany.com, whatever.local Reconnect and you should be good.

    If this isn't the issue, please try to provide more information regarding errors and specifics of what happens.


    Which I did not think about. I am having the server do all the DNS for everyone. I don't have any other additional software. So do I have to program the firewall at my remote location to look for the DNS on the server?
  7. Hi again.

    Is your laptop initiating the VPN or is the firewall at the remote location? I'll assume the laptop is so my previous comments should apply.

    "If you are using the windows client, then open the properties of your VPN connection. On the Networking tab select IPv4 and hit properties. Then Advanced. On the DNS tab supply your companies domain name in the 'DNS suffix for this connection' box - e.g. mycompany.com, whatever.local Reconnect and you should be good."

    You could also test if this is the problem before making the change by pinging the server.

    At the command prompt (start/run/cmd)

    ping myserver
    ping myserver.mydomain.com

    Where myserver is the name of the server where the network shares are located; and my domain is your domain name. The first should fail to respond, the second should respond proving that it is a DNS issue.
  8. noise said:
    Hi again.

    Is your laptop initiating the VPN or is the firewall at the remote location? I'll assume the laptop is so my previous comments should apply.

    "If you are using the windows client, then open the properties of your VPN connection. On the Networking tab select IPv4 and hit properties. Then Advanced. On the DNS tab supply your companies domain name in the 'DNS suffix for this connection' box - e.g. mycompany.com, whatever.local Reconnect and you should be good."

    You could also test if this is the problem before making the change by pinging the server.

    At the command prompt (start/run/cmd)

    ping myserver
    ping myserver.mydomain.com

    Where myserver is the name of the server where the network shares are located; and my domain is your domain name. The first should fail to respond, the second should respond proving that it is a DNS issue.


    The firewall is doing the VPN.
  9. So you have a firewall at your remote location, this is performing a site to site VPN? You aren't 'doing' anything on your laptop to begin the VPN session?
  10. noise said:
    So you have a firewall at your remote location, this is performing a site to site VPN? You aren't 'doing' anything on your laptop to begin the VPN session?


    You are correct. I am not having the laptop start the VPN from site to site.
  11. OK in that case can you perform the ping test I suggested?

    ping myserver

    and

    ping myserver.mydomain.com

    You'll need to substitute the correct names in.

    If the first one fails but the second one replies, then this si still a DNS issue - but you'll need to alter your login script/mapped drives to map against the full name of the server rather just the single name.
  12. noise said:
    OK in that case can you perform the ping test I suggested?

    ping myserver

    and

    ping myserver.mydomain.com

    You'll need to substitute the correct names in.

    If the first one fails but the second one replies, then this si still a DNS issue - but you'll need to alter your login script/mapped drives to map against the full name of the server rather just the single name.


    Sorry It took me so long to replay back. How would script the drives to do that?
  13. Best answer
    You don't need to alter any scripts yet, you just need to perform the ping test from the command prompt.

    Start / Type 'cmd' in the box and hit 'enter' on the keyboard.

    In the command prompt window (the black box which appeared) type:

    ping myserver

    You need to replace myserver with the name of the server which the network drives are mapping to.

    Note the results (replies)

    Then do the same with:

    ping myserver.mydomain.com

    Where mydomain.com is the name of your active directory domain.

    Again note the results and respond back here.
  14. If you can PING the remote destination - try using ip / or its dns name.

    I had to delete all existing network drives by using the following command from command prompt: net use * /delete
    Then I rebooted the computer, connected to the vpn and mapped the network drive again using different credentials- and vioalla, it works!


    ***Remember: Give back to the community, mark this answer if it helped you!***
Ask a new question

Read More

VPN Business Computing Servers