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. 

You need to log in to create posts and topics.

connecting to my Ubuntu Antlet with Tight VNC

12

_ _
__ _ _ __ | |_ ___| | ___
/ _` | '_ \| __/ __| |/ _ \
| (_| | | | | |_\__ \ | __/
\__,_|_| |_|\__|___/_|\___|

[email protected]:~ # ps -deaf|grep vnc
qemu 7383 1 1 Jul03 ? 00:29:06 /usr/bin/qemu-system-x86_64 -name guest=centos,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-8-centos/master-key.aes -machine pc-i440fx-2.4,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu Westmere -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 203e57b7-9477-45d9-a673-6c0f0b0b1df2 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-8-centos/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -drive file=/antlets/centos/CentOS-7.qcow2,format=qcow2,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=28,id=hostnet0 -device virtio-net-pci,host_mtu=1500,netdev=hostnet0,id=net0,mac=b2:61:6e:73:6c:15,bus=pci.0,addr=0x3 -netdev tap,fd=30,id=hostnet1 -device virtio-net-pci,host_mtu=1500,netdev=hostnet1,id=net1,mac=52:54:00:3b:7f:44,bus=pci.0,addr=0x8 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input2,bus=usb.0,port=1 -vnc 127.0.0.1:1 -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on
root 9778 7880 0 17:09 pts/2 00:00:00 grep vnc
qemu 20698 1 2 Jul03 ? 01:00:20 /usr/bin/qemu-system-x86_64 -name guest=xwindows,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-6-xwindows/master-key.aes -machine pc-i440fx-2.4,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu Westmere -m 4096 -realtime mlock=off -smp 3,sockets=3,cores=1,threads=1 -uuid 027c0d6a-b196-4c95-bf01-ad14e039f9ac -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-6-xwindows/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -drive file=/antlets/xwindows/Ubuntu16.04.qcow2,format=qcow2,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=27,id=hostnet0 -device virtio-net-pci,host_mtu=1500,netdev=hostnet0,id=net0,mac=b2:61:6e:73:6c:14,bus=pci.0,addr=0x3 -netdev tap,fd=29,id=hostnet1 -device virtio-net-pci,host_mtu=1500,netdev=hostnet1,id=net1,mac=52:54:00:d2:c4:18,bus=pci.0,addr=0x8 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input2,bus=usb.0,port=1 -vnc 127.0.0.1:0 -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on
[email protected]:~ #
[email protected]:~ # netstat -l|grep 5900
tcp 0 0 myantsle:5900 0.0.0.0:* LISTEN
[email protected]:~ # netstat -l|grep 5901
tcp 0 0 myantsle:5901 0.0.0.0:* LISTEN
[email protected]:~ #
[email protected]:~ # ps -deaf|more|grep 6900
root 23870 7880 0 17:14 pts/2 00:00:00 grep 6900

---> Started NoVNC web interface for first KVM

 

[email protected]:~ # ps -deaf|more|grep 6900
root 24298 5037 0 17:15 ? 00:00:00 bash /usr/local/antsleOS/antsle-vnc/utils/launch.sh --vnc localhost:5900 --listen 6900
root 24309 24298 1 17:15 ? 00:00:00 /usr/lib/python-exec/python2.7/python /usr/local/antsleOS/antsle-vnc/utils/websockify/run --web /usr/local/antsleOS/antsle-vnc/utils/../ 6900 localhost:5900
root 24389 24309 0 17:15 ? 00:00:00 /usr/lib/python-exec/python2.7/python /usr/local/antsleOS/antsle-vnc/utils/websockify/run --web /usr/local/antsleOS/antsle-vnc/utils/../ 6900 localhost:5900
root 24763 7880 0 17:15 pts/2 00:00:00 grep 6900
[email protected]:~ #

Cannot connect via VNC.

when using MobaXterm I get prompted for password but I don't see any reference to what that password might be or I wonder if mobaxterm just prompts you for it.

 

I emailed support and it was suggested that I install VNC on each antlet.

That works.

 

Hey @ac9hp,

I ran into this same issue while trying to connect to my Android x86 image. What I ended up doing was tunneling in and directly connecting to the real VNC port:

ssh -L 8882:localhost:5902 root@my-antsle-ip-here -i ~/.ssh/my_key_here

The port should be 5900 + whatever the port your antlet is on. You can get this via: virsh vncdisplay. I chose 8882 randomly as my local port. I used VNC Connect instead of TightVNC as I'm on OSX, but simply connecting to localhost:8882 worked just fine.

Hopefully this will help out someone in the future. Cheers!

@avidityjames,

This works great when your system supports SSH.

I have not looked recently but I need to make this work from an iPad.

I suspect I could get to to work from a PC using some SSH package but I do not recall seeing a SSH package for my iPad.  I may go look in the store.

Mostly I have been just using a VNC server to get into the machines.

For a while on my windows VM I was using Teamviewer but it kept getting flagged for commercial use and VNC is just easier and no hassle.

Thanks for the tip!

 

Wayne

It is really annoying using the web browser as VNC client. I have the same issue and never works

```

[email protected]:~ # virsh list
Id Name State
---------------------------
2 Kali-2019 running

[email protected]:~ # virsh vncdisplay kali-2019
error: failed to get domain 'kali-2019'

[email protected]:~ # virsh vncdisplay 2
127.0.0.1:1

[email protected]:~ #

```

So based on your calculation the in-port will be 5900+1 = 5901

Then, tried to connect using VNC client to the hostname: kali-2019.xxxx.antsle.us:5901

Getting connect refuse.

Please advice.

 

Thank you

 

@yasirmohammed

 

what are you using for your SSH command into the antsle before trying to connect to the antsle?

also once you run the SSH -L command you need to connect to your local machine and it will forward to the antsle..

 

I was able to connect to the port 5901 using the SSH -L (Port forward) but I am getting a black screen with a message :

( Attempting to reconnect to VNC Server ... RFB protocol error: invalid message type 255 )

Thanks

I know it's not the exact same error message, but according to this:

https://www.ixsystems.com/community/threads/vms-using-freenas-11-gui-error-connecting-via-vnc-at-linux-setup.54582/

It could be the quality level in the VNC client being set to Auto instead of High?

 

12