Re: RRAS Problem
- From: Kurt <kurtl@xxxxxxxxxxxxxxxxx>
- Date: Thu, 07 Dec 2006 21:17:02 -0800
Phil wrote:
Scenerio:
I have a co worker that is now working from home. We set up her computer on the domain and configured it locally. I want to be able to have access to her computer (Remote desktop, connect to \\computername\C$, etc.) so that we can't maintain it with updates, etc. We are using Windows 2k3 server configured with RRAS (PPTP) and IAS for policies. RRAS is configured to use DHCP.
Problem:
Client computer can VPN and connect to all servers and any other nodes on network, but local lan computers cannot connect to client (ping, RDP, etc.). Therefore, I can't manage her computer from work. If I look at her ipconfig, it show subnet mask of 255.255.255.255 instead of 255.255.252.0 which all our LAN DHCP computers receive. Is this why I can't connect to her computer?
Thanks in advance for any help!
The default PPTP VPN is a "client-to-network" configuration. It connects the PPTP client to the network by allowing the PPTP server to proxy information for it. The server accepts packets from the client and then puts them out onto the local network using it's own MAC address. When a package arrives using the client's IP address but the server's MAC address, the server knows to forward those packets to the client. But it's a one-way deal, much like NAT. You CAN make it work, but it involves a PPTP VPN in both directions and is a pain to maintain. Buy her a router and a matching one for yourself. Take a look at the Secure Computing SG300 (about $200 street price) and set up an IPSec VPN. You'll need a public IP address on both ends and at least one end must be static. Then a little creative routing will have you talking between LANS bi-directionally.
....kurt
.
- Prev by Date: Re: Default gateway for RAS
- Next by Date: Member server or DC
- Previous by thread: Re: RRAS Problem
- Next by thread: Member server or DC
- Index(es):
Relevant Pages
|
Loading