We use the Global VPN Client to connect to our network from our homes, but for some reason I never got the NetBios names to pass through the VPN connection, so we use the IP address \\192.168.16.10\sharedfile (thats the server with the shares). So this works for all users on all computers from many different locations, except for a newly
NETBIOS over VPN - NETGEAR Communities NetBIOS transport over TCP protocol is history, SMB protocol stack is the standard for hmmmm a long time. NetBIOS discovery and name resolution: This is IP broadcast based and would create a lot of noise over low bandwidth links - this would make it possible that (again old) devices would become visible in the Network Neighborhood e.g. on the HTTP File Server secure remote access without VPN or In today’s environment, Security is of even a greater concern since enabling SMB share access even over a VPN can lead to malware encrypting files and security vulnerabilities inherent in the Windows File Sharing protocol (SMB) making traditional remote access high risk.
Interface: VPN VPN Type: L2TP over IPSec Service name: VPN (L2TP) 2. Adjust the newly created L2TP over IPsec interface. System Preferences > Network > VPN L2TP . Configuration: Default Server Address: 203.0.113.1 Account Name 3. Add the authentication settings. System Preferences > Network > VPN L2TP > Authentication Settings
SMB 3.0.0 added Multipathing, which would explain it, but my 2012 hosts have that. I jumped over SMB 3.0.2 to 3.1.1 with W10/2016, but as far as I can tell it was only encryption and security improvements, no real performance issues.
Reducing MTU value to fix slow CIFS/SMB over VPN. : sysadmin
Mar 02, 2020