General discussion

Locked

Slow logins

By Tim.Doyle ·
I have a Netware 5.1 sp7 server and a Windows 2003 AD domain. Some windows XP Pro (SP1a) PC's with various versions of the Netware client (4.83 and newer) experience extremely long login times in the morning. I have found a few Novell TIDs that have randomly been of use, but no silver bullet yet. Thus far I have:

- Remove and reinstall client software of all versions.
- Set default protocol to IPX instead of IP (also tried the reverse).
- Reinstall client and removed NMAS option.
- Disable NMAS in advanced login page.
- Add preferred server name to general properties page.

Thus far, some machines are ok, others continue to have this issue. It doesn't seem to be the user object, but I have no objection to blowing it away and trying to re-create it. If I have the user login workstation only they can then use the client software to login to NDS from their desktop...this works perfectly every time.

I was convinced that the issue was the newer version of the client, but after backdating it to 4.83 and it still happens I'm no convinced of this.

This is a huge problem for me because the two people who are getting the worst of this are my boss and another senior VP...so this is making me look like an idiot. Lots of points for a silver bullet answer.

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by pierrejamme In reply to Slow logins

Setting up "Scoped SLP", Pure IP with NW6.0SP5, and client 9.92 with all the patches has worked great for me.
You do not have that option as you don't have Pure IP. You might try Scoped at:
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10059981.htm
Or unscoped at:
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10060296.htm

I would keep IPX also until you move to NW6.x
good Luck,
Peter

Collapse -

by pierrejamme In reply to

Another thing that will slow login is MalWare overload. have you cleaned lately?

If you are unfamiliar with spyware/Malware, check out the articles at:
http://www.pcmag.com/article2/0,4149,1522416,00.asp
http://www.pcmag.com/article2/0,4149,1523357,00.asp

If you have XP or Millenium, it has a System Restore:
You need to disable systen restore before removals tools will work.

Turn off System Restore:

Click Start > right-click My Computer, and then click Properties.
Click the System Restore tab.
Select the "Turn off System Restore" check box and then click OK.
Click Yes when you receive the prompt to the turn off System Restore.

When you reboot, the system restore won't replace the automatically backed up file and reinfect you.
For the Spyware/Malware the two best Free scanners are AdAware SE at:
http://www.lavasoftusa.com/
And Spybot Search & Destroy version 1.3 at:
http://www.safer-networking.org/index.php?page=download
After Installing each check for updates before proceeding. Both have several cool tricks, Adaware has a custom search that can search your Hosts file and your archived files as well. SPpybot S&D has an new program called Teatime that doesn't install by default you have to check the box when you are installing. SPybot S&D also has an Immunization program.

Another excellent program is SpySweeper from www.webroot.com, it allows for one update and then you need to purchase to get anymore updates. It will find a lot that the two free one didn't.

I also use PestPatrol which also costs money. It is located at:
http://www.pestpatrol.com/ and they have a free pest scan if you can stay on the Internet long enough.
Turn on System Restore Back on
Clear the Turn off System Restore check box (or the Turn off System Restore on all drives check box), and then click OK.
Reduce the size of the System Restore to 3% or less. You don't need the 12% default.

Collapse -

by BudTheGrey In reply to Slow logins

If you didn't already, un-install & re-install the client, but choose a CUSTOM install. This lets you pick either IPX or IP as the protocol. The key is to *not* install support for both at the client level. This is a known performance killer.

SLP is an IP-only tool, so there's no need to set up SLP scopes & etc if you use IPX as the protocol of choice..

Collapse -

by Kinetechs In reply to Slow logins

Have you tried experimenting with the bindings? Open your Network Connections folder and choose Advanced on the menu. Select Advanced Settings. Try different binding orders for the protocols, clients, and services. It'll take some trial and error but hopefully a better combo will work for you.

Cheers!
~Sean

Collapse -

by theotherkiwi In reply to Slow logins
Collapse -

by mrjay67 In reply to Slow logins

I would suggest changing your IPX frame type from auto detect to 802.3 or whatever your network supports. In most enviroments i've seen it usually is 802.3. Just check under your IPX protocol settings in network properties for your network connection. This solves it every time in our enviroment. This appears to be related to the way switches are configured but may be caused by other physical connection issues. Anyway for whatever reason there seems to be issues when auto-negotiating the frame type in certain configurations and WinXP is really bad in this situation.

HTH

Jason
GPISD

Collapse -

by ErickL In reply to Slow logins

We had a similar problem with NW5.1 SP6 and an NT4 Domain. Running a DSTrace to monitor communication during logon attempts showed that there was a problem in NDS relating to the NT objects. We were running a Novell NT integration product (Account Management, I believe it was at the time - it was the iteration between NDS4NT and DirXML.) Some of the NT objects were corrupted in NDS. Oddly enough, DSRepair never found/fixed the problem and Novell was never able to recommend a fix that worked. Uninstalling NT integration, repairing NDS and reinstalling NT integration fixed the problem. Boom, fast login restored.

Hope this helps,
Erick

Collapse -

by Why Me Worry? In reply to Slow logins

I would go pure IP if I were you. Remove IPX from the server and workstations and setup SLP on the server, make it a DA, and point your Windows XP client to the server's IP address. Also, the 4.83 client has issues with it, so I would recomment going to 4.9x client. I have seen the 4.83 client authenticate users across slow WAN links when a local NDS replica was available. We caught this when we ran a Sniffer LAN trace and found it coming from the workstation. It was definitely the client.

Collapse -

by Tim.Doyle In reply to

Poster rated this answer.

Collapse -

by Tim.Doyle In reply to Slow logins

Sadly I cannot remove IPX and go straight IP since Netware 5.x doesn't support NDS replication across IP. I have more than one server so IPX has to stay.

I just installed the newest version of the client software from Novell and it seems to have at least temporarily corrected my issue.

My thanks to all who replied.

Back to Networks Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums