We had similar perfomance problems with initial authentication while 802.1-Authentication was activated in the client but not supported by our Netware-Servers.

Greetings

Olaf

Merucry32 running in NDS mode, i.e. Windows Server with Novell Client.

On Server 2003, this runs as expected.

On Server 2008 (and 2008 R2), authentication performance is abysmal. If Mercury has several logged in imap users, new logins start piling up and remain as "[Not-logged-in]" for very long (30 seconds or several minutes!). Of course, once Mercury comes around to authenticate the user, the respective imap client has long given up and produced a timeout error. The server effectively ceases to work from the clients point of view.

Is this a known problem with Windows Server 2008 and up? Or maybe a problem with Novell Client 2 (this is a re-write, very different from the old Novell Client for Window XP and Server 2003)?

Greetings

Markus

P.S.: I posted a similar question a while ago, but now we could pin-point our problems to Server 2008.

Maybe you have activated 802.1-Authentication in the Novell Client? In standard installation it is activated in the Systemprofile of the client.

 Greetings

   Olaf

How would 802.1-Authentication influence performance? As far as I know (I'm no 802.1 expert), this is only overhead for initial network access, not for every tcp connection.

Greetings

Markus