Problem Joining Windows Server 2008 Domain

[triton]

Hi @all,
I have a problem after upgrading my Windows domain to Windows Server 2008 RC0. My NAS can't Join the domain any more.
Is there a known issue with the new directory service?

Maybe there are a few new Kerberos or Signing Policies?

Thanks
Sigi

[pain2k]

Hi triton,

I have exactly the same Problem. After Upgrade to 2008 my NAS can't join the Domain any more.
I have the latest beta firmware installed.

Can someone plz fix the Signing Policies in the next beta firmware?

THX

pain2k

[CondoMax]

Subsequent to upgrading a DC to W2K8 I've tried everything I can think of to join the ReadyNAS NV+ 4.0c1-p2 to an AD domain that previously was successfully joined in W2k3 R2. I am simply not able to join the domain. You'll be getting an explosion of complaints similar to this one when W2K8 hits the streets in large numbers this spring, so it would be advisable to heat this issue up and get a fix out in due course. Obviously, this problem affects a segment of your user community that you want to keep happy.

[lancer]

Subsequent to upgrading a DC to W2K8 I've tried everything I can think of to join the ReadyNAS NV+ 4.0c1-p2 to an AD domain that previously was successfully joined in W2k3 R2. I am simply not able to join the domain. You'll be getting an explosion of complaints similar to this one when W2K8 hits the streets in large numbers this spring, so it would be advisable to heat this issue up and get a fix out in due course. Obviously, this problem affects a segment of your user community that you want to keep happy.

ReadyNAS uses Samba. Samba currently has no support for W2K8. Two versions that do are still in the test phase. My guess is you have to wait for couple Radiator releases.

If MS had published (for everyone to see) the modifications they made early in their development process, this problem wouldn't exist.

[CondoMax]

Assuming that this will be a protracted morass, then, can anybody foresee a decent and timely workaround for the W2K8 AD fiasco?

The ReadyNAS is such a nice, compact NAS device. I'd hate to have to replace it with something else, but if it can't join an AD domain, it is worthless to me.

[matchews]

Same problem here. Our enterprise is about to update to server 2008. If the 2008 compliant firmware isn't released soon, our Ready Nas devices will become paper weights. It looks like Samba has incorporated it...


http://us4.samba.org/samba/history/samba-3.0.28a.html

Samba 3.0.28a Available for Download

===============================
Release Notes for Samba 3.0.28a
Mar 8, 2008
===============================

This is the second production release of the Samba 3.0.28 code
base and is the version that servers should be run for for all
current bug fixes.

Major bug fixes included in Samba 3.0.28a are:

o Failure to join Windows 2008 domains
o Windows Vista (including SP1 RC) interop issues

[bluenullity]

Just bumping this up to see if this is getting on a patch list anytime soon. I would like to be able to use my ReadyNAS NV+ with Windows Server 2008 soon and to be able to fix that Vista SP1 domain authentication problem as well.

[eklass]

bluenullity, check out this post:

viewtopic.php?f=18&t=17112&p=93551#p93551

chirpa says that the fix is in beta currently

[cjohnsonuk]

We've added one Windows 2k8 server to our 2k3 domain about 2 weeks ago. LAst friday users started experiencing a problem whereby they couldn't connect to the box as it was prompting them for a password. I checked the User and Group accounts page and the users were in the list. I confirmed a few settings on the "security mode" page and when confirming them again no errors are displayed but when viewing the "User and group accounts" page I get no users showing.

Checking the logs I get :

Mon Apr 21 08:53:06 WEST 2008 Unsuccessful joining domain KES7.NET
Mon Apr 21 08:53:05 WEST 2008 WARNING! Unsuccessful synchronizing clock with ADS server. Please note that this can cause problems with user authentication by ADS. This is not fatal, but you should ensure that your NAS system clock and the ADS server clock are set to the same time.
Fri Apr 18 16:28:01 WEST 2008 System is up.
Fri Apr 18 16:27:23 WEST 2008 Your NAS device has been updated with a new firmware image. (RAIDiator 4.01c1-p1)

However checking the time at the bottom of the page for the time and checking the time on all our servers (and the time zone) reveals that they are all set correctly and are set to the same time.

I'm not sure if this is the 2k8 issue or just a time/timezone issue. Any ideas?

[cjohnsonuk]

I removed the nas box from the ad and resubmitted the and details and then
I changed dhcp settings to point the dhcp provided time server to a Win 2k3 dc instead of our Linux DHCP server, rebooted and its showing me lists of users again!

Added ad users to the write enabled users in Share listings and it works fine again!

Hope this helps some of you out there.

logs:
[after changes of sntp server]
Mon Apr 21 10:54:24 WEST 2008 Successfully joined domain KES7
Mon Apr 21 10:54:21 WEST 2008 WARNING! Unsuccessful synchronizing clock with ADS server. Please note that this can cause problems with user authentication by ADS. This is not fatal, but you should ensure that your NAS system clock and the ADS server clock are set to the same time.

[before]
Mon Apr 21 08:53:06 WEST 2008 Unsuccessful joining domain KES7.NET

[Skywalker]

I'm not sure if this is the 2k8 issue or just a time/timezone issue. Any ideas?

The time sync error won't cause a domain joining failure. If you need Win2K8, you can update to the latest beta firmware release at viewtopic.php?f=17&t=17387 .