Exchange Management Console cann't connect to de server

A standard installation of w 2011 SBS server. only th administrator can connect to the exchange server. Creating a user a problem occurs with the email. When connecting to the server with exchange management console the following problem occurs:

[server.domain:80]Connecting to remoteserver failed with the following error message:
De WinRM-client kan de aanvraag niet verwerken. het verificatiemechanisme Kerberos is gebruikt, maar de toegang tot de doelcomputer (server.domain:80) is geweigerd wijzig de configiratie zodat het verificatiemechanisme Kerberos is toegestaan of geef een van de verificatiemechanismen op die door de server worden ondersteund.

I have tried a lot but i cann't find whare and how i can manage the verificationmechanism
please can you help me in a simple way to resolve this problem?
deouweAsked:
Who is Participating?
 
DhanukadamCommented:
possible cause  - 1.Remote PowerShell uses Kerberos to authenticate the user connecting. IIS implements this Kerberos authentication method via a native modulemake sure that go to the PowerShell Virtual Directory and then look at the Modules,the Kerbauth module is not enabled on the Default Web Site, but is only enabled on the PowerShell virtual directory.
2.If the WSMan module entry is missing from the global modules section of the C:\Windows\System32\Inetsrv\config\ApplicationHost.config file, as follows:

<globalModules>
           <add name="WSMan" image="C:\Windows\system32\wsmsvc.dll" />

This will result in the WSMan module displaying as a Managed module on the PowerShell virtual directory.

To correct this, make sure that the WSMan module has been registered (but not enabled) at the Server level, and has been enabled on the PowerShell virtual directory.

or please check the below link...

http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx

thanks

- Dhananjay
0
 
deouweAuthor Commented:
This was not the a good answer. I have windos let check the conectivitie de problems that where shown i have solved en after that it was possible to contact the exchange server
and manage it.
thankc so far
0
 
deouweAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for deouwe's comment #a39381997

for the following reason:

This was the solution
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.