Docker transparent network command breaks RDP access on AWS

After deploying a Windows 2016 host with containers on AWS and RDP’ing in to the Windows UI and powershell to run docker network create -d transparent transparent command as per the Rancher Windows instructions it seems to break RDP access and it is impossible to re-connect via RDP to the server again.

Has anyone else experienced this or is there some work-around to avoid this?

Transparent network will not be supported on some of cloud providers.

I am using hyperV and even I have the same issue. RDP access is broken soon after “docker network create -d transparent transparent” is executed.
Is there any workaround for this.

I ran into he same issues in aws. Any workaround would be great.

We found a workaround.We are using Hyper-V and was using a windows 2016 server.
We went to hyper-v console, selected Connect via Console, and we could connect to the machine. Then we did the below steps.

  1. Go to Control Panel\Network and Internet\Network Connections
  2. Select the LAN connection and right click select properties.
  3. Check the option, Internet Protocol Version 4 (TCP/ IPv4)
  4. Now it should start working.