Windows Server 2003 RC2 x64 - 2 NIC - 2VLAN - Ping in but not out.

[JarredK]

Here is our setup

Switch 3548

Two Vlans
vlan 1 Public Internet Access
vlan 2 Private Network Access

Servers all have

2 Broadcom build in gigibit network adapters

4 intel gigabit network adapters on a PCI expansion card



I made some changes today so I will give the configurations pre and post changes

Pre Change


Broadcom Port 1 is connected with vlan 2 and a static IP address

Broadcom Port 2 is connected with vlan 1 and a static IP address

When servers first start, I can ping vlan 2 (10.4.4.x) and I can also ping all vlan 1 up to and including my gateway. However I cannot ping past gateway, however can ping into the box sometimes. I can disable the broadcom port 2 adapter and then re-enable it and then I can start pinging out as well as in. However, ever 24 to 36 hours the intel port 1 stops working, requires another disable and re-enable to resume working.

Post Changes, today I change things around until they are as follows:

Broadcom Port 1 is connected with vlan 2 and a static IP address

Intel Port 1 is connected with vlan 1 and a static IP address

When servers first start, I can ping vlan 2 (10.4.4.x) and I can also ping all vlan 1 up to and including my gateway. However I cannot ping past gateway, however can ping into the box sometimes. I can disable the intel port 1 adapter and then re-enable it and it still will not ping out. I can disable broadcom port 1 and then everything works fine.

I also have one box on this configuration:

Inte Port 2 is connected with vlan 2 and a static IP address

Intel Port 1 is connected with vlan 1 and a static IP address

When servers first start, I can ping vlan 2 (10.4.4.x) and I can also ping all vlan 1 up to and including my gateway. However I cannot ping past gateway, however can ping into the box sometimes. I can disable the intel port 1 adapter and then re-enable it and it still will not ping out. I can disable intel port 2 and then everything works fine.

I am honestly stumped, I have never seen windows act this way, any help would be appreciated greatly.

Jarred

 

[ADB100]

You can only have 1 default-gateway active at any one time, check the routing table from a command prompt (route print). You can manually add static routes using the 'route add' command however these are not dynamic - i.e. if a gateway goes down Windows won't magically switch the route to a different gateway.
Windows is always happier with a single NIC (teamed or physical), otherwise you have to administer a local IP routing table.

HTH

Andy

 

[JarredK]

So I should add the "private network" gateway int he route add, but let windows manage the "public network