[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 356
  • Last Modified:

Multiple NIC Cards and Routing Issue

I have a Windows 2003 server at my office that has two NIC cards, one with an internal IP on the LAN, and one that is assigned a "real world" IP address. It is not able to ping any of my clients that I have at a remote branch because I assume it is attempting to go out through the default gateway of the "External" NIC. All of my other machines with just the local address on them are able to get out and ping the remote vpn clients because their default gateway has a static route to the location (this router is also the VPN "server"). Is there a way in Windows that I am perhaps forgetting or don't know about that allows you to specify certain networks to be sent out specific NIC cards? Or is there any other work around that you can think of? I guess I may just have to buy a new router or a new interface for the router and assign the "real IP" to that and forward the ports I need to the server and just take out the other NIC. Thanks for your help!
0
pctechcorp
Asked:
pctechcorp
3 Solutions
 
DbergertCommented:
you can do a tracert to see what path it is taking....
0
 
pctechcorpAuthor Commented:
I understand that, and have verified that the traffic is going out the "wrong" interface.
0
 
omrisiriCommented:
You could just configure a routing table on your computer. although this will require some knowledge in routing
Type route in the command prompt will give you a list of options

Before that i would check if turning off each NIC will allow you to use it's respective resources
For example disable the nic connected to the outside and try pinging inside and vice versa

you could just have a different network problem.

I actually do this all the time with my computer shouldn't have any problems...
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 
omrisiriCommented:
Also check the Network Mask on both nic's
and make sure internal computers are using 'illegal' ip's for the internal network (192.168.x.x or 10.0.0.x for example)
Otherwise the traffic will be routed through the default gateway.
0
 
DbergertCommented:
ok -- actually you stated that you assumed this... thanks for verifing.

you can add a staic route for the clients network to tell it what interface to use on the W2K3 box.  or  alternativy you could put the external NIC and its next hop as the default gateway, and create statics for any internal traffic and networks that need to access it.
0
 
KVR_SolutionsCommented:
Here is the information that you are looking for:

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/route.mspx?mfr=true

Remember that if you don't make it a persistent route, it will remove itself from the routing table at the next reboot.

(This option is -p)

Ira @ KVR
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

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