cant vnc into pi using remmina

[thereisnofood]

hi

i am unable to vnc into my headless pi using remmina on the pandora, it keeps giving me the error "unable to connect to vnc server". i have checked all the ports on my router and they are configured correctly as before i was using remmina to remotely access my desktop computer

i dont believe its the server itself as i can vnc into the pi on my desktop using a host address and my internal ip

thanks

 

[Linux-SWAT]

Maybe the server isn't configured to host two connections at the same time ?

Checked the X server number ?

 

[thereisnofood]

sorry how would i do that 

but i created 2 sessions on the server and managed to connect to both at the same time using my desktop computer so i believe it is capable of hosting two connections at the same time

 

[Linux-SWAT]

Can you ping in both directions ?

 

[thereisnofood]

yes i can ping in both directions

and i can also ssh into my pi 

 

[Linux-SWAT]

Strange.

Some vnc combos can lead to failures, but they are usually more verbose.

No log at all (both sides) ?

 

[thereisnofood]

sorry i dont know how to get log of remmina but here is log of 1 of the sessions frm the server

Spoiler

22/03/13 22:41:54 Xvnc version TightVNC-1.3.9
22/03/13 22:41:54 Copyright © 2000-2007 TightVNC Group
22/03/13 22:41:54 Copyright © 1999 AT&T Laboratories Cambridge
22/03/13 22:41:54 All Rights Reserved.
22/03/13 22:41:54 See http://www.tightvnc.com/ for information on TightVNC
22/03/13 22:41:54 Desktop name 'X' (raspberrypi:2)
22/03/13 22:41:54 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
22/03/13 22:41:54 Listening for VNC connections on TCP port 5902
Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring
Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring
xrdb: No such file or directory
xrdb: can't open file '/home/pi/.Xresources'

22/03/13 22:42:39 Got connection from client 192.168.0.1
22/03/13 22:42:39 Using protocol version 3.8
22/03/13 22:42:39 Enabling TightVNC protocol extensions
22/03/13 22:42:44 Full-control authentication passed by 192.168.0.1
22/03/13 22:42:44 Using tight encoding for client 192.168.0.1
22/03/13 22:42:44 rfbProcessClientNormalMessage: ignoring unknown encoding 16
22/03/13 22:42:44 Using image quality level 6 for client 192.168.0.1
22/03/13 22:42:44 rfbProcessClientNormalMessage: ignoring unknown encoding -223
22/03/13 22:42:44 Enabling LastRect protocol extension for client 192.168.0.1
22/03/13 22:42:44 Enabling cursor position updates for client 192.168.0.1
22/03/13 22:42:44 Enabling full-color cursor updates for client 192.168.0.1
22/03/13 22:42:58 Client 192.168.0.1 gone
22/03/13 22:42:58 Statistics:
22/03/13 22:42:58   key events received 1, pointer events 41
22/03/13 22:42:58   framebuffer updates 10, rectangles 85, bytes 78552
22/03/13 22:42:58     LastRect markers 1, bytes 12
22/03/13 22:42:58     cursor shape updates 1, bytes 684
22/03/13 22:42:58     cursor position updates 1, bytes 12
22/03/13 22:42:58     tight rectangles 82, bytes 77844
22/03/13 22:42:58   raw bytes equivalent 3183288, compression ratio 40.893171

22/03/13 22:55:29 Got connection from client 192.168.0.1
22/03/13 22:55:29 Using protocol version 3.8
22/03/13 22:55:29 Enabling TightVNC protocol extensions
22/03/13 22:55:31 Full-control authentication passed by 192.168.0.1
22/03/13 22:55:31 Using tight encoding for client 192.168.0.1
22/03/13 22:55:31 rfbProcessClientNormalMessage: ignoring unknown encoding 16
22/03/13 22:55:31 Using image quality level 6 for client 192.168.0.1
22/03/13 22:55:31 rfbProcessClientNormalMessage: ignoring unknown encoding -223
22/03/13 22:55:31 Enabling LastRect protocol extension for client 192.168.0.1
22/03/13 22:55:31 Enabling cursor position updates for client 192.168.0.1
22/03/13 22:55:31 Enabling full-color cursor updates for client 192.168.0.1
22/03/13 22:56:28 Client 192.168.0.1 gone
22/03/13 22:56:28 Statistics:
22/03/13 22:56:28   key events received 1, pointer events 416
22/03/13 22:56:28   framebuffer updates 504, rectangles 1180, bytes 343491
22/03/13 22:56:28     LastRect markers 35, bytes 420
22/03/13 22:56:28     cursor shape updates 13, bytes 9916
22/03/13 22:56:28     cursor position updates 1, bytes 12
22/03/13 22:56:28     tight rectangles 1131, bytes 333143
22/03/13 22:56:28   raw bytes equivalent 15134484, compression ratio 45.429392

both of those connections were from desktop, pandora connection is not even there

 

[Linux-SWAT]

Try in remmina window:

help -> debug

 

[thereisnofood]

no such option it seems

is there another way to get the log?

 

[Linux-SWAT]

No idea :/ .

 

[thereisnofood]

Ahh no worries thanks for helping out.


I managed to vnc through my iphone, I think i may have found the issue, when I enter the sever address on desktop or phone I can enter the port number with a :: after the address followed by desired port. when a new session is created on server it listens on a different port as opposed to 5900 but rather 5901. there is no option to edit the port in remmina and adding it at the end of the addrss does not work.how would I change the port?

 

[Linux-SWAT]

IP:0

IP:1

e.g.:

192.168.2.3:0

 

[thereisnofood]

it worked. thank you !!