Pro/Forums - View Single Post - Snap 4200 GOS 5 Windows Server 2008 AD issues

Max8 · 03-19-2009, 03:33 PM

I know nothing about AD but I have been told that a snap or any decent NAS is a great tool for testing that you have AD set up correctly...

Example;
I did an eval from a guy who could not get a loan snap onto his AD.... I got my techs involved.
He swore blind that his AD was setup correctly.

I took the unit back and we upgraded it from 5.0.133 to 5.1.041 as I had just received it & just to make sure we attached it to our AD and it worked no problem on our network.

I took it back to the potential customer and 3 days later no dice, it still would not work... 1 week after that, I chased up the reseller and I learn that it is going well... I don't know what happened and I don't want to embarrass the guy but I would imagine that there was something amiss that he had not seen before... all it takes is one small error or setting for your AD I guess...

I am quite certain that the AD issues are sorted in Gos 5.0.133 & 5.1.041 so try to go over your AD settings again just so you can rule that same issue (that my mate above had) completely out of the equation...

03-19-2009, 03:33 PM	#8
Max8 Cooling Neophyte Join Date: Mar 2009 Location: Sydney Australia Posts: 83	Re: Snap 4200 GOS 5 Windows Server 2008 AD issues I know nothing about AD but I have been told that a snap or any decent NAS is a great tool for testing that you have AD set up correctly... Example; I did an eval from a guy who could not get a loan snap onto his AD.... I got my techs involved. He swore blind that his AD was setup correctly. I took the unit back and we upgraded it from 5.0.133 to 5.1.041 as I had just received it & just to make sure we attached it to our AD and it worked no problem on our network. I took it back to the potential customer and 3 days later no dice, it still would not work... 1 week after that, I chased up the reseller and I learn that it is going well... I don't know what happened and I don't want to embarrass the guy but I would imagine that there was something amiss that he had not seen before... all it takes is one small error or setting for your AD I guess... I am quite certain that the AD issues are sorted in Gos 5.0.133 & 5.1.041 so try to go over your AD settings again just so you can rule that same issue (that my mate above had) completely out of the equation...