Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Connection Refused for Exchange backup???

Status
Not open for further replies.

MISCHICK1

MIS
Aug 28, 2002
10
US
I can't seem to backup anything on Exchange.

I'm using Networker 6.1 on the networker server running Linux 7.2.

We just migrated our Exchange server to a box running Windows 2000 and Exchange 5.5.

I.P. and Host name have been put into the host file. Networker admin can connect to the networker server from exchange and visa versa.

Reverse lookup was fine.

I installed the networker client, BSM 2.0 but it will not run.

Scheduled backup was configured correctly.

The old Exchange server was fine. It was an NT box and the backup server at the time was also NT.

The new box is on a different segment from the Networker server.

I'm still awaiting a call back from Legato tech support but thought someone here may have some ideas of what is wrong.

Thanks for you help! :)
 
Are you using the exchange BSM command?
Are you running the command as a user with exchange Admin priv's?
Is the BSM on the client started with exchange admin privs (not system account)?
 
Hi

Have you tried carrying out a normal filesystem backup of your exchange server? This might point you in the right direction. Also try running the NetWorker Exchange User program on your Exchange server and kicking off a backup that way. I've seen problems where manual backups of this sort will work but scheduled ones won't so this can be a good starting point!

What message are you getting from Legato? Are you just getting "Connection Refused" or something else as well? This will help narrow down the problem.

If you are getting a connection refused then check that the NetWorker Remote Exec service is up and running on your Exchange server. Check and double check the IP addresses in the hosts files of both the NetWorker server and the Exchange server. Also, if you have a DNS server check that the Exchange server is correctly entered into DNS and that there isn't a rogue entry in there which is throwing NetWorker.

Good luck!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top