• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2603
  • Last Modified:

how to configure multiple gateways on a Windows 2003 server

I have a server that has two network cards.  One nic has a private ip address and the other nic has a public ip address.  When I go to save the information Microsoft Windows 2003 is stating, "Warning - Multiple default gateways are intended to provide redundancy to a single network.  They will not function properly when the gateways are on two seperate, disjoint networks.

I realize that Windows 2003 does not like the configuration.  I need both gateways working what do you suggest I do to resolve this issue.

Thanks in advance
0
lemastass
Asked:
lemastass
2 Solutions
 
Mal OsborneAlpha GeekCommented:
Not sure what you are trying to do here. Assuming you are trying to communicate with the 'net on the "external" NIC, and just a simple subnet internally, you only need a single default gateway, on the external NIC, pointing to your router.

 If you have a more complex setup with other subnets connected by routers on the "inside", then you will need to manaully add appropriate routes using the "ROUTE ADD" command. Type "ROUTE" at a command prompt for a synopsis.
0
 
lemastassAuthor Commented:
I have an application that relies on the private ip address and I have another relying on the public ip address.

I have two seperate processes on the server that require both private and public ip addresses to function properly.

I have one router and Windows 2003 server that the ip's are living on.
0
 
kdearingCommented:
malmensa is correct.
You cannot have 2 default gateways.
He's not saying you can't have an IP adress in the internal NIC, just leave the default gateway blank.
0
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

 
yasirirfanCommented:
You can use the following example

route add -p 10.2.0.0 MASK 255.255.254.0 10.0.0.10

route add -p 10.4.0.0 MASK 255.255.254.0 10.0.0.10

route add -p 10.6.0.0 MASK 255.255.254.0 10.0.0.10

from the above example 1

10.2.0.0 is the subnet and 10.0.0.10 is the gateway to access that network
0
 
lemastassAuthor Commented:
Thank you for the responses.

Yasirirfan I entered in the route as you stated but it did not make a difference.  I have an application that relies on the private ip gateway.

I also have an external public ip address and it's gateway being used by another application.

I need to have both gateways active.  Any other suggestions that you may have would be greatly appreciated.
0
 
kdearingCommented:
You keep saying "I have an application that relies on the private ip gateway".

A default gateway is a route.
Obviously, you have other subnets on your LAN that you need to access.
As yasirirfan stated, all you need to do is to ad a route to the other subnet.
What other subnet are you trying to access?
We need a detailed description of your LAN, including IP addresses/subnets.
0
 
lemastassAuthor Commented:
Hello and thank you all for trying to help me, but I have figured out what I needed to do.  I went ahead and purchased a real piece of equipment that could do what I needed to do.  I got a Cisco ASA 5510 and configured it to where I didn't need the second network card on the server.  This eliminated the gateway issue.  Natting is my friend along with access policies.
0
 
lemastassAuthor Commented:
I figured out the issue on my own, but a couple of you did offer some good suggestions I split the points between only the two that provided a layout of a possible way to fix the multiple gateway issue. Thank you and take care.
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now