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

Wrong IP in NLTest

Hi,

Hoping someone out there knows where a setting comes from...

Running the command 'nltest /dsgetdc: DOMAIN.com' on a DC:
DC: \\DC.DOMAIN.COM
 Address: \\169.254.242.118
 Dom Guid: <hidden GUID>
 Dom Name: DOMAIN.COM
 Forest Name: DOMAIN.COM
 Dc Site Name: London
 Our Site Name: London
        Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST CLOSE_SITE FULL_SECRET WS DS_8
The command completed successfully

Open in new window


I've looked everywhere to locate where it's pulling this blatantly incorrect 169 IP address from and cannot locate it anywhere!

Anyone know where it gets this address from so I can get rid of it??

I have confirmed no NIC is active with an APIPA address, (but a disabled NIC could have picked that up way back when the server was first built.)
no DNS entries have been located with it
nslookup resolves the correct IP for the server when tested
DCDiag /test:dns comes back with no issues.

Already tried the suggestions in:
http://www.minasi.com/forum/topic.asp?TOPIC_ID=7356
http://www.winvistatips.com/wrong-ip-address-t772421.html

Windows 2012 Standard DC on 2003 Functional level domain/forest.
2 AD sites, 4 DCs in total.
1
Steve
Asked:
Steve
2 Solutions
 
Rob StoneCommented:
The boxes I've ran this on uses the primary IP with highest priority metric value.

If you run the following does it show anything unusual:
netsh interface ipv4 show addresses

I presume it runs OK on the other DC's?
0
 
MaheshArchitectCommented:
Can you please post ipconfig /all output on DC here

Mahesh
0
 
SteveAuthor Commented:
Thanks Stoner79. That pointed me in the right direction.

There was an old NIC that doesn't show up anywhere but in netsh. I couldn't remove it but I did manage to set a lower priority metric and that's solved the issue.

The IP is now correct.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Rob StoneCommented:
Glad it helped :)
0
 
SteveAuthor Commented:
Stoner79's comment was exactly what I was after as it helped me locate the issue and find a way to resolve it.
0
 
Bruno CordeiroCommented:
I had this problem yesterday, my AD replication stopped because I was APIPA address as principal, after detecting the network interface that was with this IP , deactivated the interface and had to restart the server and replication is restored.

Tks!!
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

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