I've been using EON successfully (mostly) for several months now. Occasionally, I notice my shares are not accessible from my windows boxes. I typically see some smb error in the /var/adm/messages that is not too specific. The typical fix is to rejoin the domain using smbadm join.
Today, I've been fighting to get this working again all day. I finally got it, but I don't expect it to last long. It started with one of my nfs shares not being accessible from my VMWare host. Because my DCs run on VMware, EON couldn't contact my PDC, and I couldn't browse my shares from my windows boxes. After getting the nfs share back online and my DCs powered back up, there were different errors in the messages file. I started getting clock skew too great errors from ntp. I configured the ntp.conf to look to my DCs for time. I googled how to restart the ntp service, but nothing worked with EON. I compared the clock on my DC to the clock on EON and it was maybe a minute or two off. After running ntpdate -u <PDC>, the times synced up and I stopped getting that error. Ended up having more problems and had to populate the krb5.conf file (not sure how this was working before with just defaults), and when I was done, I got another clock skew too great. ntpdate -u fixed it and I could successfully join the domain and browse shares. How can I fix this permenantly? -- This message posted from opensolaris.org _______________________________________________ distribution-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/distribution-discuss
