Problem with Windows 7 and Snap Server 1100
 

Problem: "Create New Folder" crashes which ever program I am using, and in the background it is stuck in an infinite loop of creating folders until I "End Task".

Up to this point, my network consisted of only Windows XP machines. I have recently added the first Windows 7 machine, and to my surprise... it doesn't play nicely with the Snap Server that I have. :rolleyes:

I have Windows 7 Home Premium, and a Snap Server 1100. The Snap Server is running Software 3.4.803 (US) on Hardware 2.0.2 with BIOS 3.4.758.

At first, I was having a problem authenticating with the Snap Server. The user was showing as a bunch of random characters (see below). I had hoped that this was the cause of the original problem. :cool:

Attachment 5912

Thanks to this thread, I changed the NTLMv2 settings. After doing this, the server authenticated and the user name was being shown correctly. However, this did not fix the original problem. :(

I found a thread describing a work around for this. Namely, creating a folder on the desktop and copying it to the server. I was wondering if anyone else has any other thoughts or suggestions on fixing this problem?

Re: Problem with Windows 7 and Snap Server 1100
 

SnapOS is not compatable with anything after XP. And there is No Support for it any more, EOL.. Now v4.0.860 may work a little better if at all.

Re: Problem with Windows 7 and Snap Server 1100
 

.

Re: Problem with Windows 7 and Snap Server 1100
 

I appreciate the replies! It looks like I may be out of luck then. :(

Re: Problem with Windows 7 and Snap Server 1100
 

.

Re: Problem with Windows 7 and Snap Server 1100
 

Thanks again for the attempt. It had my hopes up, but the result was still the same: the creation of an infinite loop of folders still locking up Explorer. :(

I did restart after executing both commands, and I ran the command window as Administrator. For what it's worth, here is the message that was given after each command was executed.

It looks like I will be replaceing a perfectly working server now. Thanks to the ever "improving" versions of Windows. :rolleyes:

Re: Problem with Windows 7 and Snap Server 1100
 

.

Re: Problem with Windows 7 and Snap Server 1100
 

I have my Snap Server 2200 with Snap OS 4.0.860 and 2 Seagate SATA HD each 1.000 GB (with IDE/SATA Converter) in Raid 1 running and I use it without any problem with Windows 7 Ultimate 32bit (German) and Windows 7 Home 64bit (German too).

It should be work with Snap Server 1100 and by example 2TB drives too.

To access the Snap OS hardware you should have the same Workgroup in the LAN and the windows 7 user should be registert in the Snap Server. Alternative use the unlocked Guest account.
If not many users have access at the same time, the on board RAM of the Snap Servers 1100/2200 should be enough.

Re: Problem with Windows 7 and Snap Server 1100
 

schnappi, that's great information. Keep us abreast if any of your information changes. It would be greatly appreciated.

Where did you get this "Snap OS 4.0.860 SP3"? The "SP3" is throwing me off.
Can you tell us which converter adapter you are using and chipset if you know?


thanks,
bitor

Re: Problem with Windows 7 and Snap Server 1100
 

Sorry, sorry, sorry. NO SP3! I muddled it with the SP of the Guardian OS.
Its plain Snap OS 4.0.860.

But here is the info for the Converter. You get them anywhere.

I tell you some of the current ebay auctions:
Item number: 180504071375, or 270585555149 or 370282677369 or ...

They would work well in Guardian Snap Servers 4200/4400/4500 .., but
the 2 electrolytic capacitors are to big to fit everything into the drive caddy.

Next week, if I have little time, I try to solder them out and mount them on a place were they do not to hamper.

Greetings from Germany
And sorry about my simple school english

Re: Problem with Windows 7 and Snap Server 1100
 

schnappi, no problem about the "SP3" I understand.

This adapter most likely because of the larger/longer capacitors and according to my research is a JM20330 chipset made by http://www.jmicron.com/Product_JM20330.htm

Linux Compatibility:
http://en.wikipedia.org/wiki/JMicron

There are low profile capacitors that you can buy and replace them if you like. If you did not know this already.

A good information link about capacitors is here. I incurage you to view it before replacing them.
http://www.afrotechmods.com/groovy/c...eplacement.htm

Here is one with the JM20330 chipset without the big capacitors, but I have not tested this one yet.
http://cgi.ebay.com/Serial-ATA-SATA-...-/200475947656



Thank you for your input. Please keep us up to date on your progress and if possible supply pictures.


bitor

Re: Problem with Windows 7 and Snap Server 1100
 

Originaly, this was a Windows 7 topic.
Shall we open an extra SnapOS SATA subject?

To the windows 7 problem:
@WhiteWormGreen

Do you have installed both: TCP/IPv6 and TCP/IPv4 protocol?

Re: Problem with Windows 7 and Snap Server 1100
 

schnappi, you may if you like, but it doesn't matter to me.... "topics" evolve in to other subjects and that's ok by me.




No, not yet.

Re: Problem with Windows 7 and Snap Server 1100
 

.

Re: Problem with Windows 7 and Snap Server 1100
 

I agree, you should try NFS. However, be aware that only 2 versions of windows7 have nfs support and it is not enabled by default. Enterprise Edition (only available via bulk license) and Win7 Ultimate. Let us know if that works for you.
Also as a side note: NFS is also available in Vista ( ....yes I said the name that should not be spoken LOL) but also only in enterprise and ultimate.

Re: Problem with Windows 7 and Snap Server 1100
 

I noticed the same thing with my Snap Server 1000 and Windows 7 (and with Vista).
I fixed it by disabling:
- Enable Opportunistic Locking
- Enable NT SMBs
These are under: Network Settings -> Microsoft Networking -> Advanced of the Snap Server's configuration web page.

Re: Problem with Windows 7 and Snap Server 1100
 

Thanks GoRadar! I had the same problem and your solution worked perfectly.

Re: Problem with Windows 7 and Snap Server 1100
 

It has been well over five months since GoRadar posted the solution and probably won't ever see it anyways. I dislike bumping old threads like this, but it seems to have fixed the problem.

Much Thanks!