Re: can't log in on workstation

On 16 August 2013 14:46, Petter Reinholdtsen <pere@hungry.com> wrote:
To me, the log seem to indicate a broken DNS server, not returning
anything for 'host tjener.intern'. Is that correct?

It looks like it, but when I log in as root, ws01 can ping tjener, and also out onto the internet, by name

Aug 15 17:04:28 tjener dhcpd: LDAP-HOST line 2: semicolon expected.
Aug 15 17:04:28 tjener dhcpd: option host-name ws01.
Aug 15 17:04:28 tjener dhcpd: ^

It seem to indicate a typo in the dhcp setup related to the ws01 DNS
name. How did you add ws01 to DNS? Is its name invalid somehow?

Do you think its the .intern extension? I followed the example in the manual, adding ws01.intern to the name field. I didn't add any DNS record, just checked the box. Are we supposed to add a record? The manual just says "activate dhcp and dns" and shows the box has been checked. Then I ran ldap2bind.

After failing to delete this machine from gosa (it came back as a 'component')

I tried another computer, and called it ws02 (no extension). Now there is no naming error, but I still get this:

Aug 16 16:02:19 tjener ldap2bind: Reloading the zone 'subnet01.intern.' was successful\n
Aug 16 16:02:36 tjener dhcpd: DHCPRELEASE of 10.0.16.23 from 00:90:f5:34:02:0d via eth0 (found)
Aug 16 16:03:15 tjener dhcpd: DHCPDISCOVER from 00:90:f5:34:02:0d via eth0
Aug 16 16:03:15 tjener dhcpd: DHCPOFFER on 10.0.3.2 to 00:90:f5:34:02:0d via eth0
Aug 16 16:03:15 tjener dhcpd: DHCPREQUEST for 10.0.3.2 (10.0.2.2) from 00:90:f5:34:02:0d via eth0
Aug 16 16:03:15 tjener dhcpd: DHCPACK on 10.0.3.2 to 00:90:f5:34:02:0d via eth0
Aug 16 16:03:35 ws02 fetch-ldap-cert: Failed to fetch LDAP SSL certificate from dnsdomainname: Name or service not known tjener.intern.

Am I doing the gosa thing right?

thanks

nigel