|
|
Snap Server / NAS / Storage Technical Goodies The Home for Snap Server Hacking, Storage and NAS info. And NAS / Snap Classifides |
Thread Tools |
12-04-2007, 09:01 PM | #1 |
Cooling Neophyte
Join Date: Dec 2007
Location: SF Bay
Posts: 2
|
XP and snap1000
Thanks to the info on this site I was able to upgrade a old snap 1000 (3.4.804) to a 130 Gig in a snap.
It was kind of fun to do it, too. But I'm confused as to how I should be able to connect the server as a network share. Is the MS SMB patch issue preventing me from seeing the server in my workgroup, or am I doing something wrong? It seems like I should be able to map a FTP 'network place' as a drive as well, but that doesn't work. I've been able to map a drive using MS client for NFS, but that seems to have issues with reading data straight off the drive, as well. Any helpful suggestions? thank |
12-05-2007, 05:49 AM | #2 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
Re: XP and snap1000
Without the v4 OS your best bet would be ftp access, even though it should work with smb. Did you restart the snap after you made changes? The older OS seem to need this for certain function worked. Make sure you ID on your PC matchs the snap. So when you login in to MW Windows screen it makes the connection to the snap and every thing should work.
V3 had issues with XP an MS AD support. I don't recall all of the issues. The snap uses v2 SAMBA so it has to do all of the conversion. Running it as FTP will speed it up a tad.
__________________
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 |
12-05-2007, 08:28 PM | #3 |
Cooling Neophyte
Join Date: Dec 2007
Location: SF Bay
Posts: 2
|
Re: XP and snap1000
I appreciate the time you spent answering my question.
I was confused about whether SMB should work or not. I'd remembered the user name matching, but it turns out my problem was even more bone-headed than that. 'Client for MS Networks' was in the list of available clients, but I failed to notice that it was un-checked Thanks again |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|