"actively refusing a connection" ususally means that the NW client daemon/service is not responding.
- It could be that it has not even started
- It could have died
- It could also be a firewall issue
Try to reach the client from the server by running "nsradmin -p nsrexec -s client_name".
If this succeeds than use nsrpush.
Thanks for your reply.
I have tried running that command but it does not seem to work.
It just logs into the nsradmin prompt and i cant run anything else from there.
Not sure if this is a change in networker 9 or not.
I tried running the nsrpush command on the networker server locally with "nsrpush -i *server* to see if it could be a firewall issue. Windows firewall is disabled on the server but is still fails with the below.
I have also run the nsrcpd through the command prompt and get a heap of errors as below that just keep scrolling through.
To me it kind of seems like a database has been corrupted somewhere
I'm fast running out of ideas as the server has already been rebooted so if its an issue with the service itself it seems there may be a bigger issue.
After some more troubleshooting i have managed to get it semi working.
The main issue now is that the nsrpush command does not seem to be able to start nsrcpd correctly.
If i have the nsrcpd manually running in cmd nsrpush will work perfect.
However when i just run nsrpush solo i can see the nsrcpd start in the processes but it dies pretty much straight away with the same closed by remote host error as before.