• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 765
  • Last Modified:

Users cannot login to OWA - error HTTP 500 - The local Security Authority cannot be contacted

I am implementing EBS in the existing Windows 2003 SP2 environment. At this point, there are new Windows 2008 servers, both domain controllers, both DNS servers, and 2 old domain controllers, one of them is a DNS server, another one is an Exchange server.
This setup was working for a while until I rebooted one 2003 and one 2008 server. After that, all users lost ability to log on to their computers. In addition, one one could open OWA and, I believe, Outlook (definitely, not from remote computers). With OWA, they receive: "HTTP 500 - The local Security Authority cannot be contacted". The only exception was from servers while logged in as domain admin.
I found  a way to '"fix" it but it lasts for a very short time if users close Outlook or OWA. What I did was I went to the Account tab in ADUC and gave them access to all computers listed there.
It does the trick but only for a while.

No new group policies were introduced, unless they came with EBS and 2008 Server.

Thank in advance for your help.


0
pfarber22
Asked:
pfarber22
  • 3
  • 2
1 Solution
 
pfarber22Author Commented:
Yes, I have. Almost identical situation.
The person asking the question resolved it: "i have checked this all out and it it turns out to be that due to the fact that i had restricted users to their own pc - this in turn basically locked them out of OWA if they used another PC.

I have removed their PC assignments within active directory and its fixed the problem"

How did he "remove their PC assignments within active directory", I don't know but, in my case, I don't know of any restrictions implemented via GP or otherwise. In addition, my users could not access OWA from any computer except servers.
My 'fix' by granting users access to servers manually does not last long.
0
 
WizardWillCommented:
Can you make sure that the netlogon service on all the dc's are started and set the startup type to automatic... If the service is not running start it .. right click and than start ...
0
 
pfarber22Author Commented:
Of course, it is running. I could always connect from any server other than DC. It is started and set to autmatic on all DC.
0
 
pfarber22Author Commented:
The reason for this behavior was found by EBS support. Once passed 30 days after installation, EBS licenses needed to be properly registered. Since it was not done, people were shut down from their computers (and Outlook). Additional grace period was given to complete the installation and configuration.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now