Legato 6.02 backup problem on NT 4.0 SP 6A

[dchp]

We are getting the following error on Savegrp. Any information on this error would be helpfull. We have deinstalled, and reinstalled the client. All systems are nt 4.0 service pack 6A. Backup is working on one client in the same subnet, but not the one below. The clients are identical Dell's.


08/22/01 04:47:49 PM savegrp: command 'savefs -s chc06.cfs -c chc03.cfs -g Default -p -l full -R -v -F c:\ d:\ e:\ ' for client chc03.cfs exited with return code 9.
08/22/01 04:47:49 PM savegrp: chc03.cfsrobe unexpectedly exited.
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = savefs
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = -s
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = chc06.cfs
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = -c
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = chc03.cfs
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = -g
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = Default
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = -p
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = -l
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = full
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = -R
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = -v
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = -F
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = c:* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = d:* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: current token = e:* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: port = 28789, res = 0, errno = 22
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: port = 28790, res = 0, errno = 135
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: Adding port range (reserved): 600-1023
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: using reserved ports to connect
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: port = 28791, res = 0, errno = 22
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: port = 28792, res = 0, errno = 135
* chc03.cfs:c:\ 08/22/01 04:47:01 PM nsrexec: port = 867, res = 0, errno = 135
* chc03.cfs:c:\ 08/22/01 04:47:02 PM nsrexec: port = 868, res = 0, errno = 161
* chc03.cfs:c:\ 08/22/01 04:47:05 PM nsrexec: port = 869, res = 0, errno = 161
* chc03.cfs:c:\ 08/22/01 04:47:09 PM nsrexec: port = 870, res = 0, errno = 161
* chc03.cfs:c:\ 08/22/01 04:47:14 PM nsrexec: port = 871, res = 0, errno = 161
* chc03.cfs:c:\ 08/22/01 04:47:24 PM nsrexec: port = 872, res = 0, errno = 161
* chc03.cfs:c:\ 08/22/01 04:47:41 PM nsrexec: port = 873, res = 0, errno = 161
* chc03.cfs:c:\ Connection refused
08/22/01 04:47:49 PM savegrp: chc03.cfsrobe will retry 5 more time(s)

 

[jboyer]

I am getting a similar problem with a NT box once I applied the security rollup patch. The problem is the NT box is not communicating with the rpc process. Running rpcinfo -p server, gives a failure. I have not been able to get rpc to talk again. Any ideas??

 

[dchp]

Thanks for responding. I have not installed that patch, but I have the same problem with rpcinfo.

 

[Legato007]

Fellow NetWorker victims,


The error message you are getting has to to with connectivity issues between the client and the server. To resolve this issues follow the technical bulletin produced by Legato at

http://www.legato.com/support/documentation/bulletins/299.html.

I find that 9 times out of 10 this troubleshooting guide helps immensely.

 

[jboyer]

I have gone through the Legato FAQ and found out what the problem is but there is no information on how to solve the problem of rpc not communicating.

 

[Legato007]

Do not look at the FAQ section. Read the Bulletin that I have attached to my previous thread.

 

[jboyer]

I have gone through that bulletin and it did point to the rpc problem. I am running only the Legato portmapper and everything looks the same as the other 4 NT servers that are working. This box was working until I installed the MS roll-up patch, it hasn't worked since. I have not installed the roll-up patch on any of the other machines. It is obvious to me that MS changed something that stopped the rpc from talking, but what?

 

[eskolnik]

Any answers here! I have the problem on Win 2K clients

 

[TDun]

Do you have any Internet security software or firewall software on the client that is not working?