P
PLWells42
We have an agent loaded on a Windows Server 2016. This agent allows for the a migration server running RHEL 6 to connect to the Windows Server via SSH, initiate a shadow copy and then transfer that shadow copy image to the migration server. The initial discover connection works just fine, but when it connects to run the shadow copy commands, the connection is rejected. When we run an SSH echo test, which opens 100 consecutive SSH connections, it consistently succeeds from 0 to 18 and then fails on the 19th connection. So, something on the Windows Server is only allowing 19 consecutive SSH connections. Now we just have to figure out what setting (GPO, local policy, etc.) is limiting these connections.
We've done the echo test between the migration server and other servers in a different environment and they succeed all the way up to 100, so we can rule out any ssh or sshd settings on the migration server. This has to be on the Windows Server 2016 side. Does anyone have any recommendations of where to start looking?
Thanks in advance.
Patrick
Continue reading...
We've done the echo test between the migration server and other servers in a different environment and they succeed all the way up to 100, so we can rule out any ssh or sshd settings on the migration server. This has to be on the Windows Server 2016 side. Does anyone have any recommendations of where to start looking?
Thanks in advance.
Patrick
Continue reading...
