If you google you will find a lot of entries for that error message. Unfortunately, the NW Error Message Guide does not have any hint. I expect trouble with the firewall ports (9737 & 9738)
You better start with a communication check between the clients as this is mandatory for the communication. The standard procedure is to run
nsradmin -p nsrexec -s name
from both sides. So you should use
from the NW server nsradmin -p nsrexec -s client_name and
from the NW client nsradmin -p nsrexec -s server_name to verify a positive connection.
Also let us know your NW versions. Using savefs tells me that you use a pretty old environment.
Sorry, my fault. Of course the ports did not change at all over all years.
Besides that your problem is not easy to investigate. First of all I would check whether this is a new client or whether it has already worked in the past.
If it is an older installation then something within the network must have changed that NW now fails.
If it is a new configuration, you might download the NetWorker Test & Troubleshooting Tool NTT from the NetWorker site. Install and run it - it will give you much more details.
bingo.1
1 Rookie
•
2430 Posts
429
0
Posted October 21st, 2022 07:00
If you google you will find a lot of entries for that error message. Unfortunately, the NW Error Message Guide does not have any hint. I expect trouble with the firewall ports (9737 & 9738)
You better start with a communication check between the clients as this is mandatory for the communication. The standard procedure is to run
nsradmin -p nsrexec -s name
from both sides. So you should use
from the NW server nsradmin -p nsrexec -s client_name and
from the NW client nsradmin -p nsrexec -s server_name to verify a positive connection.
Also let us know your NW versions. Using savefs tells me that you use a pretty old environment.