NWDSLogin Failure - 34948 (0x884) / Can I set preferred
server?

I've got one problem and a possible solution.  We have a piece of 
software installed on a client machine that uses the NWDSLogin method to 
log us in to eDirectory.  We have started receiving the 34948 error (no 
changes to workstation or system as far as we know of and the client has 
a very strong change control system) and can no longer login.  When the 
client tries to login on the workstation if they don't provide a server 
name they receive a cannot find tree error but as soon as they provide 
the server to use they login fine.  

As a short term solution I'm trying to find out if there is a way for us 
to force the preferred server on the login attempt.  I know I can use 
NWGetPreferredConnName to get this information but I'm looking for a set 

Shane wrote:
> I've got one problem and a possible solution.  We have a piece of 
> software installed on a client machine that uses the NWDSLogin method to 
> log us in to eDirectory.  We have started receiving the 34948 error (no 
> changes to workstation or system as far as we know of and the client has 
> a very strong change control system) and can no longer login.  When the 
> client tries to login on the workstation if they don't provide a server 
> name they receive a cannot find tree error but as soon as they provide 
> the server to use they login fine.  

Try taking a look at the network traffic from any such host both when 
the client login is attempted in a scenario in which it will fail (tree 
specified but no server as I understand it). Try capturing traffic when 
the other software uses NWDSLogin. It sounds like the selected name 
resolution protocol(s) for the client are no longer functioning. I can't 
remember the defaul order but I think it is SLP first then DNS and DHCP 
is in there somewhere I believe. Looking at traffic you should see one 
or more of the methods execute but receive no response. FWIW, that makes 
it a support question rather than a developer one.

> As a short term solution I'm trying to find out if there is a way for us 
> to force the preferred server on the login attempt.  I know I can use 
> NWGetPreferredConnName to get this information but I'm looking for a set 
> method.

You wouldn't be able to use it before the client logged in so it 
wouldn't do anything to the fundamental nature of the problem. You 
appear to appreciate it would be a workaround but it may be better to 
resolve the cause.

-- 
Regards,
David.

***************
David A. Mair

Shane, Devnet SysOp 57 wrote:

> I've got one problem and a possible solution.  We have a piece of
> software installed on a client machine that uses the NWDSLogin method to
> log us in to eDirectory.  We have started receiving the 34948 error (no
> changes to workstation or system as far as we know of and the client has
> a very strong change control system) and can no longer login.  When the
> client tries to login on the workstation if they don't provide a server
> name they receive a cannot find tree error but as soon as they provide
> the server to use they login fine.
>
> As a short term solution I'm trying to find out if there is a way for us
> to force the preferred server on the login attempt.  I know I can use
> NWGetPreferredConnName to get this information but I'm looking for a set
> method.

You can set the preferred server using NWCCSetPrefServerName but as David
says, I doubt that will help.

Try to establish a connection to your preferred server using
NWCCOpenConnByName before calling NWDSLogin. If SLP is not set up correctly,
some methods of locating a server fail, but whoever wrote NWCCOpenConnByName
did a good job, and if the server is out there and communicating, it seems
to find it.

John
DevServ SysOp 24

Hello, John.

Interesting.  Thanks for the information.  We were able to solve the 
clients issue by having the clients  Netware person who had been away at 
the time look at the Netware client settings when they got back.  They 
realized that a bunch of them were set improperly.

Regards,

Shane

In article <422B714E.E521DEB6@jrbsoftware.com>, john@jrbsoftware.com 
says...
> 
> 
> Shane, Devnet SysOp 57 wrote:
> 
> > I've got one problem and a possible solution.  We have a piece of
> > software installed on a client machine that uses the NWDSLogin method
to
> > log us in to eDirectory.  We have started receiving the 34948 error
(no
> > changes to workstation or system as far as we know of and the client
has
> > a very strong change control system) and can no longer login.  When
the
> > client tries to login on the workstation if they don't provide a
server
> > name they receive a cannot find tree error but as soon as they
provide
> > the server to use they login fine.
> >
> > As a short term solution I'm trying to find out if there is a way for
us
> > to force the preferred server on the login attempt.  I know I can use
> > NWGetPreferredConnName to get this information but I'm looking for a
set
> > method.
> 
> You can set the preferred server using NWCCSetPrefServerName but as David
> says, I doubt that will help.
> 
> Try to establish a connection to your preferred server using
> NWCCOpenConnByName before calling NWDSLogin. If SLP is not set up
correctly,
> some methods of locating a server fail, but whoever wrote
NWCCOpenConnByName
> did a good job, and if the server is out there and communicating, it seems
> to find it.
> 
> John
> DevServ SysOp 24
>