Problems after the server name was changed 3

[vampyre2000]

Please help..
Ever since replacing an old server we have been getting the errors below:

For a long time no we have been getting the following errors
Error E3201 Unable to connect to network drive
Note connect to dhservernew admin$ as administrator

I think the problem happened because we called the new server dhservernew and set up all the software, migrated the data and changed to name back to dhserver once the old server was switched off.

The problem is that there seems to be no way of telling arcserv the the old server name no longer exists.
All the data on the server is backuped OK. But we keep on getting the errors.
Is there any way of deleting the old references. Short of reinstalling...
Many thanks to all

 

[yvfwc]

What version of Arcserve? What OS?

Cheers,

Mark ;-)

 

[santanaa]

Hi,

One question:

After migrated the data, have you changed the job?

OK, i know that it seems a stupid question, but you did'nt say that you have changed the old job to not try to backup the data from the dhservernew if you were making it using the network.

Another question: Are you making the backup of the dhserver(new) via network ?

I had a problem a little like yours but the backup has been made using network.

Bye,

 

[monkeylizard]

If you're using the client agents, when you modify the job in the Source tab, you can right-click on the client agent for dhservernew and Delete it. If dhserver doesn't appear, then right-click the Client Agents branch and do a Find New Agents (or something like that). Monkeylizard
-Isaiah 35-

 

[Guest_imported]

Check the system environment variables. Arcserve does not reset these variables after re-install.

LNAME, RNAME.

Hope this helps