user connection/not connected

[jlfiller]

I have a user who is unable to log on because the message comes up: you are logged in to too many stations (limit is 2)

When I look in the Connection screen in the Monitor console, the user is not connected to either server.
But when I do an nlist user=jonesj /a, I see that he is connected to a certain Ethernet address.

I ran a DSREPAIR, but still see that connection under nlist. I also see the connection under NetAdmin in the user's details, Network Address in the Environment tab.

Any suggestions welcome! JL Filler,Wilton Public Schools, Wilton CT

 

[jlfiller]

More info -- I found the machine that the user was sorta logged on to -- it wasn't even turned on. I booted it and upgraded the client to client32 3.3 and logged on as the user in question, then logged off. Still listed in nlist and in netadmin as being on this computer. Aaaaargh!! JL Filler,Wilton Public Schools, Wilton CT

 

[yvfwc]

Is the user authenticating to another server somewhere? When logged in what does the NetWare Connections show?

Cheers,
Mark ;-)

 

[TheLad]

Try removing the connections limit, getting the user to log on, then putting the connections limit back on. This will force NDS to drop the inactive connection and mean the user can log on next time ok. "It's true, its damn true!"

 

[jlfiller]

Yes, the user was authenticating to another server, but neither showed a connection on the monitor console for this user. I even checked all the other servers. I changed the user's password and signed on to the SAME station again with the user's account, then logged out. I thought that would force the connection to be deleted. But no.

I ended up deleting the user's account, then recreating an account with the same name and attaching the user's former home directory to the newly created account. That finally cleared the connection and it didn't come back.

But it's still weird! Thanks for your help/suggestions. JL Filler,Wilton Public Schools, Wilton CT

 

[jlfiller]

Well, it happened again with another student. I saw NO connections in Monitor on either server for this user, but when I did an
nlist user=stuname /a
I saw 2 (!!) addresses listed.
User connection limit is set to 2, as I think it should be.
I think the workstations in question might have Client32 rel 2.11 or so. But we have some problems with Client32 rel 3.3 sometimes, so I don't really want to upgrade unless it's absolutely necessary.

The only way out of it is to delete the user and recreate. Nothing else seems to work. But that's a pain!

Any clues about how/why this might happen?
JL Filler,Wilton Public Schools, Wilton CT

 

[TheLad]

My suggestion above definately works. Increase the concurrent connections by a few, get the user to log in, decrease concurrent connections back to normal level.

Much easier than deleting and recreating the user object! -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[jlfiller]

Unfortunately, that does not fix the problem. The user can log in, but those 'phantom' connections are still there. The students are not in today (winter break) and there are no students logged in, according to the console. But when I do
nlist user /a
I see 59 students logged in. If I look in NetAdmin, I see them in Environment.

But they aren't really logged in and most of those machines are not even turned on.

I tried your suggestion, TheLad, but it didn't force those phantom connections to clear. They remained. JL Filler,Wilton Public Schools, Wilton CT

 

[TheLad]

Usually, the phantom connections will disappear after a timeout period of (usually) 15 minutes.

What Service Pack are you running? What version of Novell Client are you running?

Try looking at the following TIDs also:

http://support.novell.com/cgi-bin/search/searchtid.cgi?/2912951.htm

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10058318.htm

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[jlfiller]

I had already seen those two TID's, but I think I'll take another look at the first one.

I am running Service Pack 9 on Netware 4.11
I have some machines with Client 32 version 2.11 and some with Client32 v3.33

These connections hang around for weeks. I even re-booted the server and they came back.

I have just finished deleting the 59 problem users and re-creating them. Pain, but it will fix the problem. For now.

I think I'll try running
"load dsrepair -n1"
every night for a while with the cron NLM
and see if the problem comes back. JL Filler,Wilton Public Schools, Wilton CT