Can't bind Static IP to network cards
Right the info, I recently had to restore a Dead Server to a completly different machine. The restore worked for pretty much everything (This is a DC Win 2K server and running Exchnage 2003), I used Acronis universal restore for the rebuild. Anyway the nics on the current computer are totaly different, with the new ones being Intel Gb, I'm not sure what the old ones were, but whatever flavour Dell have on their PowerEdge 2400's.
The nic will use DHCP and I can assign a static IP, however if I look at the Nic properties box after I have assigned the IP their ip isn't showing, but an ipconfig will show the addresses, info below
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : cornhill
Primary DNS Suffix . . . . . . . : boyden-financial.co.uk
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : boyden-financial.co.uk
Ethernet adapter Local Area Connection 5:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 PM Network Connect
ion #3
Physical Address. . . . . . . . . : 00-30-48-84-6F-14
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.254
DHCP Server . . . . . . . . . . . : 255.255.255.255
DNS Servers . . . . . . . . . . . :
Primary WINS Server . . . . . . . : 192.168.0.101
Secondary WINS Server . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : 24 January 2007 05:44:18
Lease Expires . . . . . . . . . . : 24 January 2007 06:44:18
Ethernet adapter Local Area Connection 4:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 PM Network Connect
ion #2
Physical Address. . . . . . . . . : 00-30-48-84-6F-15
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.254
DNS Servers . . . . . . . . . . . : 192.168.0.1
192.168.0.101
The wierd bit is Coonection 4 says DHCP no and 5 Says Yes, however none of the nics show IP in the properties box. Plus if I reboot the nics pick up DHCP, which given this machines role, it's not good.
More Info.
I have removed the old Nics using the show hidden devices command. Also adding another nic isn't an option as I don't have any half height nics to put in it, this client is pretty stingy and I can't see them stumping up for one.
Any help here gratfully accepted
The nic will use DHCP and I can assign a static IP, however if I look at the Nic properties box after I have assigned the IP their ip isn't showing, but an ipconfig will show the addresses, info below
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : cornhill
Primary DNS Suffix . . . . . . . : boyden-financial.co.uk
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : boyden-financial.co.uk
Ethernet adapter Local Area Connection 5:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 PM Network Connect
ion #3
Physical Address. . . . . . . . . : 00-30-48-84-6F-14
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.254
DHCP Server . . . . . . . . . . . : 255.255.255.255
DNS Servers . . . . . . . . . . . :
Primary WINS Server . . . . . . . : 192.168.0.101
Secondary WINS Server . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : 24 January 2007 05:44:18
Lease Expires . . . . . . . . . . : 24 January 2007 06:44:18
Ethernet adapter Local Area Connection 4:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 PM Network Connect
ion #2
Physical Address. . . . . . . . . : 00-30-48-84-6F-15
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.254
DNS Servers . . . . . . . . . . . : 192.168.0.1
192.168.0.101
The wierd bit is Coonection 4 says DHCP no and 5 Says Yes, however none of the nics show IP in the properties box. Plus if I reboot the nics pick up DHCP, which given this machines role, it's not good.
More Info.
I have removed the old Nics using the show hidden devices command. Also adding another nic isn't an option as I don't have any half height nics to put in it, this client is pretty stingy and I can't see them stumping up for one.
Any help here gratfully accepted
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
jessmca :
The only problem with right-clicking the network card is it is no longer installed, yet he still have conflicts. I've seen this many times where you have a wireless card, set up a static IP, pull the card, then try to enter the same IP on an existing NIC. You'll receive errors of conflict. This is what I was assuming is happening with DBrookfield.
jocasio
The only problem with right-clicking the network card is it is no longer installed, yet he still have conflicts. I've seen this many times where you have a wireless card, set up a static IP, pull the card, then try to enter the same IP on an existing NIC. You'll receive errors of conflict. This is what I was assuming is happening with DBrookfield.
jocasio
ASKER
Ok guys maybe I should say more, I'm well aware of the dangers of having wins pointing to both nics as well as the DNS, it is only like this so it will work. Remember this is a DC with Exchange and it needs to do it's job. IPCONFIG shows one card as static, BUT IT ISN"T (sorry about caps), if you look at the properties of both cards in TCIP they are both empty and saying DHCP. There is no wireless on this and has never been, it is a Domain Controller. Interesting point about the registry, I'd assumed that removing the non-existent device from device manager would do this, one lesson there never assume anything. I'll check the registry as soon as I can
Sadly I can't pull any of these cards as they are onboard (as in on the mnotherboard).
Will check registry, thanks so far for the pointers.
Sadly I can't pull any of these cards as they are onboard (as in on the mnotherboard).
Will check registry, thanks so far for the pointers.
DBrookfield, I was mentioning the wireless because I have seen the same behavior using a wireless card where you remove it from your pc/laptop without removing the static ip address and then having conflicts when you want to add another NIC card with the same ip address. I've never had this happen with a NIC card, although I am assuimng you would run intothe exact same issue if you just pulled it out. When you restored your machine, the registry still thinks you have the old NIC card which is assigned that particular IP address so it's not going to let you assign it again...
I hope I'm not missing your point...
jocasio
I hope I'm not missing your point...
jocasio
ASKER
Sorry, I was just trying to give all info, I think you are all on the right path with the registry, I've not spent ages digging registry values so i've taken a back up and will post relevent data, comments much appreciated, I was just trying to make sure I gave all info so people wouldn't cover old ground.
The problem is there are several IP avlues and I wouldn't know whihc was orphaned or not. I'm assuming { } means orphaned but I have no idea.I would have hoped teh regisry held the mac address of the nic, which would be really helpful in tracking down this sort of thing, but it doens't (as far as I can see)
Cheers so far
David
The problem is there are several IP avlues and I wouldn't know whihc was orphaned or not. I'm assuming { } means orphaned but I have no idea.I would have hoped teh regisry held the mac address of the nic, which would be really helpful in tracking down this sort of thing, but it doens't (as far as I can see)
Cheers so far
David
The values in the {} are the GUID (Globally Unique IDentifiers) for each of the NICs. You're right in that it would have been just as simple for them to use the MAC Address as all devices should have unique MAC Addresses. What you need to do is click on each one and see which one had the rogue IP address and change that value (maybe to something in the same IP range as your network or even 0.0.0.0).
Remember which one you changed so you can change it back if it does not give you the desired results.
jocasio
Remember which one you changed so you can change it back if it does not give you the desired results.
jocasio
ASKER
Ahh sadly if only it was that easy, both my current nics have to have .1 or .101 whihc was the prvious IP's so no way of knowing which one :( Hey ho looks like I have some work changing firewall rules over the weekend :( and then I can change the IP's. It may be worthwhile me disabling the Nics at the Bios, hopefully that would remove teh current nics from the registry and I can work from there. If only IT was easy hey ;) Thanks so far for the imput :)
ASKER
Oh yes I should have said beofre, I did re-install drivers, that was the first thing I did, so we can tick that one off :-)
ASKER
Ok I've been really busy so haven't been able to do anything about this problem just yet, I'm thinking about just putting a Nic in and disabling the onboard nics and see if that works. Will credit where it is due when I've done tried this, all your help was greatly appreciated. Will update as oon as I can.
You may want to first uninstall the existing NIC cards. Then when you go into the registry, the existing keys should be for the ophaned NIC Cards....THEORETICALLY....
jocasio