Hello, I just added a Secondary Domain Controller into our Windows 2000 Network environment. After doing this, the weirdest things started to happen.
Now whenever I add a new user to the Domain, any mailbox related stuff does not work properly. For example, after adding the user, and then setting up their POP3 account on the outside, it won't authenticate them. It keeps asking for the password again and again. BUT, if I check off "logon using Secure Password Authentication" inside their Outlook POP3 client, then it allows them to POP their mail. We never had to do this before, and none of the existing accounts have this setting enabled. It seems as if there are some communication issues happening - regarding the Exchange Server and the Domain Controller. Also, if you try to send mail to the newly created user's address, the server accepts the message okay, but it never shows up in the user's mailbox. Then a day or two later, the message will show up in the senders mailbox as Undeliverable. It just does not want to mate up any Exchange related information, to the basic user information in Active Directory. It's as if, the user is in Active Directory, but some portions of it possibly get written to the Secondary Domain Controller, and other portions get written to the Primary Domain Controller. I know it sounds dumb, but it's almost if the Exchange server is aware of the user, but just can't put all the pieces of the puzzle together regarding this persons SMTP Address and their password - yet, it's plain as day when you look at Active Directory Users and Computers. Any users that already existed before the new server was installed are totally insulated from this weirdness. So what I did, was uninstalled the newly created Secondary Domain Controller - and converted that box back into a Standalone Server. And now, everything works again. I can add users until I am blue in the face, and I can POP their mail normally, etc. What the heck is going on here? Does anybody have any ideas as to what the problem may be? I NEED to have a Secondary Domain Controller - because if my first one blows up, then all hell will break loose. I feel very naked without a Secondary Domain Controller, and I need to put this back online soon - but I can't have my Exchange Server break because of it. My environment is all Windows 2000 Server, SP3 - which is standard on every box on the network, and my Exchange Box is Exchange 2000 with Service Pack 3. I would kill for any ideas right now... Thanks, Mike _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
