Exchange causes Outlook P/W prob

[SgtMUSMC]

In Exchange 5.5 we are having problems with regular users being able to access their mailboxes. The admins can get into their own mailboxes with out any problems. With the users they are getting prompted for a username, password and domain. When the info is put in it comes back saying that it is incorrect. I have created a test account and it does the same thing with it. I have gone through all of the permissions and have not found anything wrong. I have even cleaned up alot of stuff while trying to troubleshoot this. The Navy side had messed up the Site Connector to the PDC and also the Directory Replication Connector yesterday. We went through and got those back up today so that the mail is at least coming through again. The mail is there its just that the users are getting prompted for their passwords.
Any one have any ideas?
Thanks
Sgt. Moreland

 

[Telecommguy]

Did you ever figure out what was causing your problem? I am experiencing the same or similar as well. I would appreciate any info you could pass along.

 

[DarraghFitzpatrick]

2 things

have you ensured a primary account has been assigned to each mailbox. (Mailbox properties)

Check the permissions of each mailbox ensure appriate user for each mailbox is assigned and has full mailbox permissions

 

[wood55]

It sounds like the workstations need to be put back into your domain so that the users can be authenticated properly.
If the "admins" are Domain Admins they would have been able to add their machines in automatically as they logged in but the normal users wouldn't have and may just have logged in with cached credentials.

Also a simple reboot of the Exchange Server once the PDC is up and running again can often fix this kind of problem.

Andy.

 

[SgtMUSMC]

All of the machines are on the domain. Also all of the users have rights into their own mailboxes in the permissions tab. It is user rights not full admin rights though. Also the server has been rebooted a few times and also made sure that all services were running. Once a user is added into Domain admins they are able to get into their mailbox. Trying to get around a rebuild here. Can anyone think of anything else that it might be. All help is appreciated.

 

[wood55]

Inside exchange admin, go to tools > options > Permissions and check that your default domain is set correctly.

This might be way off the mark, but it's worth checking!

 

[Telecommguy]

Hey everyone I want to run something past all of you.
We had just realized that the Exchange server has not been rebooted since the last time the PDC has been rebooted. We think that once a reboot is done, it will take care of our problems, but need to make sure all users have logged off. I know wood55 had eluded to that. I just wanted to confirm with everyone else, and also to see if SgtMUSMC has rebooted since there last PDC mishap.
I would like to thank everyone for their ideas and suggestions, it is greatly appreciated.

 

[SgtMUSMC]

I had gone into the permissions tab to ensure that the correct domain was in there. It seems by now I have been everywhere in Exchange except for where I need to be. The server has also been rebooted several times. I am on a ship right now and this thing is always loosing power so it gets rebooted more than I would like. Also have changed the users rights to admin in their ownership of their mailbox and it didnt do anything.
Thanks guys for all of your help. Hey Telecommguy I have seen where email was doing some screwy things because the server hadnt been rebooted in a while. Hope that helps you out.

 

[jonarden]

I saw the same "symptoms" when Exchange was moved to a new Win 2000 server in an NT (not an Active Directory) environment. It was solved by making sure that NetBios in the server's TCP/IP settings were enabled (someone had disabled them during the new installation). Also make sure that TCP/IP NetBIOS Helper Service is running on the Win 2000 server where exchange is installed.

 

[AhkSaudi]

If you are having two different log on and exchange domains make sure all the users have the same user name and passwords on both the domains, we faced this problem before it was solved after modifying with identical usernames and passwords on servers.