EXTREME SLOW PERFORMANCE ON WINDOWS Y2K WITH NETWARE CLIENT AS PRIMARY LOG ON

  • Thread starter Thread starter Lily LAPD
  • Start date Start date
L

Lily LAPD

Background:
LAPD has an enterprise NOVELL LAN and a few small
isolated private LANs that runs Windows 2000 servers. A
special unit wants to have access to both NOVELL and
Windows 2000 LANs from the same PC using Windows 2000. The
Windows 2000 LAN is configured in a Workgroup
configuration.

Problem:
Logging on to NOVELL LAN works fine, but logging on
to Windows 2000 workgroup LAN works EXTREMELY slow or even
hangs.
And when NOVELL Client is removed, the PC works fine.

Please help.
Any recommendations and tips will be greatly appreciated.

Lily Wren
LAPD
(e-mail address removed)
 
START with this checklist, make sure you do EVERYTHING on it, then report
back

what kind of packet sniffing/troubleshooting/etc have you done so far?

make sure you are using the latest nwclient & patches
http://support.novell.com/filefinder, http://download.novell.com
Make sure you have rolled it out via ACU & disabled NMAS if you do not need
it.

run through http://www.ithowto.com/novell/clientspeed.htm

make sure DS is clean & healthy

make sure you have the server updated to the latest patches & oplocks level1
& 2 are set correct -
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10085899.htm youll
want to make sure server & workstation are configured.

SLP is setup properly on the server, & distributed properly to workstations
via dhcp (yes, you do want to set this up) - service location protocol,
useful even in a small 5 person office all the way up to the largest
companies around. (how many users do you have anyways?)
http://www.srvloc.org/,
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10014570.htm,
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10024591.htm. You
set this up, then push the options out via dhcp.

Internal DNS setup properly (yes, you do want to set this up) - you can use
sys:public\dnsdhcp console (run the setup from there) or iManager for dns (&
dhcp).

DHCP - you want this setup internally, because you can push out dhcp options
to clients that your WG router cannot, such as SLP, & static ip addressing
is pointless with reserved dhcp addresses.

latest drivers for everything (nic/chipset/controller/etc)

that speed/duplex on *everything* is hardset, & hardset correctly

check cables, make sure everything is cat5e certified, not using flat
cables/cat3/etc (ive seen it in a lot of places)

purge all volumes & turn off compression - there are many utilities out
there that allow you to do automated purges, check out the links section
under www.abend.org

make sure there is more than 10% free space on EVERY volume

make sure bios/firmware to everything (server/raid
cards/switches/workstations/etc) up to date

Microsoft Office slow - Other things that may make it
slow is office itself isnt up to date (you do have enterprise version & roll
it out/update via AIP right?), and drive mappings to slow remote servers or
servers that no longer exist. If you are using nwclient49sp1, make sure you
rolled it out via ACU with nmas disabled (www.appdeploy.com has ACU info).


--
Thanks,
Keith V. Klenke
--------------------------------------------------
Hey everyone,
I just wanted to let you know there is a site that may be of some use. A
lot of people who work with Novell products, and are VERY good with
implementations and troubleshooting, frequent the site. You can find it at:
http://www.abend.org
 
I had a similar problem... this might help you.

When using the installed Novell client, nwgina.dll is the
primary gina when logging on. It does not, or does not
gracefully pass the user info on the microsoft client to
subsequently logon to a MS domain, and may work similarly
in a workgroup setting. To get the MS client to be the
primary logon to the PC go to
HLKM\software\microsoft\windows nt\currentversion\winlogon
and look for the key Gina.DLL This key is usually
created by the Novell client install. change the value of
the key from nwgina.dll (or other values, I've seen a few)
to MSGINA.DLL. Try it. Good luck. It's working well for
me.
 
With this method don't you get promted twice for logon?? the initial logon
will be your Windows logon...then your Novell logon?
I had a similar problem... this might help you.

When using the installed Novell client, nwgina.dll is the
primary gina when logging on. It does not, or does not
gracefully pass the user info on the microsoft client to
subsequently logon to a MS domain, and may work similarly
in a workgroup setting. To get the MS client to be the
primary logon to the PC go to
HLKM\software\microsoft\windows nt\currentversion\winlogon
and look for the key Gina.DLL This key is usually
created by the Novell client install. change the value of
the key from nwgina.dll (or other values, I've seen a few)
to MSGINA.DLL. Try it. Good luck. It's working well for
me.
 
Back
Top