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.
connecting to my Ubuntu Antlet with Tight VNC
Quote from ac9hp on May 7, 2018, 11:54 amI installed tight VNC and when I try to connect to my antsle it does not act like I can.
I added a LAN connector to my local network direct
I am using ip addressing so it is not a DNS issue.
I followed these instructions here:
https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-16-04
I am on the second step in Step 3. Connecting with Tight VNC client.
When I use the NoVNC on my surface pro I do not get a mouse pointer so I was just trying to resolve that issue by using another VNC viewer.
Any thoughts?
I installed tight VNC and when I try to connect to my antsle it does not act like I can.
I added a LAN connector to my local network direct
I am using ip addressing so it is not a DNS issue.
I followed these instructions here:
https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-16-04
I am on the second step in Step 3. Connecting with Tight VNC client.
When I use the NoVNC on my surface pro I do not get a mouse pointer so I was just trying to resolve that issue by using another VNC viewer.
Any thoughts?
Quote from mardo.delcid on May 9, 2018, 6:33 pmHi ac9hp,
Have you tried to connect directly to the VNC service that virsh provides out of the box?
You can find the VNC port by SSHing into your antsle and executing:
virsh vncdisplay ANTLET_NAME
That'll return something like: 127.0.0.1:0
You can connect to display 0 in the Tight VNC client.
If it asks for port, you can find the port by adding 5900 to the display number. In this example, for cero (0) is: 5900 + 0 = 5900.
If the output would have been something like 127.0.0.1:4, then port would be 5904 (5900 + 4).
Let us know how it goes!
Hi ac9hp,
Have you tried to connect directly to the VNC service that virsh provides out of the box?
You can find the VNC port by SSHing into your antsle and executing:
virsh vncdisplay ANTLET_NAME
That'll return something like: 127.0.0.1:0
You can connect to display 0 in the Tight VNC client.
If it asks for port, you can find the port by adding 5900 to the display number. In this example, for cero (0) is: 5900 + 0 = 5900.
If the output would have been something like 127.0.0.1:4, then port would be 5904 (5900 + 4).
Let us know how it goes!
Quote from ac9hp on May 10, 2018, 5:41 amI seem to have an issue with my hostname?
root@myantsle:/etc # virsh vncdisplay antlet15
error: failed to get domain 'antlet15'
error: Domain not found: no domain with matching name 'antlet15'root@myantsle:/etc # virsh vncdisplay antlet15.bblv
error: failed to get domain 'antlet15.bblv'
error: Domain not found: no domain with matching name 'antlet15.bblv'root@myantsle:/etc # virsh vncdisplay antlet15.local
error: failed to get domain 'antlet15.local'
error: Domain not found: no domain with matching name 'antlet15.local'root@myantsle:/etc # virsh vncdisplay ubuntu16
error: failed to get domain 'ubuntu16'
error: Domain not found: no domain with matching name 'ubuntu16'root@myantsle:/etc # virsh vncdisplay ubuntu16.bblv
error: failed to get domain 'ubuntu16.bblv'
error: Domain not found: no domain with matching name 'ubuntu16.bblv'root@myantsle:/etc #
I seem to have an issue with my hostname?
root@myantsle:/etc # virsh vncdisplay antlet15
error: failed to get domain 'antlet15'
error: Domain not found: no domain with matching name 'antlet15'root@myantsle:/etc # virsh vncdisplay antlet15.bblv
error: failed to get domain 'antlet15.bblv'
error: Domain not found: no domain with matching name 'antlet15.bblv'root@myantsle:/etc # virsh vncdisplay antlet15.local
error: failed to get domain 'antlet15.local'
error: Domain not found: no domain with matching name 'antlet15.local'root@myantsle:/etc # virsh vncdisplay ubuntu16
error: failed to get domain 'ubuntu16'
error: Domain not found: no domain with matching name 'ubuntu16'root@myantsle:/etc # virsh vncdisplay ubuntu16.bblv
error: failed to get domain 'ubuntu16.bblv'
error: Domain not found: no domain with matching name 'ubuntu16.bblv'root@myantsle:/etc #
Quote from ac9hp on May 10, 2018, 5:43 amThis is even more odd...
As it can resolve the hostname.
Guess I should read up on using virsh and see how I can list what it knows these antlets as..
root@myantsle:~ # virsh vncdisplay ubuntu16.local
error: failed to get domain 'ubuntu16.local'
error: Domain not found: no domain with matching name 'ubuntu16.local'root@myantsle:~ # ping ubuntu16
PING ubuntu16.local (172.24.1.193) 56(84) bytes of data.
64 bytes from ubuntu16.local (172.24.1.193): icmp_seq=1 ttl=64 time=0.360 ms
64 bytes from ubuntu16.local (172.24.1.193): icmp_seq=2 ttl=64 time=0.583 ms
64 bytes from ubuntu16.local (172.24.1.193): icmp_seq=3 ttl=64 time=0.289 ms
64 bytes from ubuntu16.local (172.24.1.193): icmp_seq=4 ttl=64 time=0.330 ms
64 bytes from ubuntu16.local (172.24.1.193): icmp_seq=5 ttl=64 time=1.26 ms
64 bytes from ubuntu16.local (172.24.1.193): icmp_seq=6 ttl=64 time=0.357 ms
^C
--- ubuntu16.local ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5007ms
rtt min/avg/max/mdev = 0.289/0.530/1.263/0.341 ms
This is even more odd...
As it can resolve the hostname.
Guess I should read up on using virsh and see how I can list what it knows these antlets as..
root@myantsle:~ # virsh vncdisplay ubuntu16.local
error: failed to get domain 'ubuntu16.local'
error: Domain not found: no domain with matching name 'ubuntu16.local'root@myantsle:~ # ping ubuntu16
PING ubuntu16.local (172.24.1.193) 56(84) bytes of data.
64 bytes from ubuntu16.local (172.24.1.193): icmp_seq=1 ttl=64 time=0.360 ms
64 bytes from ubuntu16.local (172.24.1.193): icmp_seq=2 ttl=64 time=0.583 ms
64 bytes from ubuntu16.local (172.24.1.193): icmp_seq=3 ttl=64 time=0.289 ms
64 bytes from ubuntu16.local (172.24.1.193): icmp_seq=4 ttl=64 time=0.330 ms
64 bytes from ubuntu16.local (172.24.1.193): icmp_seq=5 ttl=64 time=1.26 ms
64 bytes from ubuntu16.local (172.24.1.193): icmp_seq=6 ttl=64 time=0.357 ms
^C
--- ubuntu16.local ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5007ms
rtt min/avg/max/mdev = 0.289/0.530/1.263/0.341 ms
Quote from ac9hp on May 10, 2018, 5:44 amHere we go:
root@myantsle:~ # virsh list
Id Name State
----------------------------------------------------
5 Freebsd running
9 Win10 running
10 AppleIIEmulator runningroot@myantsle:~ # virsh vncdisplay AppleIIEmulator
127.0.0.1:0root@myantsle:~ #
Here we go:
root@myantsle:~ # virsh list
Id Name State
----------------------------------------------------
5 Freebsd running
9 Win10 running
10 AppleIIEmulator runningroot@myantsle:~ # virsh vncdisplay AppleIIEmulator
127.0.0.1:0root@myantsle:~ #
Quote from ac9hp on May 10, 2018, 5:48 amSo my antlse is 172.24.1.131 and if I use tight VNC I get a message that my antsle is activing refusing the connection.
If I VNC to the machine ip of 172.24.1.193 it times out.
Maybe I am fighting a firewall issue not related..
So my antlse is 172.24.1.131 and if I use tight VNC I get a message that my antsle is activing refusing the connection.
If I VNC to the machine ip of 172.24.1.193 it times out.
Maybe I am fighting a firewall issue not related..
Quote from mardo.delcid on May 11, 2018, 4:07 pmHi ac9hp,
You need to use the *antlet name*, not the hostname. Looking at your output, I see your antlet names are "Freebsd", "Win10" & "AppleIIEmulator". Based on the names, my guess is that ubuntu is "AppleIIEmulator" (not ubuntu16), so you should execute:
virsh vncdisplay AppleIIEmulator
That should give you the display number to use in the VNC client.
Hi ac9hp,
You need to use the *antlet name*, not the hostname. Looking at your output, I see your antlet names are "Freebsd", "Win10" & "AppleIIEmulator". Based on the names, my guess is that ubuntu is "AppleIIEmulator" (not ubuntu16), so you should execute:
virsh vncdisplay AppleIIEmulator
That should give you the display number to use in the VNC client.
Quote from skewled on July 3, 2018, 11:59 amI can concur that the instructions given do not help connect to the antlet.
IP of Antsle: 192.168.1.20
Getting output from virsh vncdisplay ubuntu returns
127.0.0.1:1
Using RoyalTS Tightvnc, host: 192.168.1.20:5901
Connection is refused, zero networking rules are in place to prohibit the internal connection.
Using VNCViewer, connection refused.
I can concur that the instructions given do not help connect to the antlet.
IP of Antsle: 192.168.1.20
Getting output from virsh vncdisplay ubuntu returns
127.0.0.1:1
Using RoyalTS Tightvnc, host: 192.168.1.20:5901
Connection is refused, zero networking rules are in place to prohibit the internal connection.
Using VNCViewer, connection refused.