| View previous topic :: View next topic |
| Author |
Message |
CTSSteve
Member
Joined: 25 Oct 2007
Posts: 3
|
 Posted: Thu, Oct 25 2007, 9:23am Post subject: 150d Clock scew error |
 |
|
I have been trying to join a 150d to a 2000 domain and keep getting a clock scew error. I have tried setting the clock back an hour (like I read in a previous post) still didn't work.
I have also tried, 1/2 hour forward and backward, changing time zones, then back again. I'm now going to take it over to another clients place to see if I can join there domain.
anything? |
|
| Back to top |
|
 |
TESBA88
Forum Guru
Joined: 09 Sep 2007
Posts: 658
|
| Posted: Thu, Oct 25 2007, 1:17pm Post subject: |
|
|
| Check NTP settings. Also, if NTP IS CORRECT try this ( but don't ask why!!) set time zone to GMT, reset your time, then power cycle. Set zone and time back to what you need it to be. Try again. Also how about trying the latest firmware? |
|
| Back to top |
|
|
CTSSteve
Member
Joined: 25 Oct 2007
Posts: 3
|
| Posted: Fri, Oct 26 2007, 6:25am Post subject: |
|
|
| already tried all that, still nothing. firmware is 69.69 the latest out. |
|
| Back to top |
|
|
CTSSteve
Member
Joined: 25 Oct 2007
Posts: 3
|
| Posted: Wed, Oct 31 2007, 10:18am Post subject: |
|
|
took it to 2 different customers with windows 2000 servers, and kept getting the same error at both places. Also took it to another customers with server 2003, joined that Domain no problem.
Is it possible this doesn't work with a 2000 domain? |
|
| Back to top |
|
|
TESBA88
Forum Guru
Joined: 09 Sep 2007
Posts: 658
|
|
| Back to top |
|
|
MacGeek
Forum Guru
Joined: 01 May 2006
Posts: 2749
|
| Posted: Wed, Oct 31 2007, 1:51pm Post subject: |
|
|
Since it is Server 2K, try joining as an NT 4.0 Domain Member. The only time you will get a clock skew error is when Kerberos has issues. NT 4.0 doesn't use Kerberos, so you should be good.
MG |
|
| Back to top |
|
|
|
Forum FAQs
Search Posts
Member Directory
Usergroups
Create a Username
Edit My Profile
Log in
