Antsle Forum
Welcome to our Antsle community! This forum is to connect all Antsle users to post experiences, make user-generated content available for the entire community and more.
Please note: This forum is about discussing one specific issue at a time. No generalizations. No judgments. Please check the Forum Rules before posting. If you have specific questions about your Antsle and expect a response from our team directly, please continue to use the appropriate channels (email: [email protected]) so every inquiry is tracked.
kvm console
Quote from chinywhite on April 12, 2020, 10:05 amhi ive edgelinux antman setup
ip Is set by the dedicated server dhcp
added the template windows 10 and started it giv me internal ip .10 the end
this were I get stuck how do I rdp into this the window
hi ive edgelinux antman setup
ip Is set by the dedicated server dhcp
added the template windows 10 and started it giv me internal ip .10 the end
this were I get stuck how do I rdp into this the window
Quote from lancem on April 13, 2020, 11:41 amIf 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.
Quote from Annata20 on March 18, 2024, 9:36 pmQuote from lancem on April 13, 2020, 11:41 amIf your computer you are RDPing from isn't on the same Palworld Breeding Calculator 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.
I did it this way and it worked, many thanks
Quote from lancem on April 13, 2020, 11:41 amIf your computer you are RDPing from isn't on the same Palworld Breeding Calculator 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.
I did it this way and it worked, many thanks
Quote from jace8392 on May 5, 2025, 1:12 amIn an IB context, especially within Information Technology in a Global Society (ITGS) or Computer Science, it demonstrates a real-world application of systems design and hardware integration. Additionally, incorporating tools like the Kirkeskat beregner—a Danish church tax calculator—can serve as a unique cross-disciplinary example in Maths AA/AI or Economics IA, showing how localized financial tools interact with national systems, supporting global awareness and analytical thinking in IB assessments.
In an IB context, especially within Information Technology in a Global Society (ITGS) or Computer Science, it demonstrates a real-world application of systems design and hardware integration. Additionally, incorporating tools like the Kirkeskat beregner—a Danish church tax calculator—can serve as a unique cross-disciplinary example in Maths AA/AI or Economics IA, showing how localized financial tools interact with national systems, supporting global awareness and analytical thinking in IB assessments.