Jump to content
mastercam

C: Volume Not Seen By Server

Recommended Posts

Hi - we have a 7x server and client set up. 

 

The client c volume was able to be seen...now it's not. 

The e volume is still seen...not the c.

 

So - I thought I'd update to 9.5 - server side went well...and to our wonderment...so did they client update from the server.

 

All this while a c:\drive was not seen from the server side. 

 

And it's still not seen....only the E volume (his local external drive).

 

We checked in windows and the SYSTEM ID seems to have full access to the C:  volume.

 

Any ideas? 

 

Thanks!

Share this post


Link to post
Share on other sites

Try removing the Client on the Server then adding it again and see if this restores the C: drive.

 

Do you backup the Client by selecting the individual volumes or by selecting the client as a whole? This can make a difference to the visibility of a volume if a change is made such as to its name or size.

Share this post


Link to post
Share on other sites

Try removing the Client on the Server then adding it again and see if this restores the C: drive.

 

Do you backup the Client by selecting the individual volumes or by selecting the client as a whole? This can make a difference to the visibility of a volume if a change is made such as to its name or size.

 

 

We tried that....nothing. 

 

The tech mentioned to see what user the service was running under. Said is was to be 'system' , it is no...it's running under the logged in user. 

 

The odd thing...we can see the E:\drive.

Share this post


Link to post
Share on other sites

The Retrospect Client services (Retrospect Client, Retrospect Helper and Retrospect Instant Scan) should be set to log on as Local System account. This allows them full access to the system. Running under any other account limits thier access to the system.

 

The C: drive is a system drive whereas the E: drive is non-system drive. To be able to access a system drive the Retrospect Client services have to be running under the System account. If the services are running under a User account it will only be able to access non-system drives [that that user has access to].

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×