# WinRM not working

**URL:** <https://forums.powershell.org/t/winrm-not-working/13101>\
**Category:** PowerShell Help\
**Created:** [September 6, 2019, 11:42am UTC](https://forums.powershell.org/t/winrm-not-working/13101 "2019-09-06T11:42:32Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![aaron-hardy](https://avatars.discourse-cdn.com/v4/letter/a/c4cdca/32.png) [@aaron-hardy](https://forums.powershell.org/u/aaron-hardy)\
**Post date:** [October 23, 2019, 4:36pm UTC](https://forums.powershell.org/t/winrm-not-working/13101/21 "2019-10-23T16:36:01Z")

</div>

Response time is relative and there are a number of factors involved when it comes to performance. Some things to consider:

1. Response time is dictated by what resources are available on both systems, especially the system where PowerShell is doing all the processing.
2. You're performing remote commands over a wireless connection which is subject to low bandwidth, interference or distance-related issues, and it's just not as reliable as a good ol' wire.
3. For instance, if you ran a simple command against a remote system, like `Get-Service -ComputerName server -Name Netlogon`, it shouldn’t take too long compared to if you ran `Invoke-Command -ComputerName server { Get-ComputerInfo }` or an unfiltered `Get-EventLog`/`Get-WinEvent`.

For starters, if it's possible, get the laptop on a wired connection.

---

<div class="post-metadata">

**Author:** ![sinoath](https://avatars.discourse-cdn.com/v4/letter/s/e99b99/32.png) [@sinoath](https://forums.powershell.org/u/sinoath)\
**Post date:** [October 28, 2019, 11:19am UTC](https://forums.powershell.org/t/winrm-not-working/13101/22 "2019-10-28T11:19:05Z")

</div>

Thanks Aaron for the response,  
i totally agree with you regardind the wire powa, but i just figured out what was the problem: firewall rules  
i had to enable some of those on the laptop firewall, and after that i now have a ‘normally delayed’ response (due to wireless connection)  
I mean that now i issue a command and in a couple of second i have response from the server, which seems to be normal to me (now)

The firewall rules were mainly:

- File and Printer sharing
- Network Discovery
- DCOM
- Remote Service Management (RPC)
- Other that probably were not part of this problem

Now almost all works fine, exept a strange error that i discussed in another post of mine, regading the use of Get-WmiObject with the -AsJob parameter  
but since i can bypass this strange behavior with

- Invoke-Command -AsJob or
- Start-Job  
I just stopped struggling to solve it

---

<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:31pm UTC](https://forums.powershell.org/t/winrm-not-working/13101/23 "2024-05-16T20:31:09Z")

</div>



[Previous page](https://forums.powershell.org/t/winrm-not-working/13101.md?page=1)