?
Solved

New install of Exchange 2007 users cannot login and Outlook client request authentication but does not login

Posted on 2008-02-08
3
Medium Priority
?
479 Views
Last Modified: 2012-08-13
I have three servers in a domain.
Windows 2003 Ad, GC Exchange 2003
Windows 2003 Member Server with Exchange 2007
Windows 2003 Ad GC

I have installed exchange 2007 sucessfully however i am unable to login to OWA and VIA the outlook client.  I get no errors on the server.  When i connect via outlook it will prompt me for authentication but not log me in,  and it should not prompt.  In OWA it prompts like normal but does not log in.  I noticed that on the local security options\User Rights Assignment Access this computer form the network only has the SID of the computer not the normal groups.  Could this be the problme?  I am not able to add new users to this.  

Anyone have an idea about why that would be empty.  This is my new Exchage 2007 server which said  it installed sucessfully etc, i did all the right steps to setup but i can not login.

help please.....

0
Comment
Question by:wadephillips
  • 2
3 Comments
 
LVL 7

Expert Comment

by:mcse2007
ID: 20856794
What other application error logs you see from this Exchange 2007 server relating to authentication issue? Also, can you try logging into OWA from IIS, would you get the same error message?
0
 
LVL 1

Author Comment

by:wadephillips
ID: 20857366
Inbound authentication failed with error LogonDenied for Receive connector Default EXCHANGEDB1. The authentication mechanism is Gssapi. The source IP address of the client who tried to authenticate to Microsoft Exchange is [10.0.0.5].

I get this error, but every 10 min or so.  10.0.0.5 is the inside of of the Exchange 2003 box trying to connect to EXchangedb1 the new exchange server.  

I do not get any authentication errors on the server at all.  do you think that the access this comptuer from the network setting could have something to do with it?

I appriciate your time and help on this.



issues.jpg
0
 
LVL 1

Accepted Solution

by:
wadephillips earned 0 total points
ID: 20857525
Turns out my idea was right.  For some reason the domain policy was pushing down a setting for access this computer from the network and it only had the SID in and not the normal default groups.  I removed the setting to define it there and added the normal groups.  

After a gpupdate /force and a reboot i got the new settings and now outlook client can login and owa works a usually..

I appreciate your time on this

take care
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Among the most obnoxious of Exchange errors is error 1216 – Attached Database Mismatch error of the Jet Database Engine. When faced with this error, users may have to suffer from mailbox inaccessibility and in worst situations, permanent data loss.
Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.
Many of my clients call in with monstrous Gmail overloading issues with Outlook. A quick tip is to turn off the All Mail and Important folders from synching. Here is a quick video I made to show you how to turn off these and other folders in Gmail s…
In this video I will demonstrate how to set up Nine, which I now consider the best alternative email app to Touchdown.

599 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question