|
I would do the following:
1) Make a copy of you login script, give it a new name.
2) Put tons of tracers messages in it, like this:
; code
?"Now mapping drive... press any...." get$
; code
?"Now doing something else ... press any...." get$
; code
3) Promote it to NETLOGON and assign this script to a test user.
4) Login and take notes ... your trying to pinpoint in your script, what is taking all time.
5) Refine your tracers and re-promote - keep doing this until you pinpoint the problem.
6) Check your application eventlog on workstation for Kixtart messages.
| 
