Windows 2008 multiple network cards don't work

I have installed Windows Server 2008 x64 Enterprise edition and I setup 2
NICs on it. They're setup in different VLANs on a Cisco 6513 switch. Here's
the config:

1st NIC
172.16.0.63
255.255.252.0
172.16.0.1 gateway

2nd NIC

172.30.7.15
255.255.255.0
(no gateway setup)

I cannot ping the IP address on the 2nd NIC 172.30.7.15 from any computer on
the domain.

I can ping the 1st NIC just fine. I can also ping the 2nd NIC from the
switch itself but not from any other computer in the network.

----------------------------

I have the exact same setup on a Windows 2003 server and it works just fine.
Here's my troubleshooting steps:

1. Turned off Windows firewall
2. Turned Network discovery On and Off, it didn't make any difference.
3. checked the binding order in Advanced properties and made it match the
2003 server
4. Turned off IPV6 on all the NICs.

It seems to be the server not responding to any clients, except for the
switch itself.

In message <4DA89CFC-5BD2-4DFC-9E48-(E-Mail Removed)> Gilbert
<(E-Mail Removed)> was claimed to have wrote:

>I have installed Windows Server 2008 x64 Enterprise edition and I setup 2
>NICs on it. They're setup in different VLANs on a Cisco 6513 switch. Here's
>the config:
>
>1st NIC
>172.16.0.63
>255.255.252.0
>172.16.0.1 gateway
>
>2nd NIC
>
>172.30.7.15
>255.255.255.0
>(no gateway setup)
>
>I cannot ping the IP address on the 2nd NIC 172.30.7.15 from any computer on
>the domain.
>
>I can ping the 1st NIC just fine. I can also ping the 2nd NIC from the
>switch itself but not from any other computer in the network.

This might be a stupid question, but are you trying to ping from a
client in 172.30.7/24 or from computers located in another subnet?

You may want to use tarcert to find out where the traffic stop.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Gilbert" <(E-Mail Removed)> wrote in message
news:4DA89CFC-5BD2-4DFC-9E48-(E-Mail Removed)...
>I have installed Windows Server 2008 x64 Enterprise edition and I setup 2
> NICs on it. They're setup in different VLANs on a Cisco 6513 switch.
> Here's
> the config:
>
> 1st NIC
> 172.16.0.63
> 255.255.252.0
> 172.16.0.1 gateway
>
> 2nd NIC
>
> 172.30.7.15
> 255.255.255.0
> (no gateway setup)
>
> I cannot ping the IP address on the 2nd NIC 172.30.7.15 from any computer
> on
> the domain.
>
> I can ping the 1st NIC just fine. I can also ping the 2nd NIC from the
> switch itself but not from any other computer in the network.
>
> ----------------------------
>
> I have the exact same setup on a Windows 2003 server and it works just
> fine.
> Here's my troubleshooting steps:
>
> 1. Turned off Windows firewall
> 2. Turned Network discovery On and Off, it didn't make any difference.
> 3. checked the binding order in Advanced properties and made it match the
> 2003 server
> 4. Turned off IPV6 on all the NICs.
>
> It seems to be the server not responding to any clients, except for the
> switch itself.

I did a TRACERT and it stops at the switch/router. I have a Cisco 6513
switch that acts as the gateway and I have multiple VLANs configured on it.

I also did a packet capture on the server itself and it does see the traffic
coming from 172.31.6.5 but it's just not replying to it.


"Robert L. (MS-MVP)" wrote:

> You may want to use tarcert to find out where the traffic stop.
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "Gilbert" <(E-Mail Removed)> wrote in message
> news:4DA89CFC-5BD2-4DFC-9E48-(E-Mail Removed)...
> >I have installed Windows Server 2008 x64 Enterprise edition and I setup 2
> > NICs on it. They're setup in different VLANs on a Cisco 6513 switch.
> > Here's
> > the config:
> >
> > 1st NIC
> > 172.16.0.63
> > 255.255.252.0
> > 172.16.0.1 gateway
> >
> > 2nd NIC
> >
> > 172.30.7.15
> > 255.255.255.0
> > (no gateway setup)
> >
> > I cannot ping the IP address on the 2nd NIC 172.30.7.15 from any computer
> > on
> > the domain.
> >
> > I can ping the 1st NIC just fine. I can also ping the 2nd NIC from the
> > switch itself but not from any other computer in the network.
> >
> > ----------------------------
> >
> > I have the exact same setup on a Windows 2003 server and it works just
> > fine.
> > Here's my troubleshooting steps:
> >
> > 1. Turned off Windows firewall
> > 2. Turned Network discovery On and Off, it didn't make any difference.
> > 3. checked the binding order in Advanced properties and made it match the
> > 2003 server
> > 4. Turned off IPV6 on all the NICs.
> >
> > It seems to be the server not responding to any clients, except for the
> > switch itself.
>
>

