• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 487
  • Last Modified:

Network Cards not working in Windows 2008

Dear All,

I have installed windows 2008 enterprise in two servers. Those servers have 2 NIC for each. First NIC connected to our network. The second NIC connected cross with another server.

I connect the first NIC to our network and everything is ok. When I connect the Private NIC cross between two servers, I loss the network connectivity, I cant ping, I cant access both servers remotely.

I uncheck the IPv6 from both network cards (Privet & public NICs) but this is not change anything. What should I do to solve this issue?

Thank
0
Arabsoft-ACS
Asked:
Arabsoft-ACS
  • 7
  • 5
1 Solution
 
vikasjusCommented:
What is make and model of Servers. If servers NIC are 1GBPS and above then try to use straight cable.
0
 
Arabsoft-ACSAuthor Commented:
It's 1 Gb, but i need to connect both NIC cross between each other, does straight cable will work for this???

Servers Model HP DL 380 G5
0
 
vikasjusCommented:
If it is pure 1GBPS card then straight cable should work.
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
Arabsoft-ACSAuthor Commented:
Dear Vikasjus,

What do you mean it's pure 1GBPS?

Also, why the problem happened?
0
 
Arabsoft-ACSAuthor Commented:
In additional; I need to connect both servers cross, this is a required to installed a cluster mailbox Exchange 2007
0
 
vikasjusCommented:
Pure 1GBPS means it should not be 10/100/1000 or 100/1000. Most of the 1gbps cards wont work on cross cable. So put straight cable even if you want to configure it as cluster.
0
 
peter41Commented:
Hi Arabsoft-ACS,
I think problem is only in TCP/IP and routing configuration for servers.
First:
In TCP/IP on every server configure default gateway only on one NIC (connected to network)
on the second NIC leave default gateway empty.
Second:
By connecting two servers with cable (cross-over or patch - if it's Gigabit) there must be set different subnet than subnet on LAN.
For example:
Server1 is connected to LAN where is subnet 192.168.1.0/255.255.255.0 and for network cards connected directly set IP addresses from  different: 192.168.2.0/255.255.255.0

But still it is unclean for me where is connected second NIC of Server2 ?
Is it something different than 192.168.1.0/255.255.255.0 in this example ?
0
 
Arabsoft-ACSAuthor Commented:
Dear peter41,

No default gateway, DNS, WINS or anything in second NIC. Just IP & Subnet mask

Both of them in another subnet (Public: 10.10.25.5/16) & (Private: 192.168.1.1/24)

second NIC of Server 2 it's connected to second NIC of Server 1 (Both Servers Connect to each other)
0
 
vikasjusCommented:
Hi,
Have you tried with normal straight through cable?
Reason why it will not work with normal cross is because gbps cards use all 4 cable pairs, where as normal cable uses only two wire cables. Current gbps cards have auto sensing capability which since cable connection and act accordingly.
0
 
Arabsoft-ACSAuthor Commented:
I tried the same cable, the problem is, I can ping and access remotely. But both NIC cards are not working even when I connect them directly by straight cable. They have the red x (like they are not connected).
0
 
Arabsoft-ACSAuthor Commented:
Dear All,

I change the network cable (cross), now; I can ping and I can see the network. The only problem remaining issue is that, I cannot access the servers remotely. When I disable the private NIC, the remote connection is working find.

Something related to remote desktop (I use Windows Remote Desktop which default in window)
0
 
vikasjusCommented:
Some confusion. When you use stright cable you are able to ping and perform remote access. but card shows red cross.
If you change to cross then you can ping but not able to take remote controle.
with cross cable and private NIC's enable try to use private IP of server in MSTSC and update us.
0
 
Arabsoft-ACSAuthor Commented:
I find it; the problem was from windows firewall. When I switched off, everything is working fine

Thanks all
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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