Hi to you all,
-Timothy Biles:
The error message:
"Cannot make TSA connection to default NetWare server 0xfffdffba"
Means just like it states. Regarding to the HEX error code, according
to a document I found on Novell's own site. The error message means:
0xFFFDFFBA NWSMTS_TSA_NOT_FOUND Invalid or inactive TSA specified
Here is the link to the document:
http://developer.novell.com/ndk/doc/smscomp/index.html?page=/ndk/doc/smscomp/sms_docs/data/hka0ofpt.html
What I can see in your NWLOG.TXT. You may want to try reconfiguring
your SMDR. First, you got to shutdown everything that has something to
do with the backups, as I already explained. On the affected NetWare
box, Exit the NetWorker GUI, type NWDOWN in the console, unload
TSAxxx.NLM, unload SMDR.NLM. Now, make a backup copy of your SMDR.CFG.
You can find it under: SYS:ETC\SMS\SMDR.CFG. When you load the
SMDR.NLM, you type (in the NetWare console): load smdr new Answer the
questions, load TSAxxx.NLM, start NetWorker and here we go! Hopefully,
it will work this time. If not, I don't have a clue.
Be sure about what you're doing, This are only recommendations that
work for me.
-Tim Mooney:
The HEX code seen in the error message, is in fact a error message and
not an IPX/SPX address. Even if they look much alike. The problem you
guys encounter, with NetWare 6. Is that even if you are running only
IP, and not even have IPX/SPX installed. The NetWare server wants an
IPX/SPX server id, when running NetWorker. Exactly why?... I can't
answer, but it does. Otherwise you will see some error messages in the
LOGGER SCREEN, that nags and nags, on and on about it.
Hope this help and good luck once more!
/Joaquin Camp.
On Fri, 2003-03-28 at 23:07, Tim Mooney wrote:
> In regard to: Re: [Networker] Netware client backup from a UNIX server,...:
>
> >I'm seeing the exact same error message on a Netware 5.1 box:
> >
> >Cannot make TSA connection to default NetWare server 0xfffdffba
>
> I know next to nothing about NetWare, other than the NetWare clients
> we back up view NetWorker are a thorn in my side.
>
> [remainder of message deleted]
>
> >I also posted a similar message to the Netware backup for 5.x newsgroup,
> >and am hoping to hear from someone there about the Netware error code
> >0xfffdffba. This is actually the first good clue I've received, so I now
> >hope that someone from Novell sees it and knows what the heck it means.
>
> Are you sure that `0xfffdffba' is an error code? Based on the message
> that's being spit out, it looks more like one of those internal host ids
> (I think they're IPX/SPX related, but I don't know -- like I said I don't
> do NetWare). Do you have some system that has an IPX/SPX host id that
> matches that?
>
> FYI, our NetWare guys had some problems with the client under NetWare 6.x
> *until* they set an IPX/SPX id, similar to the hex number shown above.
> Even though 6.x can do IP internally, the Legato client (and some other
> software they loaded, I think it was a virus checker) had problems until
> that IPX/SPX thing was set.
>
> Tim
> --
> Tim Mooney mooney AT dogbert.cc.ndsu.NoDak DOT
> edu
> Information Technology Services (701) 231-1076 (Voice)
> Room 242-J6, IACC Building (701) 231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
> --
> 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
