lynn said the following on 04/02/2012 04:13 AM:
On 01/04/12 23:53, Anton Aylward wrote:
lynn said the following on 04/01/2012 04:53 PM:
Windows clients have something that we do not. What is it?
What are the names of the Windows hosts?
How does DNS respond when queried on their addresses? How are those names assigned?
Here is a win 7 client called LYNN-PC12@hh3.site. It has its address to be obtained automatically
"automatically" meaning WHAT? Can we see the DHCP logs and the DNS logs around that activity please.
and has 192.168.1.2 hh1.hh3.site set as the only nameserver.
Which is reasonable. If this were Linux I could do that via the DHCP server. Do you? If not, why not? And if not then how do the Linux machines get told their server? If you read the documentation on DHCP you'll see that the client daemon that runs on the clients can botan it from the DHCP server and write it to /etc/resolve.conf Are you doing that? If not, then why not?
Here is the request for the machine ticket. There must have been some communication betwen the DHCP server at 192.16.1.1, LYNN-PC12 and the KDC. LYNN-PC12 was allocated IP 192.168.1.27 but next boot, it will be different.
You can gaurentee it will be different? Would life be easier if you could get it assigned the same IP - if it was available?
Kerberos: AS-REQ LYNN-PC12$@HH3.SITE from ipv4:192.168.1.27:59048 for krbtgt/HH3.SITE@HH3.SITE
Now how is Kerboros associating name with IP address?
[...]
host LYNN-PC12 LYNN-PC12.hh3.site has address 192.168.1.27
I presumem that means you ran the 'host' command ...
host 192.168.1.27 Host 27.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
The most likely reason for that is that you don't have the reverse domain set up. If its not set up then even the most advanced DHCP or SAMBA4 can't inject reverse RRs.
Ditto for the Linux hosts. How are names assigned? Here is an openSUSE 12.1 client called LXDE2.hh3.site. Here, the same DHCP server has allocated 192.168.1.22
"The same DHCP server" ?? So the same DHCP server hands out addresses for (BOTH* the Windows machines and the Linux machines?
All OK so far. Now here is where the windows and linux clients differ:
host LXDE2 Host LXDE2 not found: 3(NXDOMAIN)
host lxde2.hh3.site Host lxde2.hh3.site not found: 3(NXDOMAIN)
host lxde2 Host lxde2 not found: 3(NXDOMAIN)
host 192.168.1.22 Host 22.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
All of which tells me that you don't have DHCP and DNS working togehter properly. I've suggested the "cheat" of pre-populating the zone files. You may also want to use constructs in DHCP like host lxde2 { hardware ethernet 00:00:00:00:00:00 ; # or whatever fixed-address 192.168.1.22 ; } and coresponding entries in the forward and backward DNS records. Yes, its a cheat, yes its "like" having static addresses, but it will work and it will prove or disprove other things, like the *need* for proper DNS instead of hacnking your hosts file. Then, perhaps, you can get DDNS to work so there is no need for the static addresses and pre-loaded zone files. Lynn: the issue here is DHCP and DNS. Its those log files I'd be interested in seeing. Make sure you have logging turned on for both (or debug to syslog)
As far as DHCP goes, either machines "know" their names and use that when asking for an IP address from the DHCP server, or they are given there names by the server, along with router, gateway, and all the other information that they should if you have DHCP set up properly.
In this setup, the machine names are fixed.
How are they "fixed"?
The DHCP is set to allocate addreses only.
WRONG! It should allocate other things like name server and routing information and should tell them how long their leases are to last. Please see the man page. option netbios-name-servers option netbios-dd-server option netbios-node-type option broadcast-address option routers Do you have those? If not, why not? Unless you have the dhcpcd on the Linux clients telling the DHCP server their individual names (and distinct names, which is why you shouldn't be buqqering around with the hosts file) then the DHCP server shold also be telling them their name. My ISP uses DHCP and tells my router its name is "CPE-" followed by the MAC address followed by another string, followed by the domain. You can do this with entries like ddns-hostname = concat(binary-to-ascii(10, 8, "-", leased-address), ".hh3"); ddns-domainname = ".site"; All this is in the DHCP/DNS documentation and the on-line articles have referred to in past email. -- Error of opinion may be tolerated where reason is left free to combat it. --Thomas Jefferson, First Inaugural Speech (1801) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org