Windows Server 2 NICs - routing problem

Hi,

Following situation;
1 Server 2008 with 2 NICs.
NIC 1: connected to network: 10.0.0.105 with MASK 255.0.0.0 GW 10.0.0.5
NIC 2: connected to NAS: 10.0.10.12 with MASK 255.255.0.0 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
          0.0.0.0          0.0.0.0         10.0.0.5       10.0.0.105    266
         10.0.0.0        255.0.0.0         On-link        10.0.0.105    266
         10.0.0.0      255.255.0.0         On-link        10.0.10.12    266
       10.0.0.105  255.255.255.255         On-link        10.0.0.105    266
       10.0.10.12  255.255.255.255         On-link        10.0.10.12    266
     10.0.255.255  255.255.255.255         On-link        10.0.10.12    266
   10.255.255.255  255.255.255.255         On-link        10.0.0.105    266
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link        10.0.0.105    266
        224.0.0.0        240.0.0.0         On-link        10.0.10.12    266
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link        10.0.0.105    266
  255.255.255.255  255.255.255.255         On-link        10.0.10.12    266
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0         10.0.0.5  Default
===========================================================================

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


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

menefreAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Share-ITCommented:
One of the problems is the overlapping networks.

10.0.0.105 with a mask of 255.0.0.0 (otherwise known as 10.0.0.0/8) is the same network as 10.0.12.2.

basically with with a 10.0.0.0/8 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 255.255.255.0 addresses (or something along those lines).

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
menefreAuthor Commented:
I will try that tonight and get back to you. Thanks so far!
0
menefreAuthor Commented:
Worked. I changed the subnet. thank you very much.
0
menefreAuthor Commented:
I applied the changes as suggested and it works wonderfully. Thanks a lot.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.