Setting up RRAS/VPN's...
I have installed RRAS successfully on a server on our LAN. It has two NIC's, one for our LAN, and one connected to our frame relay router.
I can connect to the RRAS server from with NT Workstation 4.0 (by the way, the RRAS server is on NT Server 4.0), however, I lose my Internet access when connected. If I disconnect from the RRAS server, my Internet access comes back.
Do I have to specify somewhere on the RRAS server that all machines connected to it and requesting Internet access should gain that access through our router on our LAN? Is there something else involved?
Thanks!
I can connect to the RRAS server from with NT Workstation 4.0 (by the way, the RRAS server is on NT Server 4.0), however, I lose my Internet access when connected. If I disconnect from the RRAS server, my Internet access comes back.
Do I have to specify somewhere on the RRAS server that all machines connected to it and requesting Internet access should gain that access through our router on our LAN? Is there something else involved?
Thanks!
In this situation are you dialing into the RRAS at the same time you have a LAN connection to the RRAS server? I haven't proven this with a packet sniffer, but it appears the lastly established network is the first to be tried for outgoing packets. There may be a problem with your routes for dial-ups on the RRAS machine, and therefore you are not getting the internet bound packets through when you workstation sends over the improperly configured dial-up connection.
ASKER
This is what happens... I connect with my ISP at home, then connect with the RRAS server. After this point, I lose all Internet access. When I hang up with the RRAS server, Internet access is restored.
When connected to the RRAS server, I can access the LAN on which the RRAS server resides just fine.
If there is a problem with my routes on the RRAS server, where do I set them, and on which NIC (the LAN NIC or WAN NIC)?
Thanks!
When connected to the RRAS server, I can access the LAN on which the RRAS server resides just fine.
If there is a problem with my routes on the RRAS server, where do I set them, and on which NIC (the LAN NIC or WAN NIC)?
Thanks!
ASKER
This is what happens... I connect with my ISP at home, then connect with the RRAS server. After this point, I lose all Internet access. When I hang up with the RRAS server, Internet access is restored.
When connected to the RRAS server, I can access the LAN on which the RRAS server resides just fine.
If there is a problem with my routes on the RRAS server, where do I set them, and on which NIC (the LAN NIC or WAN NIC)?
Thanks!
When connected to the RRAS server, I can access the LAN on which the RRAS server resides just fine.
If there is a problem with my routes on the RRAS server, where do I set them, and on which NIC (the LAN NIC or WAN NIC)?
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks... I will try this and see if it works.
Not sure about win NT4, but I know in Windows 2000/XP there is a setting which instructs your machine to use the default gateway that is pushed down from the machine your vpn is connecting to. (providing dhcp is used)
This setting can be disabled in win2k/xp by going to the properties of the dialup/vpn connection, then to networking, then to the properties page of TCP/IP, then to advanced, and under the general tab you will see the option - Use default gateway on remote network. I found that if you disable that you can access machines on your remote network and also get on the internet still.
As I said above, I'm not sure how relevant this is to windows NT4, but I hope you can apply some of it and work the rest out.
This setting can be disabled in win2k/xp by going to the properties of the dialup/vpn connection, then to networking, then to the properties page of TCP/IP, then to advanced, and under the general tab you will see the option - Use default gateway on remote network. I found that if you disable that you can access machines on your remote network and also get on the internet still.
As I said above, I'm not sure how relevant this is to windows NT4, but I hope you can apply some of it and work the rest out.