Quote from
lancem on April 13, 2020, 11:41 am
If your computer you are RDPing from isn't on the same internal IP network (and most likely, it isn't) then you can't "see" the VM Windows computer.
You can get to the vm using the built-in VNC interface:
In Antman, while listing all the antlets, at the far right of the antlet is a 3-dot menu.
Clicking it will reveal (for KVM antlets) VNC Console which will let you access the antlet.
To use RDP, you'll have to add a virtual bridge network interface to the VM to get it on your network.
https://docs.antsle.com/networking/bridge
Or use the fancy port-forwarding in Antman:
https://docs.antsle.com/networking/port-forwarding
To forward port 3389 from your antsle to the specific Windows antlet.
Then you RDP to the antsle and it will send you on to the antlet.
If it doesn't work after that, it could be the Windows firewall on the VM is blocking port 3389.
If your computer you are RDPing from isn't on the same internal IP network (and most likely, it isn't) then you can't "see" the VM Windows computer.
You can get to the vm using the built-in VNC interface:
In Antman, while listing all the antlets, at the far right of the antlet is a 3-dot menu.
Clicking it will reveal (for KVM antlets) VNC Console which will let you access the antlet.
To use RDP, you'll have to add a virtual bridge network interface to the VM to get it on your network.
https://docs.antsle.com/networking/bridge
Or use the fancy port-forwarding in Antman:
https://docs.antsle.com/networking/port-forwarding
To forward port 3389 from your antsle to the specific Windows antlet.
Then you RDP to the antsle and it will send you on to the antlet.
If it doesn't work after that, it could be the Windows firewall on the VM is blocking port 3389.
chinywhite has reacted to this post.