Snap OS3x workaround for Server 2003 Active Directory

[Fitz]

I've seen a few people with the same problem - this is my way of saying 'screw you' to Adaptec.

I have a snap 4100 that no longer works in my Server 2003 Active Directory - I contacted Adaptec support and was told they actually expect me to PAY for a maintenance contract I will never use to fix their OS problem. I refuse to pay for updates like this and if everyone refuses then we may see a change in attitude from vendors.

There is however a workaround for this problem if you have a Linux (or other UNIX) box running SAMBA3 with Winbind.

Join the *NIX machine to your Active Directory (see WinBind docs)

Turn on NFS sharing in the Snap Server.

Edit the root$ share and add an NFS entry for UID 0 from the IP of your *NIX machine.

Make a directory on the *NIX machine for a NFS mount -
e.g. mkdir /mnt/snap

As root, mount the root$ share of the snap using NFS from the *NIX machine

e.g. # mount -t nfs ip.of.snap.server:/root$ /mnt/snap

Edit your /etc/samba/smb.conf to share the mounted folder to Active Directory users.

This should get you up and running. Hope someone finds this useful.

[re3dyb0y]

Yes, very useful

Will add to the wiki!

Thankyou!

[jontz]

As Mr. Burns would say, eeeexcelent! Great work Fitz!!!

[re3dyb0y]

So this is basically using the SAMBA for the AD authentiscation and then just linking to the shares on the snap??

[jontz]

That sounds like it...nothing fancy, but a clever little work-around.

[Davesworld]

Adaptec must think that this os from the Cretaceous period is something worth throwing money hand over fist about. Not with an outdated promise driver on an old bsd kernel it isn't.

[Davesworld]

You know, I wound up turning windows networking off completely even as I am using SnapOS 4 which does support active directory. I installed Windows services for Unix and went NFS on Windows and mapped the user and groups to be consistent. Too bad SnapOS can't do nfs over tcp. UDP? How old of a BSD kernel IS this, Adaptec? C'mon!

[re3dyb0y]

Lol

I'd be interesting to see the difference in these units with that of the new guardian os

Adaptect - If your reading, we will gladly have a unit (even with small drives :P) to play with and compare

[JoeShmo]

Well, seeing as the 4.0.860 does NOT work with w2k3 Active directory without some registry tweaking on the domain controllers and clients, we might just have to use this work around as well, but that means we dont get the nice snazzy web-gui to configure permissions, and the sharing is done on another machine, which will probably slow down performance.
We have a 12000.. has anyone come up with an "alternative os" on these things? It would be nice just to run Linux or FreeBSD on it and have it do the WinBind and samba stuff natively. Its kind of depressing seeing our 12000 sitting there collecting dust, and just acting as a stand-alone NAS.

[re3dyb0y]

It should do/Does, no one else has had problems


The 12000 is guardian

[JoeShmo]

Well, Upon connecting, I don't have access to even see any files/directories in the share. Trying to make/change directories, I get a "Network Access is Denied" message. I have given my domain account "Full Access" to the share. Outlined in Answer ID 12785 in adaptec, it describes my exact problem, and the workaround of whacking at the registry. This solutions DOES work, but I would not like to modify the registry on over 1000 client machines, plus the domain controllers just for a NAS box. Doing so may jeopardize what little security exists in Windows..

So possibly there is only something wrong in our setup (and the setup of all those people who answer id 12785 was created for). Yet if there is another solution to the same problem, I'd think it would be on the Knowledge Base on adaptec's site. So far, I've been unable to find it.

[re3dyb0y]

Well, if your in a windows AD, you could just get the computer to run the reg script on boot up using global policies

[strappingbuck]

No need for special registry scripts, these settings map to existing GPO options:

Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options

Microsoft network client: digitally sign communications (always)
Microsoft network client: digitally sign communications (if server agrees)
Microsoft network server: digitally sign communications (always)
Microsoft network server: digitally sign communications (if client agress)

Network security: LAN Manager authentication level

I just set these to see if it will help with my problem:

http://forums.procooling.com/vbb/showthread.php?t=13134