The core of the info at the website is for redhat. The only differences for SuSE should be file locations like the path to Xvnc. Currently I don't have SuSE available to check for details.
1. if I use vncviewer it asks for the server and the display number. Which display number is it?
If you read the instruction and know what you're doing, read the /etc/services file and find a combination of portnumber and vncserver geometry. The display number to use with vncviewer is (portnumber - 5900) hence: To use the vncserver at port 5950 (640x480 with 256 colors): vncviewer machine:50. For 800x600 at 16 bits colors: vncviewer machine:61. For 1600x1200 with 32 bits colors: vncviewer machine:5984.
OK!
2. I start Xvnc with the script that comes with it vncserver. It seems that this one already defined the screen password (as I use it right now)
This vncserver script starts an Xvnc at portnumbers from 5900 + displaynumber. where 5800+display must be free for the webserver and 6000+display must be free for the X11 communication.
do NOT use the script as a replacement for Xvnc in the configuration!
Where do I configure it? and start without the script? (See below what I did so far)
3. Now I get this ugly wm screen, with the setup from above I think I will get kde, right???
If you followed the entire setup at the website, then you should get a vnc-password free vncserver (no need to give an vncviewer password) and in there a login screen as if at the local display. Somehow the uggly screen tells me you used the vncserver script to start this particular Xvnc.
Let's check what I have done:
1) Install VNC
a) if installed to directory other than /usr/local/bin, edit the vnc paths in the 'vncserver.*' files (the ones used in the page below).
done!
2) edit 'xdm-config' and comment out the line '! DisplayManager.requestPort: 0' (should be the last line)
a) RedHat 6.2, 7.1, 7.2 - '/etc/X11/xdm/xdm-config'
done!
3) edit 'kdmrc' and enable XDMCP on port 177 (if kde is new enough)
a) RedHat 7.2 - '/etc/kde/kdm/kdmrc'
In SuSE it is in /opt/kde2/share/config/kdm/kdmrc:
[Xdmcp]
Enable=1
Xaccess=/var/X11R6/lib/xdm/Xaccess
Willing=/var/X11R6/lib/scm/Xwilling
Port=177
b) If running Gnome as your desktop, start gdmconfig, select Expert Mode, ensure that Enable XDMCP is checked. (You must be logged in as root)
I don't use Gnome
4) edit Xaccess and uncomment the line '* #any host can get a login window'
a) RedHat 6.2, 7.1, 7.2 -' /etc/X11/xdm/Xaccess'
*
done!
5) append contents of 'services.inetd' to 'services'
a) Linux - '/etc/services'
done!
6) Update inetd configuration for the services to enable (based on /etc/services)
a) inetd - append contents of 'vncserver.inetd' to '/etc/inetd.conf'
done!
b) xinetd - copy 'vncserver.xinetd' to '/etc/xinetd.d' (RH 7.2 (not available in my RH6.2)
I don't use xinetd now.
7) reboot (or restart inetd/xinetd and xdm or equivalent)
a) xdm i) Running KDM, to restart, killall kdm
ii) Running GDM, to restart, killall gdm
b) xinet i) RedHat 7.1/7.2 - '/etc/init.d/xinet restart'
a. kill all Xvnc sessions
b. remove all /tmp/.X11-unix/X1... and /tmp/.X1-lock ... files
c. on the server CTR-ALT-Back to restart the X server (startx)
Test vncviewer to the server ==> No answer
Debugging your connection to VNC.
1. If you find you cannot connect, this could be a few things. Ensure that the path in your inetd.conf and xinetd.d point to the same place as your actual vnc executables.
inetd.conf points to /usr/local/bin/Xvnc (correct)
2. See if your Xvnc is running. From a remote machine, telnet to the machine hosting VNC, using the full port number you have defined in your services file. In this case, an example would be port 5951. (This would test the VNC for 800x600x8). If no response, you may not be on the same subnet, or you have a firewall in the way. The normal response would be rubbish, but it proves that you have an open port to connect to.
telnet www.elmit.com:5953
Name or service not known: No such file or directory
(Firewall has the ports 5950 ~ 5990/tcp and 177/udp open)
3. Test if your XDMCP is running. This uses port 177, but uses UDP, so telnet will not work against it. You can use something like nmap http://www.insecure.org/nmap/ to test this port. The command line would be:
nmap -sU -p 177 hostname (change the hostname to suit your system).
Port
177/udp
(ok!)
BUT:
nmap -sT -p 5950-5990
Starting nmap V. 2.54BETA34 ( www.insecure.org/nmap/ )
Interesting ports on dns.elmit.com (192.168.250.254):
(The 36 ports scanned but not shown below are in state: closed)
Port State Service
5950/tcp open unknown
5951/tcp open unknown
5952/tcp open unknown
5953/tcp open unknown
5954/tcp open unknown
Nmap run completed -- 1 IP address (1 host up) scanned in 0 seconds
Any idea ???
You can also use nmap to test your regular vnc ports. If not running, check part 3 of the configuration instructions.
bye
Ronald
- bye
- Ronald
- Ronald Wiplinger
- Bright Networking Inc.
- 7F, 192-1, Sec. 3, Tatung Rd., Shijr City, Taipei, Taiwan, RoC
- Tel.: +886 2 8647-1685, Mobile +886 915 653-452, Fax: +886 2 8647-2002
**************************************************************
Scanned by eScan Content-Security and Anti-Virus Software.
Visit http://www.mwti.net for more info on eScan and MailScan.
**************************************************************
**************************************************************
Scanned by eScan Content-Security and Anti-Virus Software.
Visit http://www.mwti.net for more info on eScan and MailScan.
**************************************************************
**************************************************************
Scanned by eScan Content-Security and Anti-Virus Software.
Visit http://www.mwti.net for more info on eScan and MailScan.
**************************************************************
**************************************************************
Scanned by eScan Content-Security and Anti-Virus Software.
Visit http://www.mwti.net for more info on eScan and MailScan.
**************************************************************
