Still thinks it has old IP Address

[niallo32]

I have a Windows 2003 Terminal Server that I am trying to get Load-Balancing working with. It has two Nic's, one for the LAN and one for the Load Balancing.

The LAN Nic has an IP addy of 10.x.x.209
The LB Nic has an IP addy of 10.x.x.207, plus the IP Addy of the Cluster I setup, which is 10.x.x.210.

Our ISP NAT'd a public IP to .209, I thought if I change the IP Addy of the cluster to .209, and the IP addy on the LAN card to .210, then the Load Balancing would work.

It gave me IP address conflicts when I made the change, I changed it back, the LAN Nic is not sending/receiving any data on the LAN and when I Ping the Server by name, it pings the .210 address.

Any ideas how I can get the LAN nic to back thinking it has the .209 address?

Thanks,

 

[Dmasch]

Search the registry for the old IP address and remove all keys.

 

[niallo32]

I need to keep the .209 address as the IP Addy of the LAN Nic and need to keep the .210 address as the second addy on the Load Balancing Nic.

Is there a way I can get the Server back to thinking it has an Internal address of .209?

Thanks

 

[niallo32]

Anyone got any ideas?

When I connect to either of the Load Balancing Clusters, they do not connect because of the IP conflict.

The LAN Nic on the Server is still not sending/receiving any packets, and when I click 'Repair' under properties, I get the following error message:

'The following steps of the repair operation failed: Flushing the ARP cache'


Thanks

 

[niallo32]

Anyone got any ideas how to fix this?

When I try to log into the Terminal Server with the damaged TCP/IP Protocol, it logs me into the other Terminal Server.

I have been told I may need to reinstall Windows Server 2003 - if I do this, will it keep my settings intact?

Is this my only option?

Thanks

 

[Stevehewitt]

To flush the ARP Cache manually, go to command prompt and type in the following:

arp -d or arp -d *
Try arp -a to check that it has cleared them all.

Steve.

 

[niallo32]

I issued both of those commands from DOS; both arp -d & arp -d * executed apparantly correctly.

When I typed arp -a , it returned the IP Address of the Domain controller & the IP Address of it's Gateway.

It still is'nt receiving any data on the 2nd Nic.

Any ideas what to do?

Thanks

 

[niallo32]

Anyone got any ideas on this?

Do I need to reinstall Windows Server 2003?

Is there any other way around this?

 

[rrevuru]

Iam not a pro,but something it sounds like the issue with the NIC card. I would disable it and enable it and see if it works, also i would try to change the NIC card alone insteading re-installing the 2003 server.

 

[niallo32]

I tried disabling the Network card and reenabling it, but it made no difference.

The same thing happened when I tried to repair - 'The following steps of the repair operation failed: Flushing the ARP cache'

If I replace the Network Card, will it work?

 

[niallo32]

Anyone got any ideas?

 

[niallo32]

Bump,

I manually changed any mention of the .210 address in the registry but it's made no difference.

In the Event Log, I get the following error:

DNSAPI - 11164
----

The system failed to register host (A) resource records (RRs) for network adapter
with settings:

Adapter Name : {94DAF77F-84F8-44B7-B44D-FEA288DE882B}
Host Name : Servername
Primary Domain Suffix : Domain Name
DNS server list :
10.0.2.9
Sent update to server : 159.134.237.61
IP Address(es) :
10.0.2.208

The reason the system could not register these RRs was because either (a) the DNS server does not support the DNS dynamic update protocol, or (b) the authoritative zone for the specified DNS domain name does not accept dynamic updates.

To register the DNS host (A) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.

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

I also manually added the IP Addy of the Load Balancing Card into Static Mappings in WINS and then restarted the Service - it has'nt made any difference

Any suggestions?

Thanks