Rampage 8.6 cannot write to server!?!?

[Glenn]

A client of mine running RAMpage 8.6 recently lost both hard drives on it's server (Windows NT).
They have replaced the hard drives, re-installed Windows NT, created 2 shares, one named Ram_Vol (for Rampage preferences and RSI data) and one named Data_Vol, which contains the live prepress jobs. They ran the Network install app from the RAMpage rip as per installation instructions. The RAMpage rib box connects to the Ram_Vol share but when the rip software is launched, it gives this error:

Rampage Master Volume
"The specified volume CANNOT BE FOUND, or does not have WRITE permission.
Probably the volume isn't mounted or is invalid."

Well the volume is mounted and does have write permission!

Any ideas on how to resolve this?

Thanks in advance!

 

[david.young]

At the rip, under preferences, are the paths set correctly?

 

[Glenn]

At the rip, under preferences, are the paths set correctly?

Yes, the only way I don't get an error is when I point the rip to the C drive of the rip, which of course is useless.

 

[david.young]

Just a silly thought, have you restarted everything, and I do mean everything, rip, server, workstations.....
Been awhile since I dealt with an NT box but I seem to remember they could be quite finicky

 

[heffinchester]

Are logged into the server as Administrator?

Jeff

 

[Glenn]

Just a silly thought, have you restarted everything, and I do mean everything, rip, server, workstations.....
Been awhile since I dealt with an NT box but I seem to remember they could be quite finicky

Yes, restarted all machines and still get same error.

 

[Glenn]

Are logged into the server as Administrator?

Jeff

Administrator account is the only account on the rip. Also login as Administrator on the server.

 

[Jnsic]

At the rip, under preferences, are the paths set correctly?

We had a similar situation last week. We had to give Rampage a call to have them fix it. But, temporarily, we set up another drive on the server to be the "Rampage" drive, which seemed to work without Rampage assistance.

 

[MacTwidget]

What networking protocol are you using to connect? AFP, SMB or ??

 

[Glenn]

What networking protocol are you using to connect? AFP, SMB or ??

Connecting with SMB

 

[Glenn]

I don't know what the deal is here. Even if I do get it working, all the rip and device profiles were lost with the hard drives that failed.

 

[Raymond Ramirez]

Did you resolve this

 

[Glenn]

Did you resolve this

No, never got it connected, been farming out plates.

 

[Raymond Ramirez]

please email me at [email protected]

 

[prepressdork]

It's been a long time, but if memory serves, there was a registry entry needed so that NT knew the connection was an administrative share:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters\NullSessionShares

In NullSessionsShares, you type the name of the share EXACTLY as it is shared. Here's a link for more info:

How to enable null session shares on a Windows 2000-based computer

Perhaps this will help,
pd

 

[Chasfinch]

you must install AFP on the the windows boxes. Rampage uses AFP. I will break out the manual when I have time and see if I can find what you need to do.