I think forcing RRAS to assign your internal NIC the same IP as your
external connection will*up your router's NAT. NAT's supposed to
forward packets from an external IP to and internal IP, how could it route
packets from the external IP to the same IP again? Also, I know that when I
enabled NAT on my RRAS VPN server (also behind a firewall/NAT router) I
could no longer access it from any of my internal computers.
The only thing I can suggest is to be sure you have the correct IP addresses
of your DNS, DHCP, and WINS servers on your "internal" and "external" NICs.
You do have two NICs installed in your RRAS VPN server, correct? If you
don't have your own DHCP server, I believe your VPN clients will get the
same settings (other than the IP) as your "external" NIC.
I renamed my two NIC cards to help me remember which one VPN is using as the
"external" or "public" NIC, and which is the "internal" or "private" NIC.
This helped me avoid any configuration issues.
Also, you will not be able to use network neighborhood after connecting
through VPN. You will have to connect to resources using NetBIOS
Hope this helps,
> > > > I have a home network I want to set up with VPN to be able to access
> > > home
> > > > computers while travelling... A Win2K server is set up for VPN
> > RRAS
> > > > inside the linksys router, with port 1723 forwarded to the Win2K
> > > > address (192.168.1.5). This server is also the PDC with AD, DNS,
> > > > (running Small Business Server)..
> > > > I set up a user on the domain and gave it connection rights.
> > > > remotely from my XP laptop, everything works fine during
> > > get
> > > > an internal IP address from DHCP (192.168.1.50 - start of range).
> > However,
> > > I
> > > > cannot ping or access anything on the internal network..
> > > > Any ideas?
> > > I believe if you have a static IP you can use RRAS`s Network Address
> > > Translator to assign the public IP to an interface on your Internal
> > network
> > > so that it effectively has a direct internet connection and can be
> > > directly from the Internet.
> > > You should be able to do this on your router as well then it would
> > you
> > > having to forward a port.
> > OK.. I'm confused. Isn't the router already doing NAT?
> Sorry you`d have to get configure the Network Address Translator on the
> router to assign the public IP to your internal server - should be
> never had the luxury of a static IP or a range of static IPs to try it out