![]() | ||
|
|
Snap Server / NAS / Storage Technical Goodies The Home for Snap Server Hacking, Storage and NAS info. And NAS / Snap Classifides |
![]() |
Thread Tools |
![]() |
#1 |
Cooling Neophyte
Join Date: Aug 2006
Location: Plano, Texas
Posts: 13
|
![]()
Hello all. I have been in and out of these forums for some time and consider this place to be the 'Snap Server Authority' so I am hoping someone can help me out with this since I know I can't be alone.
I have a Snap 2000 with the following specs: OS: 3.4.807 Hardware: 2.0.0 BIOS: 2.0.282 Upgraded to 2x300GB Seagate and 128MB RAM I just installed Vista Ultimate on Wednesday and I am unable to browse the Snap or map a network drive to the Snap from within Vista. All other XP machines work fine (and have for years), but Vista will not connect regardless of username or password. My windows user/pass is the same as the Snap and should authenticate me with those credentials but it will not. I get a login window every time I try to access the Snap thru the network. I have tried every variation of username I can think of ("user", "machine/user", "domain/user") with no luck. I have only found a few references to others having this problem, but no one seems to have figured out how to fix it or get around it. Adaptec does not claim Vista support for the Snap 2000: http://adaptec-tic.adaptec.com/cgi-b...i=&p_topview=1 I know there has to be a way to get this to work without stripping away all of the security on the Snap, which is what someone reported actually did work. I simply can not open the device up that way so I am looking for a way to authenticate. I have even tried setting up a DFS in Win2003 but that did not work either since the authentication passes thru to the Snap. Help or suggestions appreciated. Thanks! |
![]() |
![]() |
![]() |
#2 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
![]()
Well, it must be nice being a beta test for MS
![]() ![]() I would expect to see a lot of this. I haven't a clue unless it's a FW thing. A work around maybe to see if you can access it going through another pc, using it as a relay. But you wold have to setup a pc for every one to go through. Good luck,
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
![]() |
![]() |
![]() |
#3 | |
Cooling Savant
Join Date: Aug 2004
Location: UK
Posts: 909
|
![]() Quote:
Or at least, has been over here Could you try creating a share with no authentisication, just to check if vista can actually communicate with the device properly It could be a problem with OS v3...
__________________
Snap Server Help Wiki - http://wiki.procooling.com/index.php/Snap_Server Snap Server 2200 v3.4.807 2x 250GB Seagate Barracuda 7200.9 w/ UNIDFC601512M Replacement Fan "Did you really think it would be that easy??" Other NAS's 1x NSLU2 w/ 512mb Corsair Flash Voyager Running Unslung 6.8b 1x NSLU2 w/ 8Gb LaCie Carte Orange Running Debian/NSLU2 Stable 4.0r0 250GB LaCie Ethernet Disk Running Windows XP Embedded |
|
![]() |
![]() |
![]() |
#4 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
![]()
I know, now their using public beta tester, and charging them to do it.
![]()
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
![]() |
![]() |
![]() |
#5 |
Cooling Neophyte
Join Date: Feb 2007
Location: California
Posts: 21
|
![]()
I am having the exact same problems and it is affecting w2k3 servers as well.
|
![]() |
![]() |
![]() |
#6 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
![]()
AD2003 requires v4.0.860, and there is a patch to the kernel in the FAQ's below the 4100's.
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
![]() |
![]() |
![]() |
#7 | |
Cooling Neophyte
Join Date: Feb 2007
Location: California
Posts: 21
|
![]() Quote:
|
|
![]() |
![]() |
![]() |
#8 |
Cooling Neophyte
Join Date: Aug 2006
Location: Minnesota
Posts: 52
|
![]()
Oh, they distrubute it stil, you just have to pony up some cash
BTW It's not just you Adaptec frustrates, it's everyone who has to deal with them. One of the reasons I no longer use their scsi cards. |
![]() |
![]() |
![]() |
#9 |
Cooling Neophyte
Join Date: Feb 2007
Location: California
Posts: 21
|
![]()
Will the guardian OS run on a 2000
|
![]() |
![]() |
![]() |
#10 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
![]()
No
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
![]() |
![]() |
![]() |
#11 | |
Cooling Neophyte
Join Date: Aug 2006
Location: Plano, Texas
Posts: 13
|
![]() Quote:
I am not running AD, and I understand that I need v4.0 of the OS to do that. This is just straight-forward "workgroup" style sharing that has always worked well with the Snap in the past. I know there has to be a way around this, I am just not sure at this point what that is. Any help? |
|
![]() |
![]() |
![]() |
#12 |
Cooling Neophyte
Join Date: Aug 2006
Location: Plano, Texas
Posts: 13
|
![]()
Oh, and yes, I realize that I am a "public beta tester" for MS, but hey, I'm a glutton for punishment.... So far Vista has behaved for the most part, but I'm not real happy about not having my Snap!
![]() |
![]() |
![]() |
![]() |
#13 |
Cooling Neophyte
Join Date: Feb 2007
Location: California
Posts: 21
|
![]()
I got mine working fine by upgrading to 4.0.860, which after spending some time with Adaptec support, admitted that most vista users will need to upgrade to 4 because of how Vista enforces authentication on file shares.
|
![]() |
![]() |
![]() |
#14 |
Cooling Neophyte
Join Date: Aug 2006
Location: Plano, Texas
Posts: 13
|
![]()
jrmccracken thanks - I am going to try that. I have the 4.0.860 OS already, just have never loaded it due to issues I had read about. I guess I will have no choice but to try that and see if it works for me. Thanks.
|
![]() |
![]() |
![]() |
#15 |
Cooling Neophyte
Join Date: Nov 2006
Location: canada
Posts: 21
|
![]()
Jim, can you elaborate on what was involved on the windows side of things after you upgrade to 860? was it the usual plug and connect after that, or are there windows authentication changes that still need to be made.
|
![]() |
![]() |
![]() |
#16 |
Cooling Neophyte
Join Date: Aug 2006
Location: Plano, Texas
Posts: 13
|
![]()
jrmccracken can you verify what snap you have? I have the 4.0.860 OS, but when I try to upgrade I am told that I do not have a supporting hardware platform. My Snap is as follows:
Snap Server 2000 Software 3.4.807 Hardware 2.0.0 BIOS 2.0.282 I thought I remembered that the 2000 would support the 4.0.860 software, but maybe I am wrong. Thanks. |
![]() |
![]() |
![]() |
#17 |
Cooling Neophyte
Join Date: Feb 2007
Location: California
Posts: 21
|
![]()
Actually It sounds like you don't have a supported software platform, please realize I don't consider myself an expert on SNAP, but my experience with Active Directory tells me that Vista is enforcing NTLM V2 instead allowing LM and NTLM V1.0. It sounds like from what I have experienced in the last 2 days is that you are using the 4.0.860 upgrade instead of the full install which Adaptec, left me singing like a soprano to get access to. I was able once I installed 4.0.860 full to configure Active Directory, and Viola Vista connected right up. On a side note, prior to Active Directory replicating permissions to the SNAP I was able to open the shares by using the internal accounts.
Snap Server 2000 Software 4.0.860 Hardware 2.0.0 BIOS 2.0.282 The odd thing about this all is that ADAPTEC STILL swears up and down that my Snap was a Dell 705N which is a 4000, instead of a 701N which is the 2000, which is what my SNAP is. |
![]() |
![]() |
![]() |
#18 | |
Cooling Neophyte
Join Date: Aug 2006
Location: Plano, Texas
Posts: 13
|
![]()
Yes, you are right - the 4.0.860 I have is the upgrade. Guess I will need to get the full version from Adaptec. They claim you can install 4.0.830 first and then use the .860 upgrade I have, but my .830 file is corrupted, and I can't find a replacement. Did they charge you to get the full version of .860?
Also, when you say: Quote:
|
|
![]() |
![]() |
![]() |
#19 |
Cooling Neophyte
Join Date: Feb 2007
Location: California
Posts: 21
|
![]()
Yes I used the Administrator account, but in 3.xx there is no support for NTLM V2 so it will not negotiate the connection. And yes they hit me for 200.00 for access to the files.
|
![]() |
![]() |
![]() |
#20 | |
Thermophile
Join Date: May 2006
Location: Yakima, WA
Posts: 1,282
|
![]() Quote:
The Dell 701N is a SNAP 2000 and the Dell 705N is a SNAP 4100. To my knowledge, there is no Dell version of the SNAP 4000. Just an FYI. |
|
![]() |
![]() |
![]() |
#21 |
Cooling Neophyte
Join Date: Nov 2006
Location: Germany
Posts: 15
|
![]()
Hi evoaz1,
I had the same problems with Vista and my snap servers (2000 and 2200). You can try the following: - select "start" -> "run" - type "secpol.msc" to open your local security policy - then got to "local policies" -> "security options" and set the "Network Security: LAN Manager" from "Send NTLMv2 response only" to "Send LM & NTLM -- use NTLMv2 session security if negotiated." Now it should work. After that I was able to see the snap and also the network shares. Then I've connected each share as a network drive and was able to browse the shares. I've selected "connection with different username" and inserted the username and password for the snapserver share, when I've connected the shares as a network drive. BUT: If I want to remove some non-empty folders at the shares, I get an error, access denied. If I remove the files into the folders at first and then remove the empty folder, there is no problem. Is there a security policy for deleting non-empty folders in vista on network-drives? I hope, I can also solve this problem or can somebody help? Regards Tino |
![]() |
![]() |
![]() |
#22 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
![]()
holzinet, that is good info, I will add it into the FAQ's.
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
![]() |
![]() |
![]() |
#23 |
Cooling Neophyte
Join Date: Nov 2006
Location: Germany
Posts: 15
|
![]()
by the way: this sollution is only for Vista Business, Enterprise, and Ultimate.
If somebody is using Vista Home Basic and Home Premium he has to change the following registry-key: look for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Lsa and change the value of "LmCompatibilityLevel" from "3" to "1" ... But I don't know, how to solve the problem with deleting non-empty folders. I think, it is a problem with the samba version on the snapos (I'm using 4.0.860). On my local fileserver I have no problems like this with Vista (running samba 3.0). |
![]() |
![]() |
![]() |
#24 |
Cooling Neophyte
Join Date: Aug 2006
Location: Plano, Texas
Posts: 13
|
![]()
holzinet! that was exactly what I needed. THAT DID THE TRICK! What I would like to have confirmed though is that updating the security policy in Vista to use LM and NTLM instead of just NTLMv2 on the 3.4.xxx OS would have worked instead of upgrading to 4.0.860. Oddly enough, until I made that policy change I was STILL unable to browse the shares on the Snap even with the .860 OS.
I can CONFIRM that there is a 4.0.860 FULL INSTALL that Adaptec can issue that can upgrade the Snap directly from 3.4.xxx to 4.0.860. Based on this experience I would assume that it is possible to have Vista and the Snap authenticate properly once the security policy is updated regardless of the OS, but I would like for someone to confirm this. Thanks to all for getting this figured out. I can now go off and try to tackle another Vista compatibility issue... but that is for another forum.
__________________
Snap Server 2000 Software: 4.0.860 Hardware: 2.0.0 BIOS: 2.0.282 2x300GB Seagate 128MB SDRAM |
![]() |
![]() |
![]() |
#25 |
Cooling Neophyte
Join Date: Nov 2006
Location: Germany
Posts: 15
|
![]()
Hi evoraz1,
I'm running 4.0.860 too on my 2200 and I can access the shares without problems when I was updating the security policy in Vista. I can copy files, folders and can also delete files but can only remove empty folders. At the webinterface I can see the right username from vista connection like from XP, so I could not understand, where the difference of the connections is. Before changing the security policy there was no real username at the webinterface (you can see at "active users"), caused of the wrong authentication mechanism. So now everything should be the same like connecting from xp!? But for me the problem to solve is still the possibility to remove non-empty folders on the share. If I connect from Vista to another client running xp or to a linux client with samba 3.0 I've no problems to handle. Connecting from xp to the snap server works also perfect. So there must be another difference with the connection between XP and Vista. I've tried to find a sollution the hole day, but no success, I think at the end it is a problem with the samba version in 4.0.860. |
![]() |
![]() |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|