<div>
It sounds more like a digital sender issue than an LDAP issue. &nbsp;They're authenticating sufficiently to scan one doc, after all. &nbsp;Not that it isn't a problem, but may not be LDAP related per-se.<br />
<br />
It may have something to do with licensing, but that wouldn't necessarily be an LDAP issue. &nbsp;When the Digital Sender sends files to the users' folder, is it connecting directly to NetWare as a client? &nbsp; Or is it sending a message of some sort through a fax or messaging server, which is what I thought Digital Senders did?<br />
<br />
If it's connecting to NetWare as a client, how is it connecting, through a Novell client, or through NFAP/CIFS, or through NetStorage, or some other method?<br />
<br />
LDAP authentication isn't the same thing as connecting to a server. &nbsp;Unless you're using NetStorage or iFolder, it wouldn't be &quot;logging you in&quot; - it might only serve as a repository of user information that another program can use as an authentication vehicle.<br />
<br />
Do you have sufficient licenses for everyone to be logged in? &nbsp;If so, are you limiting connections? &nbsp;How many servers do you have? &nbsp;Have you verified that your user licenses are not associated to any specific servers? &nbsp;They should not be. &nbsp;<br />
<br />
It's not unheard of that a user might take more than one license if their licensed connections are different modes. &nbsp;If they're logged in via the Novell Client32 on their desktop and then walk over to the D.S. and log in via NFAP/CIFS or NetStorage, or logs into a Mac and mounts a server volume using AFP, that second connection might actually take a second license, which sucks, but I haven't dug into whether it can be &quot;fixed.&quot; &nbsp;What I do is, once in a while, I'll check to see who has multiple licenses associated (using a reporting tool like DSReport by Wolfgang Schreiber) and unassociate all but the most current one, to make sure I don't hit a ceiling.<br />

</div>


<div>
Yes we have enough licenses for everyone to be logged in.<br />
As I understtod it, it needs ldap to connect to the netware network.<br />
The user logs into the DS with there network id and password. There is no cifs or other method that it is connecting with.<br />
There is no fax or messaging server either. The DS is simply a high end network scanner.<br />
Once the user is logged in they can only scan to folders they have access to.<br />
So I am thinking it logs in as a client from the DS.<br />
The users have no limits for concurrent connections.<br />
I have talked with HP twice and, of coarse, they don't have much help to offer<br />
for netware. All they say is that it will work with netware, but your pretty much left on your own to figure it out. <br />
&nbsp;
</div>


<div>
Does the DS PC have the Novell Client32 on it, or the crapware(tm) client for NetWare that comes with Windows, or what?<br />
<br />
It has to have some sort of client to get access to NetWare volumes.<br />

</div>


<div>
There is no DS pc. The DS is a stand alone unit.<br />

</div>


<div>
Then what is the DS service you mentioned that's running on an XP box used for, and why would it lock out access until that service is restarted? &nbsp;Does that run on everyone's PC? &nbsp;<br />
<br />
What is the model number of the device, so I can look up the documentation online?<br />

</div>


<div>
It's a digital sender 9250c.<br />
The ds service runs on one computer and is used to configure it.<br />
The actual logging in is done on the DS itself.<br />
The service is what tells it what ldap server to use and is also used to set up the pre defined folders.<br />
here is a link to the manual: <a href="http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c00859831/c00859831.pdf" rel="ugc nofollow">http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c00859831/c00859831.pdf</a>
</div>


<div>
<div class="content wysiwyg-content">
Network: Netware 6.5 <br />
We have a HP digital sender that connects to our Novell network using ldap.<br />
The user logs into the device and then can send files to thier folder.<br />
Recently, what has been happeneing is the user will login and scan thier first doc then the DS will as if you would like to remain signed in. The user selects yes because they have more to scan but the DS logs them out with a auth timeout error and after that noone can login until I restart the DS service running on a Windows XP box.<br />
I have found if the user selects no and then logs in again there is no problem.<br />
At the time this was happening we had 1 license available. This led me to believe that when the user selects Yes to remain loged login<br />
that it actually creates another licesed connection. <br />
Am I correct? is there a ldap setting that I'm missing?<br />
Any help would be greatly appreciated.<br />

</div>
</div>


Network: Netware 6.5 
We have a HP digital sender that connects to our Novell network using ldap.
The user logs into the device and then can send files to thier folder.
Recently, what has been happeneing is the user will login and scan thier first doc then the DS will as if you would like to remain signed in. The user selects yes because they have more to scan but the DS logs them out with a auth timeout error and after that noone can login until I restart the DS service running on a Windows XP box.
I have found if the user selects no and then logs in again there is no problem.
At the time this was happening we had 1 license available. This led me to believe that when the user selects Yes to remain loged login
that it actually creates another licesed connection. 
Am I correct? is there a ldap setting that I'm missing?
Any help would be greatly appreciated.


Ldap connections. How do they work?

Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.

Databases

NetWare is a computer network operating system developed by Novell, Inc. It initially used cooperative multitasking to run various services on a personal computer, using the Internetwork Packet Exchange (IPX) network protocol. It is hardware-independent, running on any suitable Intel-based PC compatible system, and a wide range of network cards. Products inclue NetWare Directory Services (NDS), a global directory service similar to Microsoft's Active Directory; GroupWise, an email system; ZENworks, an application configuration suite; and BorderManager, a security product. Open Enterprise Server, the current iteration, runs on a SUSE Linux Enterprise Server.