Link to home
Start Free TrialLog in
Avatar of dei_it
dei_it

asked on

Why do i get WinRM error in Exchange 2010?

i am doing a transition from an existing win2003/exchange2003 to a Win2012R2/Exchange 2010.  At first all was going well, but after a change on the new server IP address the Exchange Management Console is very slow, some information is missing, some errors come up for example trying to open on EMC Mailbox/Addresslist got this error:
"Connecting to Remote server xxx failed with the following error message: WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network and that a firewall exception for the WinRM service is enabled and allows access from this computer.  By default the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. For more information see the about_Remote_troubleshooting Help topic."

The server is in the same subnet, is actually the local server running exchange.  All firewall are set to OFF, also WinRM is allowed for all, verified WinRM for user is set to enable and allowed.  Ran EMTShooter and all passed no errors. User has local and remote access and member of all admin groups, followed all the "Online" suggested to fix WinRM.  The exchange 2010 is working send/receive email, but only when entering EMC is a problem.  The server is not live yet, but before was fast to open and no errors.  The only change was the IP but this new IP has been set up the same way the other was in all IIS settings, Firewalls, ping' is responsive, added to DNS, etc.... last time EMC took 1hr to load and each component takes about 10min.
IMG-00000223--2-.gif
Avatar of Member_2_6515809
Member_2_6515809

I'd start by checking basic network connectivity - can you nslookup the name of the server and what entries are shown for your server name in DNS administrative tool? When you do an NSLookup for the server, do you get an IPv4 or v6 address? What are the actual results you get from pinging by name?
Also worth running netdiag and dcdiag on the server in question, but to be honest it really does sound like a DNS issue.
ASKER CERTIFIED SOLUTION
Avatar of Jamie McKillop
Jamie McKillop
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Well spotted jjmck, I'd missed the 2012R2 bit!
Is it true that Win 2012 R2 does not support exchange, cause i am also having winRM Error since i made installation !
Untitled.jpg