NIC Metrics Issue - Internet Connected yet no response from websites

[jvamos]

Hello,

I am posting about a problem which has been bugging me for a while. I have a machine with two NICs on the motherboard, one is connected to a gigabit switch then to an router running a dhcp server and operating as the gateway. The other NIC is connected to a piece of hardware that is connected via ethernet to another dhcp server by sonicwall. I have many other running dual NIC this way but on this special computer the drivers and hardware on port 2 is a different model.

I followed the instructions posted here.
Windows 7 64bit dual Ethernet port EuCon DAW disconnecting

When just set to automatic metrics the internet works but the consoles connection to the PC is intermittent. When I set the metrics up and prioritize one device over the other the internet doesn't work but the console is solid. I can see the requests going out for google but nothing happening.

I have tried this with two alternative nics that are PCI and PCIe to try and rule the NICs on the mobo out.

I can post a wireshark capture of the activity on the side with no internet. I don't know much about it.

Thanks for any help.

Gigabyte GA-z68-ud7 - Win 7 64bit Ult - Eucon WS 64bit - System 5 MC

 

[TheCyberMan]

Hi from Sevenforums,

Are the others Windows?

 

[jvamos]

Thanks,

Yeah all the same OS and dual nic. The software for the consoles is different only.

 

[TheCyberMan]

I would try NIC 1 10 and 30 for nic 2 as long as don't conflict with others on the network.

 

[jvamos]

For the metrics?

 

[TheCyberMan]

For the metrics.

 

[jvamos]

Hasn't had an effect after reboot. Hm

 

[TheCyberMan]

Open a cmd prompt type route print.

Please post a screenshot.

 

[jvamos]

Hey sorry. I didn't get that till now. I just used > to create a text file.

===========================================================================
Interface List
 21...e8 94 f6 02 61 7c ......Realtek PCIe GBE Family Controller #3
 19...00 a1 b0 00 1f 46 ......Realtek RTL8139/810x Family Fast Ethernet NIC
  1...........................Software Loopback Interface 1
 16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
 20...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1     192.168.1.48     32
          0.0.0.0          0.0.0.0  192.168.168.168  192.168.168.110     20
        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.1.0    255.255.255.0         On-link      192.168.1.48    286
     192.168.1.48  255.255.255.255         On-link      192.168.1.48    286
    192.168.1.255  255.255.255.255         On-link      192.168.1.48    286
    192.168.168.0    255.255.255.0         On-link   192.168.168.110    266
  192.168.168.110  255.255.255.255         On-link   192.168.168.110    266
  192.168.168.255  255.255.255.255         On-link   192.168.168.110    266
        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.1.48    286
        224.0.0.0        240.0.0.0         On-link   192.168.168.110    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      192.168.1.48    286
  255.255.255.255  255.255.255.255         On-link   192.168.168.110    266
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0      192.168.1.1       2
          0.0.0.0          0.0.0.0      192.168.1.1  Default 
          0.0.0.0          0.0.0.0      192.168.1.1  Default 
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
 13     58 ::/0                     On-link
  1    306 ::1/128                  On-link
 13     58 2001::/32                On-link
 13    306 2001:0:9d38:90d7:2868:8d9:3f57:5791/128
                                    On-link
 13    306 fe80::/64                On-link
 13    306 fe80::2868:8d9:3f57:5791/128
                                    On-link
  1    306 ff00::/8                 On-link
 13    306 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

 

[jvamos]

The correct gateway's seem to be set. There are other metric settings though. Would one have to set those through command line?

 

[TheCyberMan]

You would set the metric interface under Internet Protocol ipv4 under advanced remove the checkmark from Auotomatic Metric and put your own metric setting in there.

Leave 32 as normal and 20 change to 40.

It should work but #windows can be funny.

Check your Windows by doing a route print set similar to those.

 

[jvamos]

Hey again Cyberman,

Thanks again for your help. Does anything look odd in this route print?

===========================================================================
Interface List
 21...e8 94 f6 02 61 7c ......Realtek PCIe GBE Family Controller #3
 19...00 a1 b0 00 1f 46 ......Realtek RTL8139/810x Family Fast Ethernet NIC
  1...........................Software Loopback Interface 1
 16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
 15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0  192.168.168.168  192.168.168.110     20
          0.0.0.0          0.0.0.0      192.168.1.1     192.168.1.48     51
        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.1.0    255.255.255.0         On-link      192.168.1.48    306
     192.168.1.48  255.255.255.255         On-link      192.168.1.48    306
    192.168.1.255  255.255.255.255         On-link      192.168.1.48    306
    192.168.168.0    255.255.255.0         On-link   192.168.168.110    266
  192.168.168.110  255.255.255.255         On-link   192.168.168.110    266
  192.168.168.255  255.255.255.255         On-link   192.168.168.110    266
        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.1.48    306
        224.0.0.0        240.0.0.0         On-link   192.168.168.110    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      192.168.1.48    306
  255.255.255.255  255.255.255.255         On-link   192.168.168.110    266
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0      192.168.1.1       1
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
 13     58 ::/0                     On-link
  1    306 ::1/128                  On-link
 13     58 2001::/32                On-link
 13    306 2001:0:5ef5:79fd:c43:24cd:3f57:5791/128
                                    On-link
 13    306 fe80::/64                On-link
 13    306 fe80::c43:24cd:3f57:5791/128
                                    On-link
  1    306 ff00::/8                 On-link
 13    306 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

 

[TheCyberMan]

The gateways have changed place should have shoiwn that first lower metric being first. The metric is different.

Does it work?

 

[jvamos]

I did a route /F and rebooted and reset the secondary switch. I then set the metrics as you had described, the route print doesn't match the metrics I set per se. But now the console stays attached and the internet works. It's a bit slow to get a response from websites but it works! Thanks so much. I was under the impression metrics were hard and fast but I guess they are calculated?

 

[TheCyberMan]

A reset of the switch or a re-boot of the switch would be neccessary for the new configuration which is on Windows would go thru to the switch.

Glad all is fixed. I have been a help to you.

A bit slow on the second switch you reset to default settings make sure you have the ethernet setting either 10/100 Fast ethernet or 10/1000 Gigabit ethernet.

 

[jvamos]

The switch was reset, it is only 10/100 but it isn't internet facing. The issue has returned unfortunately today.

I am wondering if it is due to some automatic configuration of the routing. Is there any way to go through and specify the routes?

 

[TheCyberMan]

Take the switch out of the equation for testing. Connect to the router directly. I am assuming ypou have a router.

 

[jvamos]

Yes, I just attempted this it seems stable again. Just making sure, doing some testing.

What is the difference between DHCP and switching and how can switching have a bearing on if a interface follows the gateway or not?

 

[TheCyberMan]

You have DHCP setting on a managed switch if computers have DHCP assigned "obtain a IP address automatically" then you should have DHCP client tiurned on on a managed switch so it can receive an IP address from the router.

A switch can have its own DHCP as well suggest you do some reading on swicthes.
Network switch - Wikipedia, the free encyclopedia

 

[jvamos]

I was always under the impression switches worked off of mac addresses. I am going to check but I am fairly certain my switch isn't serving DHCP as I would have way more difficulties. I will try and find a way into the switch if there is a GUI.