I have exactly the same issue did you manage to resolve it?

"Gilbert" wrote:

> I did a TRACERT and it stops at the switch/router. I have a Cisco 6513
> switch that acts as the gateway and I have multiple VLANs configured on it.
>
> I also did a packet capture on the server itself and it does see the traffic
> coming from 172.31.6.5 but it's just not replying to it.
>
>
> "Robert L. (MS-MVP)" wrote:
>
> > You may want to use tarcert to find out where the traffic stop.
> >
> > --
> > Bob Lin, MS-MVP, MCSE & CNE
> > Networking, Internet, Routing, VPN Troubleshooting on
> > http://www.ChicagoTech.net
> > How to Setup Windows, Network, VPN & Remote Access on
> > http://www.HowToNetworking.com
> > "Gilbert" <(E-Mail Removed)> wrote in message
> > news:4DA89CFC-5BD2-4DFC-9E48-(E-Mail Removed)...
> > >I have installed Windows Server 2008 x64 Enterprise edition and I setup 2
> > > NICs on it. They're setup in different VLANs on a Cisco 6513 switch.
> > > Here's
> > > the config:
> > >
> > > 1st NIC
> > > 172.16.0.63
> > > 255.255.252.0
> > > 172.16.0.1 gateway
> > >
> > > 2nd NIC
> > >
> > > 172.30.7.15
> > > 255.255.255.0
> > > (no gateway setup)
> > >
> > > I cannot ping the IP address on the 2nd NIC 172.30.7.15 from any computer
> > > on
> > > the domain.
> > >
> > > I can ping the 1st NIC just fine. I can also ping the 2nd NIC from the
> > > switch itself but not from any other computer in the network.
> > >
> > > ----------------------------
> > >
> > > I have the exact same setup on a Windows 2003 server and it works just
> > > fine.
> > > Here's my troubleshooting steps:
> > >
> > > 1. Turned off Windows firewall
> > > 2. Turned Network discovery On and Off, it didn't make any difference.
> > > 3. checked the binding order in Advanced properties and made it match the
> > > 2003 server
> > > 4. Turned off IPV6 on all the NICs.
> > >
> > > It seems to be the server not responding to any clients, except for the
> > > switch itself.
> >
> >

I figured out with a call to Microsoft Tech support.

Windows 2008 introduces a "strong host model" that doesn't allow the
different NICs to talk to each other. For example, if a request comes in on
the 2nd NIC and there's no default gateway setup, then the NIC will not use
the 1st NIC to reply to the requests. (even though there's a default gateway
setup on that 1st NIC).

In order to change that behaviour and go back to a 2003 model, you go to the
command prompt and then you type:

netsh interface ipv4 set interface NLB weakhostreceive=enable
netsh interface ipv4 set interface NLB weakhostsend=enable

(where NLB is the name of the network interface... default is Local Area
Connection)

As an alternative, you can set a default gateway on the 2nd NIC but that can
introduce more problems where the system doesn't know which way to send
traffic. MS said that I could set the metric to 2 on the 2nd NIC and that
way it will only be used if the 1st NIC is unavailable.

http://technet.microsoft.com/en-us/m....cableguy.aspx

"GJP" wrote:

