Im installing an extra adapter for my windows server 2000. So I have one NIC for my main adapter IP 172.xx.x.xx, another for bkup vlan 10.250.xx.xx The issue is when I ping back the server, it will show that the ip is 10.250.xx.xxx instead of the main 172.x.x.x. , My question. 1. How can I set the adapter 172.x.x.x. becoming the main, and the other one become #2 in windows server. 2. I did have the same problem with server 2003 but it was solve by using host file. This doesnt work with server 2000. Pls help ASAP since I have to complete my CommVault project.

You might have to change the binding order of the Nic http://support.microsoft.com/kb/894564http://www.virmansec.com/blogs/skhairuddin

Hi, In addition to Syed. 1. First of all, please double check the binding order in the registry: Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Linkage Registry value: Bind Cannot Change the Binding Order for Remote Access Connections http://support.microsoft.com/kb/311218 2. What will happen if you TRACERT the traffic to the resource on 10.100.22.0/24 subnet? How to Use TRACERT to Troubleshoot TCP/IP Problems in Windows http://support.microsoft.com/kb/314868 Thanks.

When you say that you "ping back the server" can you clarify what you mean? Do you mean you're pinging the server from another machine on the network by its host name? Does the server you're pinging it from also have the 172 network as its primary? If you're pinging the server by name and that name is being resolved to the 10 network, then it must be getting that address from somewhere. Have you checked to see if the second NIC is configured to publish its address to DNS?

Keith, I ping the server using its hostname from the server itself. Second NIC is not configured to publish its address to DNS

Ross, OK, in that case, have you configured the backup nic to have a gateway address? Only one of your NIC's (the default one) should have one. Eg, your main adaptor will have the IP, subnet, gateway and DNS servers listed, the backup vlan adaptor will just have the IP and subnet, nothing else. If you go to a command prompt and type : ipconfig /all can you let us know what output is returned please? That might give us a clue as to why your server is apparently picking the wrong one as the default.

Hello, just to mention here, hopefully that server is not a domain controller. Multihoming a DC is not recommended and should be avoided. More details about in Ace Fekay's great article: http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx If you still will use it, see the details how to configure it inside.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Thanks Keith, Let me try it first. will post the outcome later.

Keith, It doesnt work.

Syed, Not working. Still the same

Hi Ross, By default, if you ping remote server, you will receive the IP address that is replying from the same network segment with your client computer. If you'd like to receive 172.xx.x.xx, you ensure that the client computer is located in 172.xx.x.xx network or disable NIC (10.250.xx.xxx). If you'd like to achieve high availability, we suggest using NIC Teaming or server clustering . Network adapter teaming and server clustering http://support.microsoft.com/kb/254101 Brent Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Hi all, Finally manage to solve the issue. What I did was I swap the configuration for Network Connection 01 (172.x.x.x) with the one that contains the configuration Network Connection 02 (100.250.x.x). Refresh it and works like a charm. I think maybe because the older NIC have old firmware etc which Windows prioritize it as secondary NIC. Just an opinion.