Most of the case I saw that was related to dns issues,
windows adding one after the other the dns suffix you filled
in the NIC's setting when nslookup'ing.

Have a try using nslookup and then querying ip, then
name and then FQDN, not just ping. Use also "nbtstat -a" to verify.
Have also a try to fill host files, hosts file being first processed
before dns. Be also sure "127.0.0.1 localhost" to be in client host
file.

Try once to replace "all" from saveset list
to C:\, system state:\ ....
I think to remember something that preventing All
to be process probe.

Give also netstat -a or netstat -an to list
issued communication.


BTW, what's your NIC card type ?
 
HTH,

Thierry



Kind regards - Bien cordialement - Vriendelijke groeten,

Thierry FAIDHERBE

HP Service - Storage Division
Tru64 Unix and Legato EBS Consultant
                                   
 *********       *********   HEWLETT - PACKARD
 *******    h      *******   1 Rue de l'aeronef/Luchtschipstraat
 ******    h        ******   1140 Bruxelles/Brussel/Brussels
 *****    hhhh  pppp *****   
 *****   h  h  p  p  *****   100/102 Blv de la Woluwe/Woluwedal
 *****  h  h  pppp   *****   1200 Bruxelles/Brussel/Brussels
 ******      p      ******   BELGIUM
 *******    p      *******                              
 *********       *********   Phone :    +32 (0)2  / 729.85.42   
                             Mobile :   +32 (0)498/  94.60.85 
                             Fax :      +32 (0)2  / 729.88.30   
     I  N  V  E  N  T        Email :    thierry.faidherbe AT hp DOT com
                             Internet : http://www.hp.com/ 
________________________________________________________________________

MOBISTAR SA/NV 

SYSTEM Team Charleroi, Mermoz 2 Phone : +32 (0)2  / 745.75.81  
Avenue Jean Mermoz, 32          Fax :   +32 (0)2  / 745.89.56  
6041 GOSSELIES                  Email : tfhaidhe AT mail.mobistar DOT be
BELGIUM                         Web :   http://www.mobistar.be/
________________________________________________________________________

 

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Mark Bradshaw (BTOpenWorld)
Sent: mardi 20 janvier 2004 21:07
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] nsrexec: authtype nsrexec HELP !!!

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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=