> I have exactly the same issue did you manage to resolve it?
>
> "Gilbert" wrote:
>
> > I did a TRACERT and it stops at the switch/router. I have a Cisco 6513
> > switch that acts as the gateway and I have multiple VLANs configured on it.
> >
> > I also did a packet capture on the server itself and it does see the traffic
> > coming from 172.31.6.5 but it's just not replying to it.
> >
> >
> > "Robert L. (MS-MVP)" wrote:
> >
> > > You may want to use tarcert to find out where the traffic stop.
> > >
> > > --
> > > Bob Lin, MS-MVP, MCSE & CNE
> > > Networking, Internet, Routing, VPN Troubleshooting on
> > > http://www.ChicagoTech.net
> > > How to Setup Windows, Network, VPN & Remote Access on
> > > http://www.HowToNetworking.com
> > > "Gilbert" <(E-Mail Removed)> wrote in message
> > > news:4DA89CFC-5BD2-4DFC-9E48-(E-Mail Removed)...
> > > >I have installed Windows Server 2008 x64 Enterprise edition and I setup 2
> > > > NICs on it. They're setup in different VLANs on a Cisco 6513 switch.
> > > > Here's
> > > > the config:
> > > >
> > > > 1st NIC
> > > > 172.16.0.63
> > > > 255.255.252.0
> > > > 172.16.0.1 gateway
> > > >
> > > > 2nd NIC
> > > >
> > > > 172.30.7.15
> > > > 255.255.255.0
> > > > (no gateway setup)
> > > >
> > > > I cannot ping the IP address on the 2nd NIC 172.30.7.15 from any computer
> > > > on
> > > > the domain.
> > > >
> > > > I can ping the 1st NIC just fine. I can also ping the 2nd NIC from the
> > > > switch itself but not from any other computer in the network.
> > > >
> > > > ----------------------------
> > > >
> > > > I have the exact same setup on a Windows 2003 server and it works just
> > > > fine.
> > > > Here's my troubleshooting steps:
> > > >
> > > > 1. Turned off Windows firewall
> > > > 2. Turned Network discovery On and Off, it didn't make any difference.
> > > > 3. checked the binding order in Advanced properties and made it match the
> > > > 2003 server
> > > > 4. Turned off IPV6 on all the NICs.
> > > >
> > > > It seems to be the server not responding to any clients, except for the
> > > > switch itself.
> > >
> > >

Problems:

1. The Server is not a "router",...it is a server. So if it receives a
packet for a particular IP# it owns,...but receives it on the *wrong* Nic it
may not it may not "route" the packet across from one interface to the
other. I'm not positive about that because I would pretty much never do it
and would never create this kind of situation.

2. The Cisco switch,...if it is only a Switch,...is *NOT* a router and
cannot route packets anywhere. Just because you can create VLans on the
Switch does not mean the Switch has the correct routing functionality to do
this. If it has the routing ability it will be called specifically a Layer3
Switch, which means it is a Router and a Switch built into the same piece of
hardware. If that is true then you would call it a Switch when refering to
its Layer2 abilities and call it a Router when refering to its routing
abilties,...in other words treat it like it was two separate devices even
though it isn't. This way people will know what you are actually meaning.

Anyway,...if it is a Layer3 Switch, then it needs a Static Route added to it
so that is "knows" where the 172.30.7.0 network is located. It will use the
other interface of the server as the "gateway". So it would look like this:

Network ID: 172.30.7.0
Mask: 255.255.255.0
Gateway: 172.16.0.63
Metric: <leave alone>

Then all the Clients on both networks (172.16.0.0 & 172.30.7.0) will have to
use the Layer3 Switch as their Default Gateway. Depending on the LAN
Design, things can get ugly really fast with making it work,...which usually
happens when people refuse to listen to me on this subject,....which happens
way too often. :-)


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


"Gilbert" <(E-Mail Removed)> wrote in message
newsDA20D1A-8001-47E8-8F28-(E-Mail Removed)...
>I did a TRACERT and it stops at the switch/router. I have a Cisco 6513
> switch that acts as the gateway and I have multiple VLANs configured on
> it.
>
> I also did a packet capture on the server itself and it does see the
> traffic
> coming from 172.31.6.5 but it's just not replying to it.
>> "Gilbert" <(E-Mail Removed)> wrote in message
>> news:4DA89CFC-5BD2-4DFC-9E48-(E-Mail Removed)...
>> >I have installed Windows Server 2008 x64 Enterprise edition and I setup
>> >2
>> > NICs on it. They're setup in different VLANs on a Cisco 6513 switch.
>> > Here's
>> > the config:
>> >
>> > 1st NIC
>> > 172.16.0.63
>> > 255.255.252.0
>> > 172.16.0.1 gateway
>> >
>> > 2nd NIC
>> >
>> > 172.30.7.15
>> > 255.255.255.0
>> > (no gateway setup)
>> >
>> > I cannot ping the IP address on the 2nd NIC 172.30.7.15 from any
>> > computer
>> > on
>> > the domain.
>> >
>> > I can ping the 1st NIC just fine. I can also ping the 2nd NIC from the
>> > switch itself but not from any other computer in the network.