Snap Server 4000 compatible with Windows Server 2003???

[mripca]

Hi folks, my first time posting here, so I'm hoping you can help me out.

I've got two Snap Server 4000s that have been running great for a really long time, practically bulletproof. One has even been off-line for a couple years (didn't really need it anymore). The one that's been up and running all this time is running Snap OS 3.4.772. I had upgraded the other one to v4.0.860 a few years ago, but then never did anything with it as I didn't see/feel any differences.

I'm the Mac tech guy in our in-house graphics dept, but we have a whole other IT dept that manages all the hundreds of WinXP PCs in the building and all of their Windows and NetWare servers and networking stuff. I manage an Apple Xserve along with a few other smaller Mac servers, plus these Snap servers that are just used by my dept. I originally got them for easy-to-access network-accessible closet space. Right now we really just use the one for exchanging files between out Macs & PCs. Myself and the other designers have dual Mac/PC workstations.

Here's my problem: My IT dept switched their WINS/DNS servers over to Windows Server 2003 (from 2000). As soon as they shut down the 2000 server, our Snap server became unaccessible from our PCs. We can still get to it fine from the Macs (OS 9.2, 10.3, 104).

So... We double-checked all of the network settings on the Snap server, and I even cranked up the upgraded Snap, but that wasn't accessible either. Am I SOL with getting access back on the PC side?

I checked Adaptec's support section and couldn't find any specific reference to this issue, so I started Googling it, which is how I found this site. Great resource by the way!

Thanks in advance...
Mike

[blue68f100]

Welcome to our forum,

For MS AD 2003 support you need SnapOS v4.0.860. Double check the AD pointer. I do not use AD at home so other users that do may/will key in. You can also use the search feature of the forum for AD 2003 or AD2003.

Adaptec has marked the SnapOS as EOL and is no longer supporting it.

With in the last year we have been getting more and more request for help with the GuardianOS. The GuardianOS units w/v4.2 up supports Vista with the latest 4.4.049 supports Vista and the Latest MacOS 10.5. There are rumors of a v5 coming out that will support MS AD 2008, no date on the release.

[mripca]

Thanks blue,
Like I said, one of my Snap 4000s is already running 4.0.860, but I still can't access it from my XP box.

Sorry, but I know next to nothing about Windows Server management. When you say "AD", is that "Active Directory"? Where do I find this AD Pointer?

Yes, I'm aware the Snap OS is EOL, thanks.

Do you know if can I install the GaurdianOS on my 4000s? Is that a free download now, too?

[bitor]

Greetings:

I can answer the GaurdianOS question. No you cannot install GaurdianOS on SnapOS systems. As far as the WinSer2003 I know nothing about this OS system so I cannot help you there. I don't know if this makes a diff. , but did you do a 4.0860 upgrade or a full install? Might be a diff. in the two as a guess.

bitor

Originally Posted by mripca

Thanks blue,
Like I said, one of my Snap 4000s is already running 4.0.860, but I still can't access it from my XP box.

Sorry, but I know next to nothing about Windows Server management. When you say "AD", is that "Active Directory"? Where do I find this AD Pointer?

Yes, I'm aware the Snap OS is EOL, thanks.

Do you know if can I install the GaurdianOS on my 4000s? Is that a free download now, too?

[mripca]

Thanks Bitor, I believe I did an upgrade to 4.0.860, not a full install. Then again it was probably about 3-4 years ago, so not 100% sure. I still have all of the files. The "SnapOS_4_0_860.exe" file is over 21mb. Not sure if that's an upgrade or full install.

[mripca]

Anyone else here happen to know what this "AD Pointer" is that blue68f100 is eluding to?

[blue68f100]

I know very little about AD. The pointer is under the Network setting Advanced. There should also be pointers on the server side too. If not working I would blank the out, back out then go back in and enter the path to the servers. This way if something is corrupted, you will clear it out.

Sorry not my cup of tea.

[[AfZ]PiMp J]

i acquired my snap servers from my job, where the environment is a mix of macs and pcs. the user's pcs had mostly, and now fully, windows xp, and the servers were mostly server 2003. our primary domain controller, (which controls active directory) and our dns server (which is also our wins server) is server 2003.

the snap servers i have, worked fine in that environment.

i will assume you're trying to access your snap servers from the pcs using the hostname of the snapserver. for this to work, your dns can have a static entry added to it, to point to the ip of the snapserver (set its ip to static as well)

if you are trying to access the snapserver by IP and it's not seeing it, can you at least ping the snapserver ip from within windows? how do you access it from the pc side? are you going to START -> RUN and typing \\snapserverhostnamehere ?

[mripca]

We finally got it figured out. I definitely needed to upgrade both Snaps to OS 4.0.860. Then we followed the instructions from this link:
http://wiki.procooling.com/index.php...able_.5Bfix.5D

but I still had access issues, so I turned off Novell Networking, and then had to refresh the Workgroup/Domain user list from the AD2003 server by using my network ID and password as an example (in Security > Security Guides > "Using Windows domain security").

That did the trick.

Thanks for everyone else's suggestions... much appreciated!

PS: We access these servers from the PCs using a shortcut that was originally created by going to My Network Places > Entire Network > Microsoft Windows Network > [workgroup name] > and then both Snaps are listed as "Snap Server 172.18.61.5 (GSserver3)" and "Snap Server 172.18.61.6 (GSserver4)". From the Mac side, we never had a problem accessing them using just the IP address using Go > Connect to server... in Mac OS X (10.4.11).