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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Connection Refused

Status
Not open for further replies.

AdeyWheway

Vendor
May 5, 2003
5
GB
All,

Please help - I've been unable to resolve this problem despite repeated attempts!

I have Legato 6.1.3 (latest evaluation version from Legato website) configured on 2 x Windows 2000 (service pack 3) servers - one as a client the other as a backup server, with backup device connected. I installed everything a few days ago, so the eval has not expired.

I have setup the res/servers file on the client to state the short and full DNS name of the backup server.

On the Windows 2000 'client' server, I can open the Network User program and successfully backup to the Win2k 'backup' server.

However, when I attempt to schedule a backup of my Win2k 'client' server from the Win2k 'backup' server within Networker Admin (scheduling appropriate group containing client), I constantly receive the 'connection refused, attempted 1 retry, connection refused' error messages.

All Networker services are running on both servers. Network connectivity is fine - RPCinfo reports that ports are open.

We do not have reverse lookup DNS running on our network, so I configured the hosts file on each server to resolve short/full DNS names for both the client and backup server - this made no difference.

Any suggestions would be very greatly appreciated!
Regards,
Adrian.

p.s. (I'm a technical user, not a vendor!)

adrianwheway@hotmail.com
 
Try stopping the Networker remote exec service on the client, and launch it from command line with this command:

nsrexecd -i

Then, while its running, retry the backup, and see if it resolves the problem. If so, then you've got name resolution problems.
 
Thanks for the advice.

I tried your suggestion, but am suffering the same issue.

I stopped the Networker remote service in the Services Applet on the Legato 'client' server and then ran the command you indicated.

Interestingly when I checked back (and refreshed) the services applet view, the Networker Remote Service did not indicate that it had started.

I have de-installed IIS on my 'client' server which is a member of a domain, as is the Legato 'backup' server. Domain & local administrators & system, have rights to the C: system drive that I am attempting to backup on the 'client' server, only system and Domain Admins have rights to the other drives on the 'client' server.

Any further suggestions welcome.
Thanks,
Adrian.
 
Have just found the cause of my problem!

I had setup the hosts file on both the Legato backup server and client server to enable resolution of both systems with short/full DNS names. However, I'd got one digit incorrect in the TCP/IP address in the host file on the client server. Correcting this fixed the issue. Sorry, I should have known better.

We're are now going to configure reverse DNS lookup on our network.

Thanks again.
Adrian.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top