Solved

Exchange Management Console cann't connect to de server

Posted on 2013-05-16
3
462 Views
Last Modified: 2013-08-07
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?
0
Comment
Question by:deouwe
  • 2
3 Comments
 
LVL 3

Accepted Solution

by:
Dhanukadam earned 500 total points
ID: 39173911
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
 

Author Comment

by:deouwe
ID: 39381997
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
 

Author Comment

by:deouwe
ID: 39389172
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

Featured Post

ScreenConnect 6.0 Free Trial

At ScreenConnect, partner feedback doesn't fall on deaf ears. We collected partner suggestions off of their virtual wish list and transformed them into one game-changing release: ScreenConnect 6.0. Explore all of the extras and enhancements for yourself!

Question has a verified solution.

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

Ever notice how you can't use a new drive in Windows without having Windows assigning a Disk Signature?  Ever have a signature collision problem (especially with Virtual Machines?)  This article is intended to help you understand what's going on and…
This story has been written with permission from the scammed victim, a valued client of mine – identity protected by request.
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

831 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