CODEWITHSUNDEEP
powershellwinrm
dean
dean

Reputation: 81

powershell remoting suddenly stops working

I ran this script all day yesterday and then half of the day today. Now suddenly it just hangs for a minute and times out with this error:

PS C:\Users\me> Invoke-Command -computer devspin -ScriptBlock {$PSVersionTable.PSVersion}

[devspin] Connecting to remote server devspin 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. + CategoryInfo : OpenError: (devspin:String) [], PSRemotingTransportException + FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionStateBroken

I rebooted both (domain) machines, reran remoting setup, there is no firewall. And on top of that I can run the same command to other machines or from other machines and it works. It is just these two windows 2012 R2 machines have somehow stopped talking.

any ideas? thanks

Upvotes: 0

Views: 767

Answers (1)

dean
dean

Reputation: 81

Sure glad I went and asked our IT department about this. They said something about how our new switches/hardware vpn don't like the default MTU size windows is set to. They said to set it to 1450 and it would work. I was skeptical, but tried it and BAM! it work. Computers, they never cease to confuse me.

the command I used was:

netsh interface ipv4 set subinterface 13 mtu=1450 store=persistent

But your interface may be different. Hope this helps someone...

Upvotes: 1

Related Questions