New User Created in Active Directory, Can't Connect to Exchange 2003

[medens]

Hello,

I am experiencing a very frustrating issue right now where I create a new user in Active directory, as normal and when I go to set them up to communicate with our exchange server in Outlook 2003, it won't let me establish the connection. I go through Control Panel, Mail, Email Accounts, add a new email account, exchange server and so on. I type in our exchange server address and the name of the new user. If I click on Check Name, I get a message that says "the action could not be completed. the connection to the microsoft exchange server is unavailable. outlook must be online or connected to complete this action." If I skip hitting check name and hit next it says "mail from this exchange server account will be delivered to the existing personal folder on your local computer. if you wish to keep your mail on your server, you must change the default delivery location using the email accounts command from the tools menu. do you wish to continue?" I finish and close and open Outlook to where I imediately get the message "the connection to the microsoft exchange server is unavailable. outlook must be online or connected to complete this action." This happens with any new user I set up in Active Directory!! Please help!!

 

[Zelandakh]

One DNS is a single point of failure. Since you will know there is a worry as you'll be fixing it, I wouldn't worry unduly.

 

[medens]

ok, I set the primary DNS as 192.168.2.3 and the secondary blank, it seems to not have helped my issue really at all though unfortunately. Any ideas to what could be causing all this?

 

[people3]

Hi,

I assume this is working fine for older users, if so you could try setting the new pc up with an old users account.

This will tell you if its a strange AD account \ permission error with the new users.

I would still be tempted to remove the PC from the domain and re-add it perhaps changing the pc's name if thats not a problem.

also make sure any antivirus software is disabled or even uninstalled to again rule this out.

 

[58sniper]

Before we go needlessly removing machines from a domain, send the user an email from Outlook on your computer. If the message doesn't bounce, have the user log on via OWA and see if they get any errors. Let's narrow this down some.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[medens]

unfortunately we are dealing with roaming profiles(not a fan) and if I load a profile of an established user on another machine, it loads fine.

 

[medens]

Any other ideas?

 

[medens]

no other suggestions? this is still haunting me

 

[people3]

Hi

As pat suggested can you access the mailbox using OWA

 

[medens]

we aren't currently using OWA, would you recommend I set it up for testing purposes?

 

[58sniper]

it's setup by default.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/