Snap Server 4100 and Windows Vista

If you are looking to upgrade to Windows Vista and also have a Snap Server 4100 (or 1100), then there are certain incompatibilities that you should be aware of. First, domain authentication does not work correctly with the SNAP and Vista. Also, you will not be able to access the SNAP Server using local accounts with the Windows Vista default settings. Luckily, with help of the folks over at WinVistaForums, a workaround has been found that will allow you to map drives using built-in SNAP accounts. Here are the steps:

1. First, check to see if your security policies are set on the domain level if running your machines on a domain. If you are, your will want to set the security policy on the domain controller instead of the local machines.
2. On the Vista Machine (or Domain Controller), select Administrative Tools->Local Security Policy.
3. Select Local Policies->Security Options->Network security: LAN Manager authentication level.
4. Use the setting “Send LM & NTLM – use NTLM v.2 if negotiated”
5. Next, you will have to map a drive under the Computer window.
6. Under the Map Drive dialog box, select a share using this syntax: \\SNAP_SERVER NAME\SHARE_NAME
7. Select the option to enter a user name, and enter the credentials for a local account on the SNAP. Be sure to use the syntax: SNAP_SERVER_NAME\USER_NAME for the username. If you try to only enter a username or a domain account, this will not work.
8. You should now have full access to your share from Windows Vista.

If the steps don’t work for you, make sure that you are setting the Security Policy from the correct machine, and also that the permissions permit the local user to access the share on the SNAP server. Also, don’t try contacting Adaptec for help regarding Vista on the 4100. Their official response was that they did not plan on releasing a fix for Vista and they weren’t aware of any workarounds.

For more information and a discussion on this issue, check out this thread on WinVistaForums. Much of the information used here was obtained from that disucussion.