MattPhelan
asked on
Making an internet connection available to two separate networks (RRAS) ?
Hello guys, wondering if you can help !
I have two seperate private networks :
1. A windows NT 4 server with WIN98 / XP clients (192.168.1.1 - 192.168.1.254)
2. A windows 2003 server with XP clients (192.168.2.1 - 192.168.2.254)
The problem I have is that my NT4 clients can access the internet (as a proxy server on that network is hosting web services), however I would now like my WIN2003 clients to access the web also.
I use DHCP on both networks, and to ensure the correct policies are assigned at bootup, I definately require my WIN2003 clients to logon to the WIN2003 server only !
If I put my WIN2003 server onto the same IP network as the NT box, this would allow me to access the proxy server, but it will cause me all sorts of problems when my clients are logging onto the network.
I guess that RRAS on the WIN2003 server is probably my best software solution, but how should I set things up ? What I really need is to keep my networks separate, but to make the address of my NT PROXY SERVER available to my WIN2003 network. I am really stuck as how to do it !!
Any help would be most appreciated !
Regards.
I have two seperate private networks :
1. A windows NT 4 server with WIN98 / XP clients (192.168.1.1 - 192.168.1.254)
2. A windows 2003 server with XP clients (192.168.2.1 - 192.168.2.254)
The problem I have is that my NT4 clients can access the internet (as a proxy server on that network is hosting web services), however I would now like my WIN2003 clients to access the web also.
I use DHCP on both networks, and to ensure the correct policies are assigned at bootup, I definately require my WIN2003 clients to logon to the WIN2003 server only !
If I put my WIN2003 server onto the same IP network as the NT box, this would allow me to access the proxy server, but it will cause me all sorts of problems when my clients are logging onto the network.
I guess that RRAS on the WIN2003 server is probably my best software solution, but how should I set things up ? What I really need is to keep my networks separate, but to make the address of my NT PROXY SERVER available to my WIN2003 network. I am really stuck as how to do it !!
Any help would be most appreciated !
Regards.
ASKER
Thanks VTOBUSMAN for the advice, but is there anyway I can resolve this problem without having to purchase additional software / hardware ?
I know that a hardware router or a VLAN would resolve my issues, but cash is a bit of a problem in this situation.
As I said, what I really need is to keep my networks separate, but to make the address of my PROXY SERVER available to my WIN2003 network. I am really stuck as how to do it !!
Thanks again !
I know that a hardware router or a VLAN would resolve my issues, but cash is a bit of a problem in this situation.
As I said, what I really need is to keep my networks separate, but to make the address of my PROXY SERVER available to my WIN2003 network. I am really stuck as how to do it !!
Thanks again !
You should be able to bind a second IP address to the network card on the RRAS machine then set the gateway address on the clients to the second IP on the server.
So in the TCP/IP properties on the RRAS machine, add 192.168.2.1 as a second IP address on the server. Then set the gateway address of your clients on the 192.168.2.0 subnet to 192.168.2.1.
You will now be able to route between networks and also out to the internet.
So in the TCP/IP properties on the RRAS machine, add 192.168.2.1 as a second IP address on the server. Then set the gateway address of your clients on the 192.168.2.0 subnet to 192.168.2.1.
You will now be able to route between networks and also out to the internet.
Sorry, read to fast, disregard my comment.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
just incase routing isn't automatic just enable it in routing and remote access...
hers a good link to get you started good luck
http://www.microsoft.com/isaserver/