# WinRM failes to connect, is it possible to reset client?

**URL:** <https://forums.powershell.org/t/winrm-failes-to-connect-is-it-possible-to-reset-client/6742>\
**Category:** PowerShell Help\
**Created:** [July 1, 2016, 10:27am UTC](https://forums.powershell.org/t/winrm-failes-to-connect-is-it-possible-to-reset-client/6742 "2016-07-01T10:27:28Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gregory-suvalian](https://avatars.discourse-cdn.com/v4/letter/g/9d8465/32.png) [@gregory-suvalian](https://forums.powershell.org/u/gregory-suvalian)\
**Post date:** [July 1, 2016, 10:27am UTC](https://forums.powershell.org/t/winrm-failes-to-connect-is-it-possible-to-reset-client/6742/1 "2016-07-01T10:27:28Z")

</div>

Hello,

For some reason any external Wsman communication ends up in error. I try to use Test-Wsman cmdlet on non-existent box and it immeditately fails, if I use real host it fails with the same error message. I can see via network capture that connection is not event attempted to be made. This was working before but stopped working for some reason. I ruled out a bunch of stuff already (network, corrupted user profile, etc), still issue happens. Searched if it’s possible to reset Wsman client but did not find a way to do that either. Any ideas where to look else short of reinstalling OS\>

```
[ADMIN]: PS > test-wsman nonexistentserver
test-wsman : The WinRM client sent a request to an HTTP server
and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. 
At line:1 char:1
+ test-wsman nonexistentserver
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (nonexistentserver:String) [Test-WSMan], InvalidOperationException
    + FullyQualifiedErrorId : WsManError,Microsoft.WSMan.Management.TestWSManCommand
```

---

<div class="post-metadata">

**Author:** ![nigel-tatschner](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/nigel-tatschner/32/312_2.png) [@nigel-tatschner](https://forums.powershell.org/u/nigel-tatschner)\
**Post date:** [July 1, 2016, 10:30am UTC](https://forums.powershell.org/t/winrm-failes-to-connect-is-it-possible-to-reset-client/6742/2 "2016-07-01T10:30:24Z")

</div>

Have you tried PSExec?

[https://technet.microsoft.com/en-us/sysinternals/psexec.aspx?f=255&amp;MSPPError=-2147217396](https://technet.microsoft.com/en-us/sysinternals/psexec.aspx?f=255&amp;MSPPError=-2147217396)

This is a great way to get around some connection issues

---

<div class="post-metadata">

**Author:** ![gregory-suvalian](https://avatars.discourse-cdn.com/v4/letter/g/9d8465/32.png) [@gregory-suvalian](https://forums.powershell.org/u/gregory-suvalian)\
**Post date:** [July 1, 2016, 10:32am UTC](https://forums.powershell.org/t/winrm-failes-to-connect-is-it-possible-to-reset-client/6742/3 "2016-07-01T10:32:12Z")

</div>

I need wsman to work, issue is not connectivity since it fails with the same error message for existant and non existant hosts. Connection is not even attempted to be made.

---

<div class="post-metadata">

**Author:** ![gregory-suvalian](https://avatars.discourse-cdn.com/v4/letter/g/9d8465/32.png) [@gregory-suvalian](https://forums.powershell.org/u/gregory-suvalian)\
**Post date:** [July 7, 2016, 12:05pm UTC](https://forums.powershell.org/t/winrm-failes-to-connect-is-it-possible-to-reset-client/6742/4 "2016-07-07T12:05:19Z")

</div>

In case somebody else runs into this.  
Issue turns to be HTTP proxy setup on my machine which was directing HTTP traffic to proxy server instead. Unfortunately Test-Wsman does not allow to specify options for connection to bypass proxy and hence it will fail in such situation.

---

<div class="post-metadata">

**Author:** ![dotnVo](https://avatars.discourse-cdn.com/v4/letter/d/4af34b/32.png) [@dotnVo](https://forums.powershell.org/u/dotnVo)\
**Post date:** [May 16, 2024, 8:40pm UTC](https://forums.powershell.org/t/winrm-failes-to-connect-is-it-possible-to-reset-client/6742/5 "2024-05-16T20:40:54Z")

</div>

Closed on May 16, 2024, 8:40pm UTC


