IP Address Conflict

[Falcon99]

Here is my problem:

WinServer2003 DHCP , 50 stations

Station-A: local ping is 10.1.1.144
Ping Station-A from network shows 10.1.1.145

Station-B: pings 10.1.1.145 local and on net

Server DHCP IP Lease List shows 10.1.1.145 as Station-B
10.1.1.144 is not listed.

Both machines seem to have normal network access.
I have done all ipconfig commands that I know of.

I release and renew it (Station-A) but it keeps grabbing 10.1.1.144, and that ip nevers appears on the lease list.

Thanks in advance.

George

 

[pgaliardo]

Can you post your ipconfig/all?

 

[Falcon99]

Windows IP Configuration

Host Name . . . . . . . . . . . . : station-A
Primary Dns Suffix . . . . . . . : abc.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : abc.local
abc.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : abc.local
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-07-E9-26-1B-82
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.1.1.144
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.1.1.3
DHCP Server . . . . . . . . . . . : 10.1.1.30
DNS Servers . . . . . . . . . . . : 10.1.1.30
Primary WINS Server . . . . . . . : 10.1.1.30
Lease Obtained. . . . . . . . . . : Friday, May 09, 2008 8:20:55 AM
Lease Expires . . . . . . . . . . : Tuesday, May 13, 2008 8:20:55 AM


Thanks

 

[Falcon99]

I rebooted and found this warning in the system event viewer. Needless to say I had tried reregistering the DNS earlier.

DNSAPI Event:11163

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

Adapter Name : {593089BF-519C-4AD6-B4EB-8EF5E3C73CCE}
Host Name : station-A
Primary Domain Suffix : abc.local
DNS server list :
10.1.1.30
Sent update to server : 10.1.1.1
IP Address(es) :
10.1.1.144

The reason the system could not register these RRs was because the DNS server failed the update request. The most likely cause of this is that the authoritative DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.

You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator.


Thnx

 

[LawnBoy]

Try resetting your tcp/ip stack on Station-A.
netsh winsock reset


"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 

[Falcon99]

Lawnboy;

Thanks, resetting winsock had no effect.


George

 

[LawnBoy]

You might get more suggestions in the W2K3 forum.


"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 

[pgaliardo]

2 long shots you can try:

Manually delete the DNS Entry on your server
In DHCP. set up 10.1.1.144 as an exception so that it is not handed out. Then try and Ipconfig release and renew on workstation a

 

[Falcon99]

Thanks all,

The DNSAPI event error was the key. I deleted the Station-A host record in the DNS server. It showed the tie to the duplicate IP 10.1.1.145.

I rebooted, didn't need to reregister DNS.

BTW, I only came across this because I could not remote desktop to this one particular pc.


George