Anonymous_User Absent Member.
Absent Member.
2136 views

Right-Click Lag

I'm not sure which forum would best handle this query, so I'll toss it out
here and see what happens...

My network services close to 300 users and for the most part, everything
works fine. We have the latest version of the client installed on almost
all the machines, although this doesn't seem to be client version specific.
And while it's not a problem, per se, it's a definite annoyance.

It has to do with the right-click action in Windows.

With the client installed, logged into Netware, you right-click an icon [on
the Desktop, in the Quick Launch bar, doesn't matter], the station seems to
freeze for a number of seconds before displaying the menu options.

With the client installed, logged into Windows *only*, you right-click an
icon and there is no lag... the menu pops up immediately.

What is the client doing?? I haven't gone digging through every single
client option [yet], I was hoping that someone else was equally as annoyed
by this and knows of a solution.

As always, I thank you all for your help and suggestions.

NormC
Labels (2)
0 Likes
8 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Right-Click Lag


> What is the client doing?? I haven't gone digging through every single
> client option [yet], I was hoping that someone else was equally as annoyed
> by this and knows of a solution.
>


NormC,

Someone was:

/quote
From: "ljb" <ljb220@mindspring.remove.this.com>
Subject: Fix for slow right-click shortcut context menus, Win2k+SP4+Netware
Date: 02 October 2003 03:51


[Also posted to microsoft.public.win2000.general]

(OK, it's not a fix; more of a crude hack which works around the problem.
It's had minimal testing, works for me, use at your own risk, etc. Hope it
helps somebody out there.)

Description of the problem: Right-click over any shortcut (or quick-launch
toolbar icon). It takes about 10-25 seconds before the context menu pops
up. Try again, on the same or another shortcut, and it's fast. Wait about
5 minutes, and it is slow again. It happens on Windows 2000 SP4, but not
on Windows 2000 SP3. It happens with Netware Client 4.83, or 4.83+sp2, or
4.83+sp2+"update e". If you remove the Netware Client, it goes away.

What seems to be happening, based on Ethereal traces, is that the Netware
Client is trying to resolve the short-cut target's drive letter (usually
"C") as a network name. In my case, it tries IPX SAP, SLP, and Bindery,
making multiple requests (even though it gets negative replies, but that's
another problem) until it finally gives up.

My fix is based on Novell TID # 10065560 item 6, which tells how to
pre-load the Bad Server Name Cache with permanent entries for servers you
don't want to try to resolve. But I'm abusing this to preload the cache
with the letters A through Z. (I hope you don't have any servers on your
network with these names.) This appears to work around the bizarre behavior
of NWC 4.83 with Win2K SP4 trying to resolve drive letters on short-cuts as
if they were network names.

If you want to try the fix, import the .reg file below, or do it
manually as follows: Using regedt32, create a REG_MULTI_SZ value
called "BadServer" under the key:
HKLM\SYSTEM\CurrentControlSet\Services\NetwareWorkstation\Parameters
The data is the letters A through Z, each on a separate line.
Note: The change does not take effect until you reboot.

======== start badserver.reg ==========
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetwareWorkstation\Parameters]
"BadServer"=hex(7):41,00,00,00,42,00,00,00,43,00,00,00,44,00,00,00,45,00,00,00,\
46,00,00,00,47,00,00,00,48,00,00,00,49,00,00,00,4a,00,00,00,4b,00,00,00,4c,\
00,00,00,4d,00,00,00,4e,00,00,00,4f,00,00,00,50,00,00,00,51,00,00,00,52,00,\
00,00,53,00,00,00,54,00,00,00,55,00,00,00,56,00,00,00,57,00,00,00,58,00,00,\
00,59,00,00,00,5a,00,00,00,00,00
======== end badserver.reg ==========

/unquote

On the bottom of this TID is an explanation on the BadServer key:
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10065560.htm

Have fun 🙂

Peter


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Right-Click Lag

Cool! It works!! 🙂

It's still a *tiny* bit laggy, maybe about a half-second versus
instantaneous, but it's much much better than the thumb-twiddling pause I
used to endure.

Many thanks!

NormC

>
> > What is the client doing?? I haven't gone digging through every single
> > client option [yet], I was hoping that someone else was equally as annoyed
> > by this and knows of a solution.
> >

>
> NormC,
>
> Someone was:
>
> /quote
> From: "ljb" <ljb220@mindspring.remove.this.com>
> Subject: Fix for slow right-click shortcut context menus, Win2k+SP4+Netware
> Date: 02 October 2003 03:51


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Right-Click Lag

Credits to the original oster 🙂

Peter


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Right-Click Lag

Peter vdW:

> It happens on Windows 2000 SP4, but not
> on Windows 2000 SP3. It happens with Netware Client 4.83, or 4.83+sp2, or
> 4.83+sp2+"update e". If you remove the Netware Client, it goes away.
>


FWIW, it also happens on Windows XP with Client32 4.91 and the same fix
works 🙂

Joe Moore
Novell Support Forums SysOp
http://just.fdisk-it.com
http://www.caledonia.net/jmdns.html
http://www.caledonia.net/nesadmin.html
http://www.caledonia.net/jmttb.html


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Right-Click Lag

Hi Joe,

Good to know. How about making this a TID or CoolTip ?

Peter

> FWIW, it also happens on Windows XP with Client32 4.91 and the same fix
> works 🙂
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Right-Click Lag

Peter vdW:

> How about making this a TID
>


I would love to, but Primus is not cooperating with me today 😞

Joe Moore
Novell Support Forums SysOp
http://just.fdisk-it.com
http://www.caledonia.net/jmdns.html
http://www.caledonia.net/nesadmin.html
http://www.caledonia.net/jmttb.html


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Right-Click Lag

> I would love to, but Primus is not cooperating with me today 😞
>


Primus as in King of Troy ? No wonder he is not cooperating..

Peter


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Right-Click Lag

Peter vdW:

> Primus as in King of Troy ?
>


LOL - that is the web app that Novell uses to create TIDs 🙂

Joe Moore
Novell Support Forums SysOp
http://just.fdisk-it.com
http://www.caledonia.net/jmdns.html
http://www.caledonia.net/nesadmin.html
http://www.caledonia.net/jmttb.html


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.