Remote Clients Connect Via VPN But are not accessible

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
We have x remote users connecting to the office via VPN successfully. They are able to browse all resources (that they are allowed) as if sat at the office.

The problem is that the IT support staff cannot access the remote Clients ? I was hoping we could SMS to remote control their machines and solve any issues. Im not even able to ping the remote machines although they are assigned DHCP addresses.

Clients do not have the "Use remote Gateway" option ticked. Any ideas ?

Thanks
 
Are able to ping the remote clients from VPN server? If yes then try doing
tracert -d <ipaddress of remote client> and see which machine is dropping
it.
Once you have identified that then you can proceed further.

If RRAS server is dropping then it could be because of filters/firewall.
check if ports are opened.

--
-Pawan [MSFT]

-------------------------------------------------------------------------
"This posting is provided "AS IS" with no warranties, and confers no
rights."
------------------------------------------------------------------------
Confusious said:
Hi,
We have x remote users connecting to the office via VPN successfully. They
Click to expand...
are able to browse all resources (that they are allowed) as if sat at the
office.
The problem is that the IT support staff cannot access the remote Clients
Click to expand...
? I was hoping we could SMS to remote control their machines and solve any
issues. Im not even able to ping the remote machines although they are
assigned DHCP addresses.
 
If the remotes are using IP addresses in the same subnet as the LAN
machines, you should be able to access them just like LAN clients. Routing
doesn't really come into it. The LAN machine just sends the frame from the
LAN NIC (because it is in the local IP subnet). The server does proxy ARP
for the remote, gets the frame over the Ethernet then forwards in over the
pont-to-point link. That's how it works when the remote accesses a LAN
client as well.

If you can't get it to work, put the remote clients in their own IP
subnet and route the traffic through the RRAS server, as if the remotes were
on their own segment.

Confusious said:
As i said, i am unable to ping the remote clients.
The VPN / RRAS has a static addres pool of 192.168.0.150 - 159 for remote clients.
My routing table shows the connected client and indicates the gateway for
Click to expand...
that client as that of my router. but still no luck.
 
Cheers For that.
I actually did as Grant has suggested. The easy way is to set the client to use the remote gateway but this wasnt an option for me.

Thanks again.
 
Back
Top