<div>
If you open port 445, you may be able to connect using the server IP address. Try that. Also open ports 137-139 if you want to access the share by name since they are used for NETBIOS name resolution.<br />
<br />
Note that this is what I have used in the past: 137/UDP, 138/UDP, 139/TCP and 445/TCP
</div>


<div>
its not a port issue, she is connecting fine and can access a share without security on it. Also I can connect from my office as her with not issues
</div>


<div>
<blockquote>
she is connecting fine and can access a share without security on it
</blockquote>
It would have helped if you had provided that information in the original question. <br />
<br />
In this situation, I would use a network monitor to examine what is happening client-side and server side. It would appear to be an authentication or trust issue. There are probably some other Windows experts here who can offer more directed advice.
</div>


<div>
If turning off the firewall worked, then it is going to be a port issue. It's generally better to determine what the ports are in question rather than effectively leaving all ports open. But, at least you have it working now.
</div>


<div>
<div class="content wysiwyg-content">
Using Microsoft VPN server\client on Server 2012. The 2012 server is in the cloud, I have set up the VPN server and I'm able to connect to the VPN, I can ping the VPN server, I can RDP to the server when connected to the VPN but I can not access a share on the server. This is a single server (non-domain) solution that remote clients need to access a database on this server. Port 139 is open, The VPN clients get an IP address on the same subnet as the server. when trying to access the share via IP \\999.999.99.99\share &nbsp;I get Windows cannot access never prompts for user id. I have checked share and NTFS rights and the VPN users should have access. I get same results on Win10 VPN client and Win 7 VPN client
</div>
</div>


Using Microsoft VPN server\client on Server 2012. The 2012 server is in the cloud, I have set up the VPN server and I'm able to connect to the VPN, I can ping the VPN server, I can RDP to the server when connected to the VPN but I can not access a share on the server. This is a single server (non-domain) solution that remote clients need to access a database on this server. Port 139 is open, The VPN clients get an IP address on the same subnet as the server. when trying to access the share via IP \\999.999.99.99\share  I get Windows cannot access never prompts for user id. I have checked share and NTFS rights and the VPN users should have access. I get same results on Win10 VPN client and Win 7 VPN client

Conencted to VPN cant access shares

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

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.

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.