Jump to content

Password not being remembered (automatic login, network volume)


IanGrimstead

Recommended Posts

Hi,

 

I've been having odd problems with the auto-login feature of Retrospect Express 6.0 (running under XP Home); I've used the tutorial:

 

TITLE: How to edit the Launcher Service and configure an Automatic Login to backup mapped volumes - Windows 6.0 and earlier

 

Article ID: 2776

 

To set up auto-login for network mounts. This works fine, but... every now and then, the password is forgotten (i.e. I run Retrospect manually, check "My Network Places", Properties, click on the drive icon for the password and... nothing is set!).

 

The remote mount is on a laptop that's given its IP address via DHCP, but it is always showing up "A" ok under windows when checking the machines in the local workgroup... odd. Its as if something, somewhere is reseting the p assword I'm typing in, and deleting it.

 

Help! :-(

 

Ian

 

Link to comment
Share on other sites

Hi,

 

Retrospect client is a good way to get around this kind of thing. Is there are reason you are not using the client?

 

If the client is a No go I suggest a full uninstall/reboot/reinstall of Retrospect and deleting the configuration files found in documents and settings\all users\application data\retrospect. The bad news is you will have to set up Retrospect from scratch but you will eliminate any possible corruption in Retrospects services and config files

 

Nate

Link to comment
Share on other sites

Hi Nate,

 

Thanks for the thoughts - I'm not using the client as... it's a Linux partition I'm backing up over samba (hence my other post ;-)

 

I'd rather not steam clean Retrospect for the minute; hmmn. I wonder if it's because the network connection is occasionally not present, so when an auto backup is fired, the login fails (as the machine is offline), so it forgets the password?

 

Ian

Link to comment
Share on other sites

Hi Ian

 

Retrospect should remember the login info no matter if the volume is present or not. I'm afraid new config files may be your only hope for a fix. You could rename your current config files and run a test with a new set to make sure.

 

Do you have the same problem if you try this with a native windows volume?

 

Thanks

Nate

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...