Connect Snap Server Directly to Windows Server

I have a Snap Server 4500 and, instead of accessing it through the network, I'd like to connect it directly to my Windows 2003 server and use it for storage of SQL Server backups. Does anyone know if this can be done and, if so, how? The Snap website implies that it can be done with a crossover cable, but doesn't provide any information on how to access/map the drives after it's connected.

Thanks,
Hari

I plugged the Snap server into the second network port on the original server, but the configuration utility that came with the Snap server doesn't recognize that it's there. I've tried letting it assign an IP address and I've assigned one manually. I can't set the IP address of the original server to a private IP address as you described because I need users on the network to be able to connect to it from the network. Do you think that's why the configuration utility can't see the Snap server and, if so, do you know of a possible way around that requirement?

Thanks,
Hari

I'm sorry - I mislead you on that. It's the SQL Server I need to make sure users can connect to. You had said that both the SQL Server and the Snap Server would need to have private IP addresses and I assumed a private IP address would prevent users from being able to see the SQL Server. I'm a little fuzzy on internet technology. I can make it a static IP address (and had planned to), but I don't know anything about private IP addresses.

I'm trying to do this for two main reasons. One is that I just started working in an environment where I have no control over the network - and have little access to information regarding its configuration. We're a tenant in someone else's building. The other reason is security. This is very sensitive data and, if I have to put the Snap Server on the domain, I'm going to have to password lock (and possibly encrypt) my backups. I was hoping that I could just connect the Snap Server to the SQL Server in a way that no other computers could see it and use it to store my database backups.

I really do appreciate the help on this. If it ends up that it won't work, I'll see if I can get them to add the Snap server to our domain, but if you have any suggestions, feel free to toss them my way. The Snap server manual describes two methods for connecting and running the configuration utility. One is through a browser using either an IP address or the default Snap server name and the other is using a standalone Snap Server Manager utility installed on the server. Both are supposed to automatically detect the server, but neither option recognizes that the Snap Server is connected. The problem is that I have limited knowledge of how to select appropriate IP addresses. I contacted the manufacturer and they just said the IP addresses of the servers needed to be on the same subnet, but I made sure they were and it didn't make any difference. I've tried pinging the IP address for the network connection the Snap Server is on and I do get a reply.

Thanks again,
Hari

You may have just told me what the problem is. I inherited this Windows server and don't have the documentation for it, but I have a feeling the two network ports are actually dual ports on the same network adapter - for load balancing. To make this work, I probably need to add a completely separate network adapter with a 3rd port.

Thanks!

Hari

Yes, there are two network connections. But, no matter what IP address I set them to, they both seem to point to the local drives on the Windows server instead of the Snap server.