Re: Find AD hostname from Linux command line

I don't want to turn off the Linux DHCP server from assigning the IP to
the Windows machine.

Didn't suggest that, although I don't know why you don't just let the
windows server do this. Integration between DHCP and DNS is soooo easy that
way. What I suggested is that the hostname is possibly being assigned to the
DHCP clients by the DHCP server. As I said, Windows boxes use their
computernames as hostnames by default. Since your computers are registered
as something different, it would appear (from the limited information we
have to work with here) that a good possibility is that the DHCP server is
assigning the hostname. You can disable that one feature on the DHCP server
(not the whole DHCP server). I also gave you a method of checking whether or
not the hostname on an XP workstation is the same as it's NetBIOS name, by
typing "hostname" at a command prompt. That should tell you with certainty
that the hostname of the computer is different than it's computername. Just
how it got to be different will require more info to solve. Maybe it's not
different. We'll never know until you check it out and post what you find.

And I have to allow the Active Directory to
continue to do whatever it is does when it assigns a "hostname" of the
form *.ad.mydomain.com.

Active directory does not assign hostnames.

What I want to do is from the Linux server find
out what name the AD server assigned the Windows client given the
Windows client's IP address.

Once again, AD does not assign hostnames.


Yes, there are two different zones at work here: how do I query the AD
server to find out what it thinks the Windows machine name is? A simple
"nslookup 192.168.10.11" always returns the *.mydomain.com hostname,
whereas I want to get the *.ad.mydomain.com result.

That is what is listed in the reverse lookup zone. You'll have to find out
how your reverse lookup zones are being updated. Once again, do you get the
same result from an nslookup on one of the windows boxes? Maybe the Linux
box has static entries in it's hosts file? Maybe the reverse zone was set up
manually on the DNS server? Once again, step by step until you can pinpoint
where the descrepencies lie.

....kurt


.

Relevant Pages

  • Re: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie
    ... This results in windows 2008 R2 in the error message: The specified DHCP ... Migration with netsh has worked. ... Migrating DHCP using the Windows Server 2008 R2 Migration Tools ...
    (microsoft.public.win2000.networking)
  • Re: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie
    ... This results in windows 2008 R2 in the error message: The specified DHCP client is not a reserved client. ... Migration with netsh has worked. ... Migrating DHCP using the Windows Server 2008 R2 Migration Tools ...
    (microsoft.public.win2000.networking)
  • Re: Wide area failures?
    ... The W2003 server is the DNS host/primary nameserver. ... was informed just this afternoon that DHCP updating to the DNS server ... to create a Windows Domain Server and apply ADS in the near future. ...
    (microsoft.public.windows.server.dns)
  • Re: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie
    ... Mit Windows 2008 R2 führt dies zu der bekannten Fehlermeldung: ... Die netsh Migration hat funktioniert. ... Migrating DHCP using the Windows Server 2008 R2 Migration Tools ...
    (microsoft.public.win2000.networking)
  • Re: server lockup issue - narrowed down
    ... DHCP works, re-ran all wizards. ... fine from clients and server. ... You cannot start the Routing and Remote Access service on a Windows 2000 ... I also have had multiple nics in the machine at different times. ...
    (microsoft.public.windows.server.sbs)
Loading