Hey folks. I have a Windows 2003 server setup as a virtual server. It has one "virtual" NIC and everything sits behind a Linksys router with the ports forwarded. I enabled the Routing and Remote access service and I'm a able to successfully make a connection from the outside (via Verizon aircard) with Windows XP Pro "Create a new Connection" VPN. Problem is, I can ping the server by IP only and access shares on the server, but only by manually browsing as \\192.168.1.250. I can't ping any other IP devices, such as printers, on the LAN (where the server is) and can't resolve host names like the server's name or Yahoo.com. I also can't ping any outside IP addresses. I looked for some restrictive policy and did a search but all I could find was a lot of people with the same problem but no resolution. Anybody point me at least in the right direction? Thanks. Assume that I already did an Internet search.

So I guess, you are using a End-to-End VPN. That means, that the client only authenticates to the server and can't see the rest of the network. What you need is a VPN Site-to-End, that allows to connect and access to the whole network.

Paul, no it's not a gateway to gateway VPN, if that's what you mean to say. It's Windows XP and Windows 2003 Server. Thank you for you attempt. Does anyone else have any ideas on the routing issue with Routing and Remote Access? Thanks. Assume that I already did an Internet search.

Paulsep explained it correctly. When you say gateway to gateway vpn you mean site to site vpn. What Paulsep explained is you have a client to client vpn or end to end vpn which restricts your access to the server and no where else. You want a end to network vpn. We do this with vpn capable routers and by putting the vpn client on the xp station they are able to authenicate to the router which then gives them access to the entire network Imagine the power of knowing how to internet search http://www.lib.berkeley.edu/Teachin...

Wanderer, thanks. I've worked with computer networks for 11 years now. I'm pretty familiar with and implemented a number of VPN routers in both gateway to gateway and client to gateway configurations. I've even implemented VPN solutions involving Windows 2003 Small Business Server- Small Business Server has a lot of GUI tools for making implementation easy and does a lot for you. But this is the first time I've tried using Routing and Remote access on Windows 2003 "Standard" server as a VPN solution. I know using VPN hardware would be an easier solution, but I want to try and get this working with Routing and Remote Access using the setup I described above in the first post. So I guess to try and make my question a little clearer..... - Does anyone know what my problem may be or where it may lie as I described it in my first post, or does anyone know for a fact it just can't be done by using what I'm trying to use? There's no need to point out other VPN solutions as I am aware of those, and I'm trying to get this to work with Routing and Remote Access in Windows 2003 Standard. Thanks. Assume that I already did an Internet search.

This should address your issue. http://support.microsoft.com/kb/243374 Imagine the power of knowing how to internet search http://www.lib.berkeley.edu/Teachin...

Thanks. I gave it a try but still doesn't work. I've tried various setup options: VPN, VPN and NAT and basic firewall, and VPN and NAT and LAN Routing. I've looked at various options and even tried installing a MS Loopback adapter to give the system 2 network adapters and checked various settings. I can ping the server while connected but can't connect to anything else, either the web or local network. Hrmmmmmm.... Assume that I already did an Internet search.