Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a virtual windows server 2008 r2 with 2 virtual network adapters, one is part of a domain and the other isn't. When I ping to a specific PC that is part of the domain it connects to it through the second network adapter (the one that isn't in the domain) and I tried to change that with a static route:

ROUTE ADD -P <target PC's IP> MASK <Subnet mask from ipconfig> <Default Gateway of the adapter in the domain> if <tried it with all possible interfaces>

Unfortunately, that didn't work, so I'll be happy to be assisted with How to make this static route so my server will connect to the PC that is in the domain through the network adapter that is in the domain?

Output of route print and ipconfig:

C:\Users\user>route print

========================================

Interface List

 18...00 15 5d 80 0f 47 ......Microsoft Virtual Machine Bus Network Adapter #2

 11...00 15 5d 80 0f 1a ......Microsoft Virtual Machine Bus Network Adapter

  1...........................Software Loopback Interface 1

 12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter

 21...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  192.168.128.254   192.168.128.13      5

          0.0.0.0          0.0.0.0    192.168.137.1   192.168.137.15      5

        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

    192.168.128.0    255.255.255.0         On-link    192.168.128.13    261

   192.168.128.13  255.255.255.255         On-link    192.168.128.13    261

  192.168.128.255  255.255.255.255         On-link    192.168.128.13    261

    192.168.137.0    255.255.255.0         On-link    192.168.137.15    261

   192.168.137.15  255.255.255.255         On-link    192.168.137.15    261

  192.168.137.255  255.255.255.255         On-link    192.168.137.15    261

        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    192.168.128.13    261

        224.0.0.0        240.0.0.0         On-link    192.168.137.15    261

  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    192.168.128.13    261

  255.255.255.255  255.255.255.255         On-link    192.168.137.15    261

=========================================================================== 
Persistent Routes:   

Network Address       Netmask  Gateway Address Metric

192.168.128.8       255.255.255.0  192.168.128.254    1

===========================================================================

IPv6 Route Table

=========================================================================== 

Active Routes:

 If Metric Network Destination      Gateway

 18    261 ::/0                     fe80::f427:d7d8:4ec2:fd5

  1    306 ::1/128                  On-link

 11    261 fe80::/64                On-link

 18    261 fe80::/64                On-link

 11    261 fe80::8ce7:a7a5:d7c0:faf1/128 On-link

 18    261 fe80::a8c7:ee26:b1bb:fd77/128 On-link

  1    306 ff00::/8                 On-link

 11    261 ff00::/8                 On-link

 18    261 ff00::/8                 On-link

===========================================================================
Persistent Routes:   None

C:\Users\user>ipconfig

Windows IP Configuration

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :

   Link-local IPv6 Address . . . . . : fe80::a8c7:ee26:b1bb:fd77%18

   IPv4 Address. . . . . . . . . . . : 192.168.137.15

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : fe80::f427:d7d8:4ec2:fd5%18

                                       192.168.137.1

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : domainName.com

   Link-local IPv6 Address . . . . . : fe80::8ce7:a7a5:d7c0:faf1%11

   IPv4 Address. . . . . . . . . . . : 192.168.128.13    

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : 192.168.128.254

Tunnel adapter isatap.domainName.com:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . : domainName.com

Tunnel adapter isatap.{5364A7C9-95AE-4753-98A3-8D60A49D43D5}:

   Media State . . . . . . . . . . . : Media disconnected   

   Connection-specific DNS Suffix  . :
share|improve this question
    
please provide output of ROUTE PRINT and IPCONFIG – ETL Jan 28 '14 at 14:33
    
Added output - don't have enough reputation for images yet... – Moshisho Jan 28 '14 at 15:21
    
Media State . . . . . . . . . . . : Media disconnected - Start by connecting the network adapter in question to the network. – joeqwerty Jan 28 '14 at 15:21
    
As far as I understand the part of Tunnel adapter is for IPv6 (isn't it?) and the server is connected to the network - both of the domain and outside it. – Moshisho Jan 28 '14 at 15:43
    
@Moshisho Yeah, your network adapters are reported as connected. You're not using the Tunnel adapter in this set up but Windows insist on telling you all about it. – ETL Jan 28 '14 at 15:48
up vote 12 down vote accepted

Part of the problem is that you have 2 DEFAULT GATEWAY which violates the meaning of DEFAULT GATEWAY. Put the default gateway only on one interface. Then with static route, direct the traffic you want to go via the other interface.

For example, LAN1 192.168.123.13 Mask 255.255.255.0 and GW 192.168.128.254. That will get all traffic to 192.168.123.x and anything to any other network will be directed through the gateway.

But then add LAN2 192.168.137.15 Mask 255.255.255.0 WITHOUT any default gateway. That will automatically create a routing entry that 192.168.137.x will go through this interface instead of the Default Gateway. Now, if you want other traffic to go through that interface, you can create a static route like:

ROUTE ADD -P 192.168.33.0 MASK 255.255.255.0 192.168.137.1

That will send the traffic going to 192.168.33.x through LAN2 as 192.168.137.1 is in the same network as LAN2 interface.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.