Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 8 subscribers
  • Views 3943 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable To Access Drives Mapped through GPO over L2TP VPN Connection

Houndstooth

Hello,

This issue is only affecting users connecting to our UTM's L2TP VPN connection on Windows devices. Users are able to establish the connection, but when they do so, they lose access to network drives that have been mapped via Group Policy. This issue only occurs over VPN. When the device connects to the domain on our LAN, the drives maps as expected.

As a workaround, I have remounted the drives and assigned them another letter to be used while using the VPN. Very possible this is a Microsoft issue, but I wanted to check with you all as the issue is only occurring over the VPN.

The error message is 

"An error occurred while reconnecting ":I ......." (path to drive) 
Microsoft Windows Network: 
The local device name is already in use."
The connection has not been restored"
I have taken the troubleshooting steps suggested in this thread, but the issue persists:
Thanks for any guidance you can provide.


This thread was automatically locked due to age.
Parents
  • FormerMember
    0 FormerMember

    Hi ,

    Thanks for reaching out to the Community! 

    Have you configured the domain name on the client side? I'd suggest you run a packet capture and review the packet-filter logs while trying to access the mapped drive. 

    Thanks,

Reply
  • FormerMember
    0 FormerMember

    Hi ,

    Thanks for reaching out to the Community! 

    Have you configured the domain name on the client side? I'd suggest you run a packet capture and review the packet-filter logs while trying to access the mapped drive. 

    Thanks,

Children
  • 0 in reply to FormerMember

    H_Patel: Thank you so much for this idea. I have a couple clarifying questions:

    How might I got about configuring the domain name on the client side? Or confirming that these settings have been set correctly?

    Would establishing a port mirroring session using Wireshark be the best way to perform a packet capture?

    Thanks again for all your assistance.

  • 0 in reply to Houndstooth

    If you're not familiar with tcpdump, you might be interested in looking at A Tcpdump Tutorial and Primer by Daniel Miessler.

    Just to eliminate a Windows firewall issue in your server, experiment with a NAT rule like:

         SNAT : Pool (L2TP) -> {TCP 139&445 & UDP 137&138} -> {server with a share} : from Internal (Address)

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Unfiltered HTML