I have a server that is running windows Server 2003 and it has 2 nics. We have had this server setup with a cisco aeronet unit to link back to our main corporate network however the connection isnt always reliable. We just setup a new ISP service into that location and I was wondering if it is possible and how would the server be setup to retain access to the new DSL line and also the old aeronet. The Aeornet is setup with a 10.1.x.x static ip address and links it back into our DC this way and we have people that need to access that server so we want to be able to leave this in place however we would like to have the new Dsl setup to handle the internet traffic for that location. This currently is setup on a 192.168.x.x ip address that is controlled via the ISP's router. Is it possible to keep one nic setup on the 10.1.x.x and the other on a 192.168.x.x and have people from both networks be able to access the server. If not how should I setup the Nic's so there is access for both networks?
Windows Server 2003 - Multiple different IP addresses and access to server
- Thread starter crpillot
- Start date
mbreslin1954
Distinguished
- Nov 27, 2010
- 1,515
- 1
- 20,460
It shouldn't be a problem. Try it. Are you running Routing and Remote Access Server (RRAS) on your server running Server 2003?
It depends on the subnet masks you are using. If the 10.1.x.x. is a /16 then it is as simple as removing the gateway/default route from that connection. Since the default route is still on the 192.168.x.x subnet all the traffic that is not 10.1.x.x/16 will go to that gateway.
Now if you have a bunch of different 10.1.x.x subnets then it is the same process you remove the gateway from this interface but you now must use the ROUTE ADD statement to tell it to send all the networks that are in your corporate network to the route/gateway that represents the path back to the main connection. You can still say 10.0.0.0/8 goes to the main network even if you do not have all the 10. address there. It gets much more complex when you have 10. networks on both connection and/or you are accessing internet routable addresses on both connections.
Now if you have a bunch of different 10.1.x.x subnets then it is the same process you remove the gateway from this interface but you now must use the ROUTE ADD statement to tell it to send all the networks that are in your corporate network to the route/gateway that represents the path back to the main connection. You can still say 10.0.0.0/8 goes to the main network even if you do not have all the 10. address there. It gets much more complex when you have 10. networks on both connection and/or you are accessing internet routable addresses on both connections.
This server is not currently running RRAS as the routing is handled by our DC which is in the adjoining building. This server is specialized for one department that is housed in that building.
There is only the 1 10.1.21.x subnet which is controlled by our DC that this server connects to and will need to be accessed by. The new ISP will have its own Subnet a 192.168.x.x subnet that the people in that department/building would be using to access it. I connected second ISP cable to the server (the 192.168.x.x) but I was unable to access the server through it. Is that because the server still has the 10.1.21.x gateway setup on it and if I remove it will that stop access from the 10.1.21.x network. I have not done a lot of subnetting before and I want to make sure I get this right.
The way subnets work is say I have 3 networks 10.1.21.0/24 and 192.168.1.0/24 172.16.100.0/24 each on a interface. The computer knows for example that 10.1.21.50 is on the interface with 10.1.21.0 and 172.16.100.50 is on the subnet with 172.16.100.0. etc. If these are the only networks you have you do not need any gateways.
Now lets say I want to get to 4.2.2.2 or maybe 192.168.5.50. It will look and determine neither of these is in one of the networks it is connected to. Then in the simplest case looks for the point to exit the network. This is called the default route/gateway. There can only be one of these since it is the place it sends all traffic it pretty much does not know what to do with. It can be any address. If for example it was 172.16.100.200 it would know that was in the interface that has 172.16.100.0/24 or if it was 10.1.21.200 it would know to send it our the 10.1.21.0/24 interface.
When you have very simple networks you can pretty much just define the gateway on the interface that has the connection to the outside world and remove it from the rest and it will work. It is not always that simple but I suspect in your case it is.
Now lets say I want to get to 4.2.2.2 or maybe 192.168.5.50. It will look and determine neither of these is in one of the networks it is connected to. Then in the simplest case looks for the point to exit the network. This is called the default route/gateway. There can only be one of these since it is the place it sends all traffic it pretty much does not know what to do with. It can be any address. If for example it was 172.16.100.200 it would know that was in the interface that has 172.16.100.0/24 or if it was 10.1.21.200 it would know to send it our the 10.1.21.0/24 interface.
When you have very simple networks you can pretty much just define the gateway on the interface that has the connection to the outside world and remove it from the rest and it will work. It is not always that simple but I suspect in your case it is.
TRENDING THREADS
-
-
-
-
Question Display no signal when 1440P or higher full screen gaming- Started by Wouter_U
- Replies: 3
-
Question Download speed is slow on only my PC - please help!- Started by Ograsmium
- Replies: 15
Latest posts
-
-
Question Buying a used card, what should I look for before purchase?
- Latest: ohio_buckeye
-
-
-
-
Facebook
Twitter
Instagram