In short the problem is that when users connect to the VPN and try and map a network drive they can't see the server shares or the NAS on the network. This has has been working for about 2 years all through lockdown etc, it was a little temperamental but the majority of the time it worked. However, its now a case that majority of the time it doesn't work.
Office Network
- Gateway: 192.168.16.1
- Server: 192.168.16.2
- NAS: 192.168.16.11
IP config from server gives:
PPP Adapter RAS (Dial In) Interaface:
- IPv4 Address: 192.168.16.50
- Subnet Mask: 255.255.255.255
- Default Gateway: BLANK
Ethernet adapter Ethernet:
- IPv4 Address: 192.168.16.2
- Subnet Mask: 255.255.255.0
- Default Gateway: 192.168.16.1
My test client connected via the VPN then has:
PPP Adapter ARC:
- IPv4 Address: 192.168.16.52
- Subnet Mask: 255.255.255.255
- Default Gateway: BLANK
Ethernet adapter Ethernet:
- IPv4 Address: 192.168.1.100
- Subnet Mask: 255.255.255.0
- Default Gateway: 192.168.1.1
Once connected to the VPN we just want to have a mapped network drive to the NAS, so
\\192.168.16.11\data
But the client just can't see that IP address. Doing a simple PING in command prompt from the client and the server, and request times out every time.
I added a static pool address in Routing and Remote Access to make sure they were getting a useable IP address. Start IP address of 192.168.16.50, end IP address of 192.168.16.70 as I saw that solved similar problems for people.
I've also made sure the 'Routing' feature is installed, as again another solution for someone but no difference.
I thought it was a problem with the subnet mask with the VPN getting 255.255.255.255 but apparently that is common and not a problem.
I've temporarily disabled the firewall on the server to see if that makes a difference.
And I can't see a policy in Network Policy Server that might be restricting access.
So I must have missed something along the way... any help much appreciated.
