<div>
The two most common causes for this (given you have a connection) is a block by the firewall (at either end) or the subnets on both ends are the same. <br />
<br />
Check the subnets and then try allowing the subnet range in the firewall. If practical, turn off the firewall only for the duration of a test.
</div>


The two most common causes for this (given you have a connection) is a block by the firewall (at either end) or the subnets on both ends are the same.

Check the subnets and then try allowing the subnet range in the firewall. If practical, turn off the firewall only for the duration of a test.

<div>
Were you pinging/RDP by DNS name or IP? If IP works where DNS name does not, you may be using a split-tunnel vpn, which is common.
</div>


Were you pinging/RDP by DNS name or IP? If IP works where DNS name does not, you may be using a split-tunnel vpn, which is common.

<div>
I figured out the issue myself.
</div>


<div>
<div class="content wysiwyg-content">
I dont know what happened here but its a mess allright.<br />
<br />
The VPN clients connect fine, but I cant ping or reach any internal workstation within the network via RDP or any other service.<br />
<br />
Any ideas?
</div>
</div>


I dont know what happened here but its a mess allright.

The VPN clients connect fine, but I cant ping or reach any internal workstation within the network via RDP or any other service.

Any ideas?

Dial Up VPN connects but wont allow remote users to see other network resources

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.