You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context: A Python script that use pywinrm to open a WinRM session on a remote Windows host. Once the WinRM session is open the script send continuously PowerShell command to explore the remote hard drive and retrieve each directory listing.
I use ntlm transport. My client is macOS and the remote Windows host is Windows 7 SPI with Powershell 5.1.
Problem: After ~30 minutes of run the run_ps that I use to get the directory listing failed with this error message:
ConnectTimeout(MaxRetryError("HTTPConnectionPool(host='192.168.1.42', port=5985): Max retries exceeded with url: /wsman (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f06380c1430>, 'Connection to 192.168.1.42 timed out. (connect timeout=30)'))
I can reproduce this issue each time.
Is the WinRM session has a kind of maximum time? I don't think so...
This is not an idle timeout issue because the last working run_ps command is only 1 second before the one that produce the time out issue.
Thank you for the help.
The text was updated successfully, but these errors were encountered:
Context: A Python script that use pywinrm to open a WinRM session on a remote Windows host. Once the WinRM session is open the script send continuously PowerShell command to explore the remote hard drive and retrieve each directory listing.
I use
ntlm
transport. My client is macOS and the remote Windows host is Windows 7 SPI with Powershell 5.1.Problem: After ~30 minutes of run the
run_ps
that I use to get the directory listing failed with this error message:I can reproduce this issue each time.
Is the WinRM session has a kind of maximum time? I don't think so...
This is not an idle timeout issue because the last working
run_ps
command is only 1 second before the one that produce the time out issue.Thank you for the help.
The text was updated successfully, but these errors were encountered: