Unsolved

This post is more than 5 years old

194 Posts

1496

April 18th, 2006 11:00

winworkr error - 'Cannot start session with server...

Greetings,

I need to be able to do restores from a PC running Windows XP. I loaded the software and ran winworkr -s . It starts and lets me to select the client and destination hosts. At that point it pops up the dialog box:

: Cannot start session with server ' ' is not properly configured on the Networker Server

On the Legato server I run nwadmin, go to 'User Groups', select 'Administrators', and I see the line:

user=semaskav,host=*

Isn't this correct? What am I missing?

Thanks,
Vic

194 Posts

April 18th, 2006 11:00

Forgot to mention we're using Legato 7.2.1

Vic

4 Operator

 • 

14.3K Posts

April 18th, 2006 12:00

You need to define your XP box as the client. Then, that box in alias list needs to have hostname and FQDN. In the past XP did require desktop clientpak for backup... AFAIK it is not required for restore so you should be fine with above once that you fix it. In short, pc-FQDN is being missed from alias list probably.

194 Posts

April 19th, 2006 07:00

Thanks for the help. I entered my PC as a client and was able to get into winworkr.exe. Tried to do a test restore and it now complains about permissions as follows:

Recovering files of client ' ' from server ' '
Permission denied

Nothing listed in daemon.log on the server. Don't know where else to look.

Thanks,
Vic

4 Operator

 • 

14.3K Posts

April 19th, 2006 09:00

Check:
- servers file
- if restore others client data make sure you are on the remote access list of that client
- make sure you have write permissions on the file system where you are restoring data
- make sure that file system type is the same as of the backup client

194 Posts

April 19th, 2006 10:00

Another step closer. This time it was that the PC wasn't in the 'Remote access' list for the client being restored.

Now when I try to do a directed restore it says:

Recovering files of client from server .
Connection timed out

So, to me, it sounds like this now may be a firewall issue.

I also had to edit nrsla.res on the client and change:

administrator: *@localhost;

to

administrator; *@localhost, root, vsemaska;

so I could view the ports the client is using. Yes, I did restart the Windows service after changing the file.

Vic

4 Operator

 • 

14.3K Posts

April 19th, 2006 11:00

Connection timed out is generally network issue where you may face:
- firewall blocking communication (should be able to verify with sniffer or via firewall log)
- route is not set correctly (should be able to check that with rpcinfo or even traceroute)

When you initiate the restore from the client check on server side (via sniffer or netstat) if communication is established.
No Events found!

Top