We encountered something similar when a second network card was added to the client
system.

Another variation has to do with fully qualified or non-qualified node names in the
net user and net alias files. We have connectivity from one system fully qualified
and from another not qualified at all.

Feel free to call me.

========================
Leonard S. Berkowitz
mailto:[log in to unmask]
phone: (617) 972-9400 ext. 3250
fax:   (617) 923-5555








[log in to unmask] on 05/26/99 12:45:46 PM

Please respond to [log in to unmask]

To:   [log in to unmask]
cc:    (bcc: Leonard Berkowitz/THP)
Subject:  [HP3000-L] Allbase/NET - unable tpo access remote database




Hi there!

I'm having problems trying to connect to a remote database,using
Allbase/NET. I have constructed the alias file on the client system (the
node is HP1421), and the user file on the server system (node is HP1037),
and I have the listener job (ARPA listener) running.

When i try to connect, the connectin request is rejected, with an error:

No matching profile found in the NETUsers file.  (DBERR 26002)

When I look at the log file for the listener process, it seems that rather
than seeing HP1421 as the source node, it is seeing HP1421DBKL1

Has anybody else seen anything like this? I'm at a loss to figure out how
to correct it.


TIA

Tony
PS Please reply to me as well as to the list, because this is NOT my usual
address!