I've got RAS set up for VPN connections for outside sales reps to connect to our network. This tends to work without issue most of the time. But oddly, when no settings have been changed, sometimes, like now I we run into a problem. Currently my RAS server (ginkgo) is on a machine w/ 3 NICS w/ IP's .2, .5 and .6, .2 does not have a Gateway set up on the NIC. My AD/DHCP/DC/DNS/WINS Server is on another server w/ IP's .9 and .10. Right now I have a sales rep who is connected to the VPN, and in the MMC I can look at his session. I know, through this he has a IP of .67, and I have it doing this via DHCP. The DHCP server has a scope of .60 -.90 and there are 11 entries for Ginkgo RAS, and they correspond to the scope set up on Ginkgo for RAS.
I'm attempting to use either RAdmin or RDP to take control of his laptop and do some troubleshooting (this is normally not an issue), but now can't reach the computer. If I ping .67 I've got two different out comes 1)the ping times out or 2) "Reply from 192.168.254.5: TTL Expired in Transit" now, .5 is the Ginkgo server, not the computer I'm actually looking to connect to. His session is authenticated and he is registered on the network. He can ping any computer within the network, including servers and my desktop (that i'm pining him from).
Any suggestions? I'm sure there's more info thats going to be needed