Solved

Exchange Server 2007 added to environment, now users cannot access email (outlook)

Posted on 2008-10-14
5
240 Views
Last Modified: 2012-06-27
I added an Exchange 2007 server to our Exchange 2003 environment to play around with it (doh!).  Now I have some users that cannot acces email.  When they open outlook they are prompted for a username and password.

also, on the Exchange 2003 servers I am seeing different events that all have the same basic error:

"The Domain Controller xxxx  is running (Unknown Operating System) (Unknown Service Pack). DSAccess requires that  Domain Controllers that run Windows 2000 have at least Service Pack 3 installed. "

The specified domain control is actually running Server 2003 with Service Pack 3.  Attempts to login to the specified Domain Controller console fail.

Any ideas on which direction I should go to get users back in to email, and correct the DC issue?

Thanks.
0
Comment
Question by:brett_apfc
  • 3
  • 2
5 Comments
 
LVL 18

Accepted Solution

by:
exx1976 earned 500 total points
ID: 22714248
"Attempts to login to the specified Domain Controller console fail"

What are the errors?  Can you remotely manage the DC in question?  If so, what do the event logs have to say?  With the limited information given above, it sounds to me like you have a problem with your DC, not with Exchange..
0
 

Author Comment

by:brett_apfc
ID: 22714262
login error on DC shows:

"The system could not log you on.  Make sure your User name and domain are correct..."

I can't get logged in to look at the logs.

0
 

Author Comment

by:brett_apfc
ID: 22714503
I shut the DC down, and brought it back up.  I can now log in.  Error logs show mulitple Event 1173's:

Internal event: Active Directory has encountered the following exception and associated parameters.  
Exception:
e0010002
Parameter:
0
 
Additional Data
Error value:
8451
Internal ID:
109079c


Replication appears to be functioning with the other DC's.  Maybe I just had hung DC?
0
 
LVL 18

Expert Comment

by:exx1976
ID: 22714855
Are you also getting event ID 1203's and 1481's?  You should be, as they normally accompany 1173's.  If so, 1203 should tell you what the DN is of the object that caused the exception, and 1481 will give you the attribute name that is not supported.

Normally it's caused by UNICODE data that has the SYNTAX_UNICODE_TYPE attribute type.  2000 SP4 and 2008 both accept this as a valid attribute type, but 2003 doesn't (I don't know why).  To get rid of this error/problem, you need to find the offending object, and use ADSIEdit to browse to the problem object, then clear the attribute that is set as UNICODE.

More information can be found here:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;947020
0
 

Author Comment

by:brett_apfc
ID: 22715151
Since the server reboot, I am no longer seeing any issues in the logs.  I never did see any 1203's or 1481's.

Hopefully, as exx1976 said, this was just a DC issue, and rebooting it fixed it.

I will continue to monitor this and report back by tomorrow (unless errors beging appearing again sooner than that!).

Thanks for the help.
0

Featured Post

Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…

760 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

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now