Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2127
  • Last Modified:

Windows 2008 Server second intranet NIC causes first NIC Internet to disconnect

I have two NIC connections on IBM server running Windows 2008 Server w/ SQL 2008. The first NIC has been running great for the first month while in production at client site. We have now moved the CISCO ASA 5500 from the old 2003 server second intranet NIC to this new 2008 Server on its second NIC card.

The config on the first NIC for Internet is ip 192.168.2.7 / sm 255.255.255.0 / gw 192.168.2.10 / dns 192.168.2.10. .10 is our ZyWALL firewall device.

The config on the second NIC for CISCO is ip 192.168.3.2 / sm 255.255.255.0. No gw or dns.

When I enable the second NIC - its cause all the clients to lose connection to the server. They can't ping 192.168.2.7 anymore. However I can still get out on Internet from the server console. If I disable the 2nd NIC - the clients can ping the server again.

What is causing this? It worked fine on the 2003 server. Thanks.
0
interc3905
Asked:
interc3905
1 Solution
 
giltjrCommented:
Are all of the clients in the 192.168.2.0/24 subnet?  
If not, do they have a specific route to get to 192.168.2.0/24 or do they use their default route/gw?

Have you displayed the routing table on the server?

netstat -rn

What does it look like before you enable NIC2 and after you enable NIC2?

0
 
Darius GhassemCommented:
If you have a internal DNS server then point the server to this DNS server in your TCP\IP properties.

Go to your Network Connections click Advance Settings check your binding order to make sure your primary NIC is listed first.
0
 
interc3905Author Commented:
I reversed the settings on the two NIC cards and now it works. Also found this TIP from Microsoft:

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)

 - Jim
0
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.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now