LinuxQuestions.org - joining a windows 2003 domain with suse10.2

- Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)

- - joining a windows 2003 domain with suse10.2 (https://www.linuxquestions.org/questions/linux-server-73/joining-a-windows-2003-domain-with-suse10-2-a-552368/)

joining a windows 2003 domain with suse10.2

hi,

I'm trying to connect a suse10.2 desktop to the windows server 2003 domain at work, i tried fooling around a bit in yast and configured the ntp server, then tried to add my domain samba using yast. when it prompts me to join the domain, after i have typed in my un/pw it returns the error

Code:

 libads/kerberos.c:ads_kinit_password(210) kerberso_kinit_password username@domain.local failed: Clock skew too great

utils/net_ads.c:ads_startup_int(285)

ads_connect: Clock skew too great

there shouldn't be any problem with the speed 'cause i have the same ntp server as the AD, though for some reason the computers clock doesnt keep the same time as the other windoze workstations in my office, though it's only off by 30 seconds or so..

connecting to the internet and such was easy, and it is definitly working for everything else, but this is the first time i have ever used linux in a netoworking environment, and i have no clue what is really going on, so any advice would be appreciated,

also i'm sorry i have the feeling i havent provided enough information... but any pointers would be greatly appreciated

your DC will prbably be providing an NTP time source, so just sync to it... stop ntpd and then just run "ntpdate ip.of.yr.dc" and then try again. no point syncing one box against global ntp server if the rest aren't...

also this is not a networking question. more to Linux - Server.

sorry about that, didn't mean to post in the wrong place.

I did what you said, but the clock didnt appear to change, and also it's still throwing up the same error message when i try to join the domain...

thanks again,
shadow

you didn't run the command right then... if it's not providing ntp, then just sync both sides of the equation to a common source.