Windows Server 2 NICs - routing problem

Posted on 2011-04-21
Medium Priority
Last Modified: 2012-06-21

Following situation;
1 Server 2008 with 2 NICs.
NIC 1: connected to network: with MASK GW
NIC 2: connected to NAS: with MASK no GW

Generally it works, BUT when I try to ping into the network then the first ping's answer is "destination host unreachable". The second ping already works normal.
(ping to NAS works just fine)

Here is my "route print":
Interface List
 14...00 50 56 96 00 09 ......Intel(R) PRO/1000 MT Network Connection #2
 11...00 50 56 96 00 01 ......Intel(R) PRO/1000 MT Network Connection
  1...........................Software Loopback Interface 1
 13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
 15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2

IPv4 Route Table
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
    266         On-link    266         On-link    266         On-link    266         On-link    266         On-link    266         On-link    266         On-link    306         On-link    306         On-link    306         On-link    306         On-link    266         On-link    266         On-link    306         On-link    266         On-link    266
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric

IPv6 Route Table
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
  1    306 ff00::/8                 On-link
Persistent Routes:

I want the connection to work normally in both direction.
Do I have to add a route?
Thanks for your help,

Question by:menefre
  • 3

Accepted Solution

Share-IT earned 1000 total points
ID: 35439597
One of the problems is the overlapping networks. with a mask of (otherwise known as is the same network as

basically with with a you are saying any address on the 10.x.x.x is on the same network so your ping will go out of the wrong interface. You should change the nas network to 192.168.x.x addresses (or something along those lines).


Author Comment

ID: 35440954
I will try that tonight and get back to you. Thanks so far!

Author Comment

ID: 35812053
Worked. I changed the subnet. thank you very much.

Author Closing Comment

ID: 35812059
I applied the changes as suggested and it works wonderfully. Thanks a lot.

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Originally, this post was published on Monitis Blog, you can check it here . It goes without saying that technology has transformed society and the very nature of how we live, work, and communicate in ways that would’ve been incomprehensible 5 ye…
This program is used to assist in finding and resolving common problems with wireless connections.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question