Skip to content

Conversation

@TechSupportJosh
Copy link
Contributor

The short timeouts often result in Windows clients (especially when using Invoke-WebRequest to fetch the client) erroring out as shown below:
image

Increasing the timeout to 5 seconds seems to fix the issue.

@NHAS
Copy link
Owner

NHAS commented Jul 9, 2022

Hi Josh,

Thanks for this pull request!
Im definitely going to merge this, however could I ask you to make the PR to the unstable branch?

I'd also be interested in hearing about the network conditions (ping) between your rssh server and your windows box.

@TechSupportJosh TechSupportJosh changed the base branch from main to unstable July 9, 2022 14:27
@TechSupportJosh
Copy link
Contributor Author

In this case, there are two VMs running on my local machine, but they're bridged networking so they're going from my laptop -> router -> laptop, so it never leaves my local network. Unsure why this happens specifically with IWR

@NHAS
Copy link
Owner

NHAS commented Jul 9, 2022

Oh wild. I have roughly the same setup for testing and have never had this issue.

I would say even 5 seconds is probably a little small just to cover our bases, feel free to change it to 20 seconds, then I'll merge :)

@TechSupportJosh
Copy link
Contributor Author

Yeah it seems like a very random issue, but I've had other people reproduce the issue too (albeit, inconsistently)

@NHAS
Copy link
Owner

NHAS commented Jul 10, 2022

Awesome thanks

@NHAS NHAS merged commit 4c8675c into NHAS:unstable Jul 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants