Hi,I want to try and keep this as brief and still provide enough info to get a response. My site runs a Novell server with novell client 4.83 on xp and 2000. 3.32 client for the 98 o/s machines. A particular user takes 12 minutes on her machine from login until the scripting screen closes out. On her old 98 box this doesn't happen (or any 98 box in the school, for that matter). If I login to her machine it does not happen to me, I get right in. We tried logging her in to a 2000 box. Same thing, a hang for about the same time. So its not a network switch or nic, as by changing machines, thats eliminated. I have removed her from DS and recreated.. no change... However, we have started to notice other users are starting to encounter this hang on only the new xp machines. BTW the xp boxes are HP d325 business desktops. I am really at a loss to figure it out, as well as the main tech who is responsible for the food service manager whom is having the 12 minute hang. He actually did this: cloned her drive and stuck in another machine at our admin center, and it worked fine. The exact same machine as hers, yet hers wont work right (at least for her user, again, I can get right in without the delay). Any thoughts would be helpful. Thanks, Steve Collier County School District Naples, Florida

Login Speed issues can be due to a variety of causes. If it is affecting XP only at present, then I would suspect... 1 Virus activity. XP is susceptable to Blaster, Lovsan, Nachi all of which produce network sluggishness or inability to connect to The Internet or slow logins. Try downloading the latest Stinger.exe version and run it on an XP workstation. Ensure that your XP is at SP1 and that you have patched for Blaster vulnerabilty. 2 Check protocols. Do you use SLP, if so ensure agents are available and other protocols are not used. Delete any protocols not actually needed. 3 Mutiple clients Do you have the MS client ticked for the network connections you use. If so, is it necessary for your Novell environment? 4 If you use Zenworks, limit the number of apps associated with the user - eliminate duplication and unnecessary apps. 5 Analyse your tree. Reduce the distance searched for policies and apps. Associate policies and apps with organisational units rather than groups. 6 Virus Checkers. Make sure that these are not holding up login files. Use exceptions in McAfee to allow spool files and essential login traffic. 7 MS Profile activity Is the user roaming and updating a local profile? If so, there may be a lot of activity associated there. Geoff Taylor