<div>
Few thoughts, can you connect to<br />
<br />
\\x.x.x.x\share using ip address, what about \\server.addomain.local\sh<wbr />are. ?<br />
<br />
Does ipconfig /all show it is using internal dns servers once connected?<br />
<br />
Can they ping the server name remotely, different vlan maybe they haven't got access to from their vpn profile?<br />
<br />
Steve
</div>


<div>
Are all shares on the same server?
</div>


<div>
Qlemo, not all shares are on the same server however, the inaccessible share is on the same server as two shares they can access.<br />
<br />
Steve Knight, I will check what you've suggested this afternoon when I have access to one of the two questionable computers and respond.
</div>


<div>
Also have a look in in explorer whether it shows those or some shares when you you just browse to the server name with \\server name
</div>


<div>
<p>Being that you stated the user can access the folders with EVERYONE permission has me to believe that &nbsp;there is no security established when connecting via vpn.</p><p>&nbsp;</p><p>Is the user prompted to enter credentials when trying to access the mapped drive? &nbsp;</p><p>Have you tried running Windows Explorer as that user and then connect to the mapped drive. &nbsp;</p><p><br></p>
</div>


<div>
You could also confirm the SMB version. &nbsp;I don't recall if Windows 10 came with 1.0 by default. &nbsp;Just check in the windows features, if the share is on an older OS it may not support a higher version of SMB
</div>


<div>
If W10 has been upgraded from earlier Windows releases or an older W10 with SMBv1 enabled, it remains active. A fresh W10 install does not support SMBv1 by default.<br />
But I don't think that is an issue here anyway - other shares on same server work, and SMB version does not depend on the share you chose.
</div>


<div>
@Qlemo Good point, I missed that some shares worked, I saw they were on different servers.
</div>


<div>
Thanks to all of you giving this your attention. Please see my responses below.<br />
<br />
I'm taking the Surface out of the equation. Upon closer examination, when the user stated he couldn't access his H: drive when connected to the VPN, I assumed it was the same problem that I was troubleshooting on the XPS. Having actually looked at his Surface this afternoon, he was &nbsp;saying the drive mapping was missing when he connected to the VPN. That has been resolved and he can access all resources.<br />
<br />
As for the XPS...<br />
<b>Steve Knight:</b><br />
\\x.x.x.x\share using ip address, what about \\server.addomain.local\sh<wbr />are. ? <b>Both work</b><br />
<br />
Does ipconfig /all show it is using internal dns servers once connected? <b>Yes</b><br />
<br />
Can they ping the server name remotely, different vlan maybe they haven't got access to from their vpn profile? <b>I can successfully ping the server remotely by name and the correct IP address is reflected</b><br />
<br />
<b>Browsing to \\server name displays all relevant shares</b><br />
<br />
<b>yo_bee</b> permissions are being properly established as illustrated by her ability to access this mapping when using a different laptop connected to the VPN and her inability to access folders to which she does not have permission in that same session.<br />
<br />
<b>Bryan Shaper</b> this occurs with drives on the same server as Qlemo stated.
</div>


<div>
Ok so there is no main comms issue (as you had said already by saying other shares ok) so that leaves you one share.<br />
<br />
So what do you see - presume can see the drive mapped ok, does it show a red X or connected ok, if you click it can you open the drive but not the files in it or do you see an empty share or get an &quot;access denied&quot; message?<br />
<br />
You said it worked with ip and name, so can you get to the same way as that share is mapped from the pc at the time, e.g. from cmd prompt do:<br />
<br />
net use<br />
<br />
and copy/paste the share path and do:<br />
<br />
start &quot;&quot;&nbsp;&quot;\\server\sharename&quot;<br />
pushd &quot;\\server\sharename&quot;<br />
dir<br />
<br />
If you can get tose files from this pc while on the vpn using any of those?<br />
<br />
Can you check the (other) file shares at the point when this user is accessing them remotely from the server and see what account is showing up as accessing them.<br />
<br />
Are we talking permissions on the share or ntfs causing the issues. &nbsp;Can you temporarily add Everone to the share permissions and a directory in the root of that share with everyone permissions for instance?<br />
<br />
Have a look in cmdkey /list and/or credential manager for any saved credentials that have been put in there somehow for that box?
</div>


<div>
if I understand correctly, the issue can be reduced down to <br />
<br />
server with one share that allows everyone, and one share that only allows named users<br />
when on the LAN, the user on the laptop can access both shares<br />
when on VPN, the user on the laptop can only access the &quot;everyone&quot; share<br />
if a different laptop is used, the user can access both shares when on VPN<br />
<br />
as the everyone share can be accessed, L3 routing and DNS would appear to be working.<br />
as both shares can be accessed on the LAN it should not be a permissions issue<br />
as both shares can be accessed on the LAN it should not be a stored credentials issue<br />
as both shares can be accessed with a different laptop, it is not an issue with the VPN server<br />
<br />
when the user is on the LAN, a domain logon happens, when the laptop is not on the LAN, and the VPN is not started before logon, cached credentials are used. I would guess that kerberos is failing for the laptop when on VPN, and that the access to the &quot;everyone&quot; share might be using the guest account on the server.<br />
<br />
some tests<br />
<br />
check to see that the guest account has not been enabled on the server<br />
try a different user account on the laptop when connected over VPN (add the account to the share and ntfs permissions)<br />
create a share that is set for authenticated users instead of everyone and see if that share can be accessed
</div>


IT Guy

edpowell19

<div>
<div class="content wysiwyg-content">
I have a laptop that can access mapped drives that are shared with Everyone via the VPN, but cannot access a drive with permissions only for the logged in user. It works fine when in the office connected to the LAN, but not via the VPN.<br />
I replaced the user's laptop and the one I gave her works just fine so I know it's not the network or VPN. The laptop in question is a Dell XPS 15, Win10 Pro 1903, Core i7, 32GB RAM, SSD, connecting to a Sonicwall TZ400 using the Global VPN Client. This laptop and a Surface are the only machines experiencing this problem. I can connect from other PCs as either user and access all their drives.<br />
<br />
Before I give up and reset Windows, I'd love to know what the issue is. Any ideas?
</div>
</div>


I have a laptop that can access mapped drives that are shared with Everyone via the VPN, but cannot access a drive with permissions only for the logged in user. It works fine when in the office connected to the LAN, but not via the VPN.
I replaced the user's laptop and the one I gave her works just fine so I know it's not the network or VPN. The laptop in question is a Dell XPS 15, Win10 Pro 1903, Core i7, 32GB RAM, SSD, connecting to a Sonicwall TZ400 using the Global VPN Client. This laptop and a Surface are the only machines experiencing this problem. I can connect from other PCs as either user and access all their drives.

Before I give up and reset Windows, I'd love to know what the issue is. Any ideas?

Can access MOST network drives when connected to the VPN

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

A virtual private network (VPN) is a network that uses a public telecommunication infrastructure, such as the Internet, to provide remote offices or travelling users access to a central organizational network securely. VPNs encapsulate data transfers using secure cryptographic methods and other security mechanisms to ensure that only authorized users can access the network and that the data cannot be intercepted.