Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows AD Authentication

Status
Not open for further replies.

kskid

Technical User
Mar 21, 2003
1,767
US
URGENT!!!!

BOE XI, R2 on WIndows 2003

Does anyone know the fix for the following message?

The Active Directory Authentication plugin could not authenticate at this time. Please try again. If the problem persists, please contact your technical support department.

I've got users ready to string me up and hang me out to dry, especially the 24-7 areas of operation that uses Infoview and my Crystal Reports Queries a lot.

-lw
 
I forgot to mention that I receive this response when trying to log into either CMC or InfoView.

 
Just had the same issue when the physical server was moved to a new location and the ip address was changed. I had to stop and restart the CMC after insuring that the server which is now virtual had been added back to the domain.

have you verified that the CMC is running and enabled? Can you login using enterprise authentication?

 
Yes, I can log in using Enterprise authentication for both CMC and Infoview and I can do everything that I did under Windows AD authentication. I want the Windows AD to handle the security since my users have more than enough different usernames and passwords to remember without burdening them with another one from Enterprise.

I did find out that the problem occurred when our network team increased the Windows AD security function level in preparation to switching over to Sharepoint and dropping the intranet. That change propagated down to our servers and triggered the authentication problem.

We are going to download and install Release 3. Hopefully, it will fix the problem. Besides, I am almost certain that is what SAP will recommend first so I might as well get it out of the way.

-lw
 
careful with release 3. i use .net and have to wait for 3.1
 
I'll let my guys know. We are using .net as well.
 
By the way, we have a work around by switching to NTLM authentication instead of Kerberos. It may not be as secure but my users are happy.
 
I see, didn't consider that. I am using NTLM as well since everything in inside the firewall.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top