If there are none, while your client is connected and trying to access the server shares, than there is a problem on the client side. Than watch, if you see any incoming connections for SMB. As From: you would set up the user group (IKEv2-Users is the default) you use for the VPN connection or the address pool that you have defined for IKEv2 connections. Possibly you could even add a separate filter rule from the existing SMB template and log all traffic of that rule. If there is no such rule, than you have possibly messed a bit too much with your IKEv2 setup. Just change it to log allowed connections. The wizard should have created a firewall rule "Allow IKEv2-Users". That will give you a bit more insight in the connections that actually come over the tunnel. Probably you should edit your firewall configuration to temporarily log all allowed incoming connections from the VPN. Its a bare bones win server 2019, with few roles installed.
WATCHGUARD IPSEC VPN CLIENT FREE WINDOWS
no idea, what could be the problem - it's usually one of the already listed points, that cause failure to access shares.ġ: Connect to the file share locally on the LAN to rule out permissionsĢ: Turn off Windows Firewall on the server and attempted to access the Fileshare: If even that wouldn't work, than Possibly the browsing user does not have the required rights (shouldn't be a problem to check that from the local network, where the server resides).īeyond that. If it is not the Windows firewall, than it could be some AV/Endpoint Protection on that server that is blocking you.įor a test, turn off the firewall and/or AV/EPP on your server and try browsing the file shares.
WATCHGUARD IPSEC VPN CLIENT FREE FREE
Its just as if you had plugged in a cable between the remote client and a free port on the firebox. The VPN protocol just cares for the connection and has nothing to do with any kind of filtering.
Possibly it doesn't allow connections from other subnets. When you can ping the server from the remote client, than there is no problem on the IKEv2 connection. Start checking your windows firewall settings on the server you want to browse. No, it for sure is NOT the Netbios-NS packet, that is blocking you.Īs already said, this is a BROADCAST packet that is sent to the broadcast IP addressĢ55.255.255.255 and NOT to the address of your browsing client.Īs the nature of broadcast packets is, they are NOT routed to other networks.Īs long as you don't see anything red in the traffic monitor, that would include the clients AND servers IP address right behind the 'deny', it isn't the firewall, that is standing in your way.
0 kommentar(er)
