netware connection still active after logging off from win2003 server

[llap444]

When I login on my windows 2003 server (at the actual machine), it makes a connection to our netware 3.12 server (yes, it still is working). This works fine. What doesn't work fine is when I logoff the windows server -- I still show a connection to the netware server (as viewed on connection info from the netware server monitor - or from another pc running fconsole)

When I login again on the windows server, I get yet another netware connection -- this happens until I get to our netware limit of 25 licensed users - then I get errors saying I have exceeded the sessions for the server. Only when I SHUTDOWN the windows server, do the "extra" connections go away.

I can also remove the connections manually using fconsole and deleting the connections one by one, but this is obviously not what I need.

My original concern was that I will be using Remote Desktop Connection on a remoted PC to the win2003 server - thus being able to access the netware files. But, was building a list of connections every time the user logged off. This problem was solved on the Win2003 server by modifying terminal services session "end session" setting after disconnecting. So, this has almost solved my problem.

However, I have not been able to find a command line command or a gui setting that similarly modifies the ability to get rid of the persistent connection to netware after logging off at the actual win2003 server. I can manually remove the connections to netware after I'm done doing administrative tasks on the win2003 server, but I'm guessing there is a more automated method available. If I knew what command I could issue that actually breaks the connection, I could include it in a script. But even that seems to be an unnecessary workaround. Somewhere there's gotta be a checkbox or something.

anybody else with similar problem or suggestions???
john

 

[JockMullin]

Hi llap444

It sounds like you are logging off the Win server but not the Novell server. What client are you using?

Have you tried using the LOGOUT Novell command? That should do it, but I have no way of testing it myself.

On the Novell server, the default timeout before terminating an inactive connection is quite long (over an hour). This can be modified with set commands on the server. However my suspicion is the client you are using is not terminating the Novell connection anyway. If you are using the Microsoft client that is quite possibly the case especially if the connection still shows as active (has the login id).

Another thing - you can limit the number of concurrent connections for the user. I think the default is 3.

Jock

 

[technome]

John

Was that Cro-Magnon?

Try NLICLEAR.
e.g. load nliclear poll=600 (or lower)
This will clear not logged in connections after 5 minutes.

http://www.tek-tips.com/viewthread.cfm?SQID=651824&SPID=56&newpid=56&page=4

Paul Meiners

 

[JockMullin]

Hi, Paul

Maybe you're right. I read the title of John's message and assumed 'active connection' meant the connections were still active. Too literal, perhaps, but Cro-Magnon?

My understanding is NLICLEAR clears only NOT-LOGGED-IN connections and I thought the post was dealing with being unable to log out.

Sorry if my response was inappropriate.

Jock

 

[technome]

Cro-Magnon.. I was dealing with John on another site, inside joke, in reference to the age of 3.12

John has tried a number of things, this was just another possibility. He logs out but the connections are not cleared.

Paul Meiners

 

[llap444]

Thanks Paul, the NLICLEAR seems to be the trick. I first tried to simply issue the novell 'logout' command from the win2003 server -- but that does not 'clear' the novell connection.

Loading NLICLEAR appears to work OK. I really didn't want to have to tweak my dinosaur at all -- AND I still think there should be another solution that only involves the win2003 server side -- leaving novell completely untouched. I say this because somehow, win2003 server terminal services manages to release the novell connection when it finishes -- I just don't know what it's magic command is that makes it work, when logging in directly from the win2003 keyboard is NOT able to clear the connection.

So, I would still be interested if anybody has any additional ideas.
For those few of us who still wander in jurassic park, we are greatly appreciative of the 'tour guides' like Paul, that stay ready at their posts, when we get stuck in the muck.
Thanks again.
John