I will try tomorrow, now I can only connect via ssh or vpn.
Thanks.
No, I still get the black windows.
jbuchmann@srv02:~> vncviewer 127.0.0.1:5901
Connected to RFB server, using protocol version 3.7
Enabling TightVNC protocol extensions
No authentication needed
Desktop name “nobody’s x11 desktop (srv02:1)”
VNC server default format:
16 bits per pixel.
Least significant byte first in each pixel.
True colour: max red 31 green 63 blue 31, shift red 11 green 5 blue 0
Warning: Cannot convert string “--helvetica-bold-r---16-------” to type FontStruct
Using default colormap which is TrueColor. Pixel format:
32 bits per pixel.
Least significant byte first in each pixel.
True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
ShmCleanup called
Using shared memory PutImage
Same machine: preferring raw encoding
ShmCleanup called
Firstly I didn’t know you could put in the port number like this:
vncviewer <host>:port
I thought the syntax is
vncviewer <host>::port
which would be equivalent to
vncviewer <host>:$((port - 5900))
But it seems to work here, so I guess we all learn something new everyday.
Getting back to the main problem, I think the issue is that you use GDM as the greeter whereas I use KDM. The two may have different security setups, although I am not an expert on this. The results of your test means that GDM is not interested in establishing a remote connection to a client or something is preventing GDM from doing so.
Now my new theory is that it is something to do with whether XDMCP is allowed or not. For me, XDMCP is enabled by default in KDM, when I elect to allow Remote Administration.
Trawling the Internet, I came across this interesting piece about GDM and VNC, where he specifically has to allow XDMCP in the GDM configuration file, for VNC to work:
You might care to check yours to see if there is any reference to XDMCP in it.
There are three main greeters / display managers one could use: XDM, KDM and GDM. The first, XDM, which is very basic, also requires you to set an XDMCP flag for remote connections to be allowed. So it looks as though that is the problem at the moment.
Give it a whirl and see what happens. The business with the ambiguity in the localhost definitions still needs to be corrected of course.
Hope this helps yet again.
My bug was closed and marked as a duplicate of bug 623254, which is still under investigation. A patch was provided a while back, but apparently it didn’t resolve the issue. I will keep monitoring it.
I may try the patch anyway when I have a chance to see if it resolves it for me.
Bug 623254 covers a problem where GDM on a remote system does not respond. This affects VNC and Xnest. It is still under investigation.
There is also Bug 591664, which covers a generic problem in X when talking to localhost (and Xvnc on the remote machine talks to the display manager via localhost). It should be fixed by the yet-to-be-release update to xorg-x11-server-extra (look for a Jul 08 2010 Changelog entry “Fix some shortcomings in the xdmcp implementation.”)
Not a generic problem with X and localhost, “only” the specific problem that the X server (including Xnest and Xvnc) skips loopback addresses when it builds the list of potential display addresses to report to the display manager via xdmcp, even when the dm is reached via a loopback address.
It should be fixed by the yet-to-be-release update to xorg-x11-server-extra (look for a Jul 08 2010 Changelog entry “Fix some shortcomings in the xdmcp implementation.”)
Until we’ve officialy released this update, the patched packages (xorg-x11-server, xorg-x11-Xvnc and xorg-x11-server-extra) can be found in the build service.
Sorry, I meant generic in respect to the display manager. It isn’t specific to GDM.
I’ve also been experiencing this problem. It appears both during upgrades from opensuse 11.1 as well as fresh install. The only system I’m using 11.3 on has is using the unichrome drivers.
For what it’s worth, running vncserver from the command line and connecting to that works just fine. I suspect the problem is somewhere in the X11 configuration and how GDM/VNC are interacting with it. I have yet to try installing a system with KDE but that may be my next troubleshooting step.
So no, you aren’t crazy and the problem isn’t simply a misconfiguration on your part.
I have KDE on 11.3 and 11.2 systems using unichrome/openchrome drivers (shouldn’t be the problem) with VNC (vncserver) running. I can connect into either system from another 11.3 KDE system (upgraded from 11.2) via the internet, using vncviewer or KRDC as client both work.
start vncserver as a user other than root and try and connect.
how do i connect windows server 2008 from remote access
Connect TO windows 2008? or from windows 2008? The way you asked is confusing.
Connecting from is what this whole thread is about.
Connecting to w2k8 can be done with rdesktop.
Did you activate XDM for Xvnc?
cat /etc/X11/xdm/xdm-config
…
! SECURITY: do not listen for XDMCP or Chooser requests
! Comment out this line if you want to manage X terminals with xdm
!
DisplayManager.requestPort: 0
I think I might have sussed it.
I’ve been having the same problem suddenly started on one machine - another has worked fine - both on 11.3 with kde
After a bit of related research in trying to fix an sshd login delay, I found that adding :
UseDNS no
to /etc/ssh/sshd_config
and then doing a /etc/init.d/ssh restart
cured my ssh login delays and vnc worked again in all it’s 24bit, 1280x1024 glory.
I’m fairly sure it’s something to do with reverse dns resolution.
Hope this helps
Darren Hawkshaw
There is a easy way to fix temporary this problem:
uncomment the loopback-Address in the IPv6-section of /etc/hosts-file
#::1 localhost ipv6-localhost ipv6-loopback
restart the network
try vncviewer - it will works fine with the correct XDM
On 2010-08-15, pschulze59 <pschulze59@no-mx.forums.opensuse.org> wrote:
>
> There is a easy way to fix temporary this problem:
>
> uncomment the loopback-Address in the IPv6-section of /etc/hosts-file
> #::1 localhost ipv6-localhost ipv6-loopback
> restart the network
> try vncviewer - it will works fine with the correct XDM
You mean comment, not uncomment, don’t you ?
That’s what worked for me: commenting OUT this ipV6 line.
–
When in doubt, use brute force.
– Ken Thompson
Neither standard gnome nor kde install works form me. I’ve tried out by commenting the ipv6 lines, making a number of other adjustments and nope!
Also tried from uvnc and realvnc on windows and tightvnc on both.
I’ll let you know if someday I can see my vncserver!
Today I installed the released patch for x11-Xorg-server that supposed to fix this. Sadly I have to say that didn’t work for me. Any news about you?
Thanks!
Hello.
I’ve been trying to make Xvnc to work on openSuse 11.3 too. I’ve tried commenting out all ipv6 entries from /etc/hosts and went even as far as disabling ipv6 altogether from network settings. Now, if I look at the output of ifconfig I can see that the ‘lo’ interface doesn’t event have ipv6 address specified. I was also waiting for the recent xorg-x11-Xvnc update to fix this, but it didn’t.
xorg-x11-* 7.5_1.8.0-10.3.1 does not work for me either. I’m using gdm.