Exchange online- The WinRM client cannot process the request because the server name cannot be resolved

When i tried to connect to Exchange online by using powershell the following error arises for me.

$LiveCred = Get-Credential

Username

password

$Session = New-PSSession -ConfigurationName Microsoft.Exchange

 -ConnectionUri https://ps.outlook.com/powershell/ -Credential 

$LiveCred -Authentication Basic -AllowRedirection //While creating session the error

occurs."[ps.outlook.com] The WinRM client cannot process the request because the server name

 cannot be resolved"..


i have configured the winrm correctly..



C:\Windows\system32>winrm quickconfig
WinRM is already set up to receive requests on this machine.
WinRM is already set up for remote management  on this machine.

But still the error exists for me.






June 20th, 2013 3:39pm

Are you sure you DNS is working properly?

Try run execute "nslookup ps.outlook.com". What is the result?

Malte

Free Windows Admin Tool Kit Click here and download it now
June 20th, 2013 5:35pm

Thanks for your reply Malte,

When executing "nslookup ps.outlook.com"

result:
Server:Unknow
address:ip address

Dns requeste time out
   time out for 2 seconds


June 21st, 2013 9:34am

Ok... I think this is a network related problem. Please verfiy a valid dns server is configured on you machine.

Are you getting your "IP" via DHCP or manual configuration?

Malte

Free Windows Admin Tool Kit Click here and download it now
June 21st, 2013 10:50am

thank for your reply malte...

ip via "DHCP" only.

June 21st, 2013 2:33pm

When i try to open this url "https://ps.outlook.com/powershell/" via browser

it display error message ,

"This webpage is not found
No webpage was found for the web address: https://pod51037psh.outlook.com/powershell-liveid/
Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found."

Free Windows Admin Tool Kit Click here and download it now
June 21st, 2013 3:00pm

Hi,

you have to ensure DNS is working properly. You problem has nothing todo with powershell but with you network configuration. If you can't solve it by yourself consult you network admin.

Malte

June 21st, 2013 4:56pm

Thanks for your reply Malte....

i will check it out with network admin...

Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2013 1:10pm

I have the same error prompting but in my case I'm running this script

$cred=Get-Credential 

Invoke-Command -ComputerName <computername> -ScriptBlock {ipconfig} -Credential $cred

I have 4 different remote desktops but this is running correctly only on one.

In another case it's giving me an error : 

Connecting to remote server failed as WinRM client cannot process the request because the server name cannot be resolved.

What could be causing this , I've tried a lot of things but the error still persists.


July 1st, 2013 6:45pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics