You are not logged in.

#1 2013-07-29 11:59:23

Box0
Member
From: Italy
Registered: 2011-09-21
Posts: 218

Problem connecting to a vncserver from an android tablet

I'm trying to connect an android tablet to a vncserver started into my laptop, following this: https://wiki.archlinux.org/index.php/Vn … Time_Setup

I'm usng the tigervnc package from [community]

After issuing "vncserver" in my laptop i got:

New 'dellr:1 (dn)' desktop is dellr:1

Starting applications specified in /home/dn/.vnc/xstartup
Log file is /home/dn/.vnc/dellr:1.log

then I move to the android tablet, where I run androidVNC (https://play.google.com/store/apps/deta … androidVNC). It asks me to provide the following information:

Nickname: (random name for the connection)
Password: (password specified when launching the vncserver)
Address: What is this? Is it my laptop IP number?
Port: this should be 5901, right?

If use my IP as "Address" i got a timeout error.

What am I doing wrong here?

edit: just tried with tightvnc too but I got the same error

Last edited by Box0 (2013-07-29 12:07:39)

Offline

#2 2013-07-30 09:26:27

84081
Member
Registered: 2013-07-30
Posts: 5

Re: Problem connecting to a vncserver from an android tablet

Address is the IP of your laptop, example:

192.168.1.100

Port may not need to be entered, but you can try with the following examples:

This connects to display number 1, which is the VNC server in your case (dellr:1)

:1

This connects to the actual port, notice the two colons used

::5901

edit:
Stating just port 5901 should work too. I haven't tried the android app myself, so I can't be sure if the above works. They're just regular examples for most VNC clients out there.

Last edited by 84081 (2013-07-30 09:27:52)

Offline

#3 2013-07-30 09:58:29

Box0
Member
From: Italy
Registered: 2011-09-21
Posts: 218

Re: Problem connecting to a vncserver from an android tablet

so my setup is ok. 5901 is also the number entered in the example configuration shown in the android app manual.

However, I still got a timeout error while the client (the android tablet) tries to get an handshake from the server.

What could possibly be wrong? I have no idea where to look for potential errors.

Offline

#4 2013-07-30 10:25:59

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,238
Website

Re: Problem connecting to a vncserver from an android tablet

Is your laptop listening on port 5901?

netstat -tnlp | grep vnc

Are you connecting to the right address and your laptop seeing the traffic?

tcpdump -lnn -i eth0 port 5901

Replace eth0 with the appropriate interface name. Leave that running while you attempt to connect and if the traffic is getting to your laptop, you'll see some output (apart from the startup text). CTRL+C to quit.

We can go from there once you've checked those wink

Offline

#5 2013-07-30 16:26:09

Box0
Member
From: Italy
Registered: 2011-09-21
Posts: 218

Re: Problem connecting to a vncserver from an android tablet

fukawi2 wrote:
netstat -tnlp | grep vnc
tcp        0      0 0.0.0.0:5801            0.0.0.0:*               LISTEN      14863/Xvnc          
tcp        0      0 0.0.0.0:5901            0.0.0.0:*               LISTEN      14863/Xvnc          
tcp        0      0 0.0.0.0:6001            0.0.0.0:*               LISTEN      14863/Xvnc 
fukawi2 wrote:
tcpdump -lnn -i eth0 port 5901

Replace eth0 with the appropriate interface name.

Uhm... could you please elaborate about what the appropriate interface name would be? I'm not sure I understand.

Offline

#6 2013-07-30 23:15:44

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,238
Website

Re: Problem connecting to a vncserver from an android tablet

Well VNC is listening on 5901, so that's a good start smile

Box0 wrote:

Uhm... could you please elaborate about what the appropriate interface name would be? I'm not sure I understand.

Are you using wired or wireless network on your laptop? Wired connections will probably be something like enp3s0 or wireless will be wlan0 I believe (I don't use wireless on Arch)

Check with `ip a s` and look for the interface with the IP Address you're trying to connect to. For example, on the computer I'm on, the interface is eth0 (I still use the "old" naming scheme though):

~ $ ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 1c:6f:65:4e:99:b0 brd ff:ff:ff:ff:ff:ff
    inet 172.21.42.201/24 brd 172.21.42.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 2001:xxxx:xxxx:c642::201/64 scope global 
       valid_lft forever preferred_lft forever

Offline

Board footer

Powered by FluxBB