Networker

[Networker] nsrexec: authtype nsrexec HELP !!!

2004-01-20 15:03:48
Subject: [Networker] nsrexec: authtype nsrexec HELP !!!
From: "Mark Bradshaw (BTOpenWorld)" <notthehoople AT BTOPENWORLD DOT COM>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Tue, 20 Jan 2004 20:07:13 +0000
NetWorkers,

I'm at my wits end with this one. Any light anyone can shed on this
greatfully appreciated!!!

I have a Windows NT 4 SP6a client which I installed NetWorker 7.1 client on
to add to the backup schedule. Client has a single 100Mbit network card
(Intel) and 512MB RAM with 10GB of data. The server is a file server and has
McAfee installed on it.

Nothing unusual about the client to make me think there were going to be
problems, but running a probe on the client returns the error message:

nsrexec: authtype nsrexec

There is no other error message associated with this, which is strange as
you normally get another error message which shows you where the problem
really is.

Backup Server is Windows 2003, NetWorker 7.1 on same subnet as backup
client.

Ok, so to summarise what checking I've done since:

- ping short & long name from client to server (& vice versa)
- ping IP address from client to server (& vice versa)
- check through name resolution databases (cleared WINS, removed use of DNS
from backup server and client)
- nsradmin -s <client> -p 390113 connects and works successfully
- nwadmin and winworkr can connect to server successfully
- emptied SERVERS file, restarted services
- downgraded client version to 6.1.4
- upgraded device driver for network card on client
- swapped network card for a 3com and tried that
- stopped every service on the client which isn't part of core NT
- reapplied service pack 6a
- run nsrexecd and nsrd in debug mode during backups - nothing looks unusal!

There's another server here which is pretty much identical to the client I'm
trying to backup - it works fine. I've compared the 2 and can see no real
differences.

In desperation I removed 6.1.4 from the client and installed 6.1.3 as a
backup server onto the client to see if the client was ok. Interesting the
client cannot backup itself, again giving the same message!

Also, if try to perform a directed recovery from the 6.1.3 machine by
running winworkr on another machine in my environment it will allow me to
select the source machine, destination machine then says "Unable to Receive"
in winworkr.

Could anyone give me any suggestions as to what I could try now please? I've
run out of things to test!

Cheers

Mark

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

<Prev in Thread] Current Thread [Next in Thread>