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:
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.
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 successfullyI'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.
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.
Glad it helped :)
ASKER
Stoner79's comment was exactly what I was after as it helped me locate the issue and find a way to resolve it.
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!!
Tks!!
Mahesh