Netware 6 error. Connection refused.

[mawalsh]

I get a

Connection refused

error when trying to backup a Netware 6 client using NetWare ClientPak 4.2x.

Any suggestions? Thanks.

 

[sdeb]

Check your HOSTS files or your DNS configuration.
Then try to fullfill aliases fields in Networker for both the client and the server.
Might be a name resolution error.

 

[Riaan]

Check out the following bulletin:

http://www.legato.com/resources/bulletins/

299: IP Naming in Heterogeneous Environments (UNIX | NT | NetWare | Windows 95)

you should be able to ping and rpcinfo between the client and server with long and short names. =

Riaan van Niekerk
UNIX sysadmin
Potchefstroom University
South Africa

 

[esa68]

I have the same problem but I´m able to backup from the client, but when I try to make backup from the backup server, I get the "Conection refused error".

I´ve 12 Netware clients, and none of them answers to rpcinfo, but I´m able to ping all of them. Only one client doesn´t backup, the others goes fine.

Client features:

Netware 4.11 SFT III , con el Support Pack 6.
Version TSA. TSA410.NLM version 4.16, 24-Jun-99.
Version de Networker: 4.21

And the most strange when this machine is rebooted is that the scheduled backups of this client goes fine during three or four days.

 

[mawalsh]

I know it's been a long time, but I am back with this again.

I have Networker on a Sun E450, Solaris 9, Networker 6.1.2. The Novell client is Netware 6.0 running the 4.2 client.

The messages I am getting is:

savegrp: cobrarobe succeeded.
* cobra:All rcmd cobra, user xxx.central: `savefs -s backup -c cobra -g Test -p -l full -R -v'
* cobra:All 08/26/03 09:04:02 nsrexec: nsrexecd on cobra is unavailable. Using rsh instead.
* cobra:All nsrexec: authtype rsh
* cobra:All Cannot make TSA connection to default NetWare server 0xfffdffba
* cobra:All Backup cobra: failed.

Any suggestions on what to look at next?

Thanks.

 

[605]

It looks like you have not started the client "listener".
However this may also occur when you have a name resolution
problem (reverse name lookup does not resolve to the same
address).

 

[Till]

Hi All

Interesting case, we have the same problem as well sometimes.
What do you mean with "client listener" not started ?
Could you please be a little more surprised ?

Thx

Till

 

[joeunixadmin]

Hi,

I'm not very familiar with Netware but, If this problem was on a unix or windows I would say that a Service/Daemon is not starting automatically after booting. I believe in Netware it is called NLM. Is there a NLM for NetWorker? Maybe this NLM needs to be added to a start script.

-Joe

 

[mawalsh]

DNS in both ways works from the client and server.

Does anyone know the names of the NLMs which need to be loaded?

Thanks.

 

[605]

The client listener ist nothing else but NSREXECD. That's
its main functionality. However, the equivalent daemon on
NW/Netware is called RCMDSVR.NLM (Remote Command Service),
which needs to listen to the NW server.