windows 2003 as a router
hi hope someone can help me out here as i am stuck with this one basically i want to use windows 2003 as a software router i have 2 nic on the server they have been given these ip addresses the first one has a ip address of
192.168.2.100
255.255.255.0
192.168.2.1 this is the default gateway connected to te internet
the second is 192.168.1.100 with the same subnet mask and no default gateway
so i then configed the dchp server on te 192.168.2.0 network with 2 scopes and set up a dchp relay on the other card to cut a long story short pcs on the 192.168.2 network can connect to te intermet fine but not on the 192.168.1 network i have a scope on
the 192.168.1 network as follows 192.168.1.20 to 192.168.1.40 subnet mask of 255.255.255.0 default gateway is 192.168.1.100 what am i missing to get these acess to the internet
September 16th, 2010 5:14am
This article may help.
How To Set Up Internet Connection Sharing in Windows Server 2003
http://support.microsoft.com/kb/324286
Regards, Dave Patrick .... Microsoft Certified Professional -Microsoft MVP [Windows]
Free Windows Admin Tool Kit Click here and download it now
September 16th, 2010 5:26am
The problem is most likely due to the fact that you have not created a route to 192.168.1.x network on your Internet connected router. What happens is that the packets are leaving the 192.168.1.x network, the 2003 router will pass it on to the Internet
Router (192.168.2.1), NATs it, then the Internet router sends it off. However, when the packet returns, it un-NATs, but doesnt know how to send the packet back to the 192.168.1.x network.
On your Internet router, you have to create a route to the 192.168.1.x network. The interface where you have to send those packets to will be 192.168.2.100.
That will fix your issue. IF you are unable to create the route, you will have to set up the 2003 server to do NAT'ing as well so that every packet that leaves from the 192.168.1.x network will be stampted as 192.168.2.100 as a source packet. Double
NAT'ing works but the design is not as nice and it will break the communication flow between your 192.168.2.x and 192.168.1.x nodes.
Visit: anITKB.com, an IT Knowledge Base.
September 16th, 2010 10:46am
Hi kkoolkev,
Thanks for post here.
According you description I understand that you want Hosts where located in 192.168.1.0/24 segment also could access internet through router 192.168.2.1.
If I misunderstand please let me know.
Hosts(192.168.1.0/24)--------------windows server 2003------------Hosts(192.168.2.0/24)----------------Router(192.168.2.1)-----------Internet
Seems there is no problem that the hosts where in 192.168.2.0/24 segment access internet with point 192.168.2.1 as default gateway ,and is there any problem that hosts
in 192.168.1.0/24 access hosts where in 192.168.2.0/24?
What I think that you should enable route feature and add a default gateway on this windows server 2003 host ,please install RRAS on server and add the route below
on it :
Network Destination
Netmask
Gateway
Interface
0.0.0.0
0.0.0.0
192.168.2.1
192.168.2.100
How to Use Static Routes with Routing and Remote Access Service
http://support.microsoft.com/kb/178993
Hope that’s helps.
Tiger LiPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
September 16th, 2010 10:44pm
As I posted above, keep in mind that the Internet Router has to also know about the 192.168.1.x network. If it doesnt have a route (as I posted above), the packets will not be able to make it back to the 2003 RRAS server.
This user needs a route on the router pointing back to 192.168.1.x network by sending the packets to the 192.168.2.100 interface (from the perspective of the internet router).
Visit: anITKB.com, an IT Knowledge Base.
September 17th, 2010 11:05am