When I click Diagnose it says "The device or resource is not setup to accept connection on port 'The File and Printer Sharing (SMB)' " - but that port is allowed and Windows 7 computers connect just fine.ĭNS also seems to be fine as trying to access the server with \\server, \\server.domain, and \\IPAddress all do not work when connected to the VPN and again Windows 7 computers connect to the file share through the VPN by just typing \\server. However the Windows 8 or 10 client computer responds saying "CannotĪccess \\server".
How to properly set up pia vpn windows 10 windows 10#
When a Windows 10 computer tries to connect to the file share while connected to VPN, the file share does have a firewall log entry that shows that computer is reaching the server. Windows 8 and Windows 10 computers accessing SMB connected via VPN.All computers can RDP to the file server when connected to VPN (when allowed during testing).All Windows 7 computers accessing SMB connected via VPN as well as when connected to the internal network.All computers can connect to the file share when connected to the internal network.The server's Windows firewall is set to allow our internal network subnets as well as the VPN network subnet.
The odd things is that all Windows 7 computers can connect to the file share internally and while connected to the VPN offsite. To our internal network - it is just when connected to the VPN that the shares are not accessible. All shares are accessible from the same computer when connected We seem to be having some strange issue where our users who have Windows 8 and 10 (majority have Windows 10 now) cannot access the file share when connected to our Cisco An圜onnect VPN.
0 kommentar(er)
