General discussion

Locked

Outlook 2000 Startup Delay

By eric.fondriest ·
We recently installed MSX 2000 on a new server. Our previous MSX 5.5 server is no longer accessed by the user community. We also migrated our NT4 network to WIN2K running in native mode. We are noticing that workstations that have not joined the new W2K domain require increasing the Outlook 2000 timeout value so as not to receive "server not found or not available" error messages. We have also changed the remote clients that are still on the NT4 domain so that their Outlook 2000 client has the Logon network security setting set to "None". This seems to resolve the delay issues. My question is why does it take so long to present the remoter user still on the NT4 domain with the W2K authentication? Please advise.

Thanks.

This conversation is currently closed to new comments.

1 total post (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Outlook 2000 Startup Delay

by kmcniff In reply to Outlook 2000 Startup Dela ...

First thing a few questions need to be answered here to help diagnose thia problem.
1. When you installed WIN2K, did you upgrade an NT4 domain, or install a NEW AD Domain?
2. When you installed the Exchange 2K server, did you properly prepare the Forest and Domain?
3. Have you established a TRUST between the WIN2K and NT4 Domains?
4. What O/S are the client workstations running?
5. Do you have WINS installed for pre WIN2K Clients?
6. Are the pre-2K clients running the AD Client?

Answerthese questions, and I can help you get this up and running. Remember that AD and 2K are a very different beast from NT4, and there are many more considerations and problems with backward compatability. Mostly because Kerberos is used for authentication by default.

Back to Windows Forum
1 total post (Page 1 of 1)  

Related Discussions

Related Forums