Unsolved
This post is more than 5 years old
46 Posts
0
5932
NetWorker through a firewall
Hi Guys,
I am trying to configure a client to back up through the firewall. I am running 7.4.1 on the server and on the client. Both are Windows 2003 SP1.
The firewall guys have opened 7937-7941 ports on the firewall.
When I try to configure the port range through local hosts I am getting "failed on UDP ping".
Also when running nsrports -s "servername" on the client I am getting :
"nsrports: RAP error: Service not available."
All hosts files are correctly populated with short and FQDN with correct IPs on both server and client.
If I run ping and ping -a, both ways, I am getting successful name resolution. When trying to run save -vvv from the client to the server I am getting the following errors:
39076:save: RPC warning: RPC cannot make a procedure call: Create failed: 352:Remote system error - Connection refused
When running rpcinfo -p from the client to the server I am getting the following:
C:\Documents and Settings\administrator.EXTRANET>rpcinfo -p 10.0.0.60
rpcinfo: can't contact lgtomapper: rpcinfo: 344:RPC receive operation failed.
network connection could not be established with the host.; errno = Connection
reset by peer
Can anyone help please?
I am trying to configure a client to back up through the firewall. I am running 7.4.1 on the server and on the client. Both are Windows 2003 SP1.
The firewall guys have opened 7937-7941 ports on the firewall.
When I try to configure the port range through local hosts I am getting "failed on UDP ping".
Also when running nsrports -s "servername" on the client I am getting :
"nsrports: RAP error: Service not available."
All hosts files are correctly populated with short and FQDN with correct IPs on both server and client.
If I run ping and ping -a, both ways, I am getting successful name resolution. When trying to run save -vvv from the client to the server I am getting the following errors:
39076:save: RPC warning: RPC cannot make a procedure call: Create failed: 352:Remote system error - Connection refused
When running rpcinfo -p from the client to the server I am getting the following:
C:\Documents and Settings\administrator.EXTRANET>rpcinfo -p 10.0.0.60
rpcinfo: can't contact lgtomapper: rpcinfo: 344:RPC receive operation failed.
network connection could not be established with the host.; errno = Connection
reset by peer
Can anyone help please?
ble1
2 Intern
2 Intern
•
14.3K Posts
0
July 10th, 2008 03:00
Not sure why nsrports doesn't work, but it could be already set range. Try to change it via nsradmin.
rpcinfo is using port 111 which probably is not open - instead use nsrexecd port with nsradmin to test remote connectivity.
dd1980
46 Posts
0
July 10th, 2008 03:00
as always you are very helpful (thanks a bunch ;-))
No I tried to run the following from the client:
nsradmin -p nsrexec -s 10.0.0.60 "NetWorker server"
This is what I am getting
39078:nsradmin: RPC error: RPC receive operation failed. A network connection c
ould not be established with the host.
There does not appear to be a NetWorker nsrexecd server running on 10.0.0.60.
Now I know that nsrexecd is running on the networker server as there are other backups running.
I did try to telnet back to the server on port 111 and that is closed, so I have just put in a request to have that open.
It should be done in an hour or so so I will keep you posted.
Thanks
dd1980
dd1980
46 Posts
0
July 10th, 2008 04:00
I tried what you suggested and here is the outcome:
C:\Documents and Settings\administrator.EXTRANET>echo p | nsradmin -p 390113 -i
- -s 10.0.0.60
39078:nsradmin: RPC error: RPC receive operation failed. A network connection c
ould not be established with the host.
There does not appear to be a NetWorker nsrexecd server running on 10.0.0.60.
I have checked and the RPC service is started on both machines.
ble1
2 Intern
2 Intern
•
14.3K Posts
0
July 10th, 2008 04:00
You can use this against any client/server from any client/server.
ble1
2 Intern
2 Intern
•
14.3K Posts
0
July 10th, 2008 05:00
ble1
2 Intern
2 Intern
•
14.3K Posts
0
July 10th, 2008 05:00
dd1980
46 Posts
0
July 10th, 2008 05:00
If I run
telnet 10.0.0.60 7937
telnet 10.0.0.60 7938
from the client
and
telnet 172.16.1.54 7937
telnet 172.16.1.54 7938
from the server, they all run successfully.