Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
How to turn your box into a Xvnc Terminal Server
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... 5, 6, 7 ... 15, 16, 17  Next  
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
tecknojunky
Veteran
Veteran


Joined: 19 Oct 2002
Posts: 1937
Location: Montréal

PostPosted: Thu Jan 15, 2004 6:32 am    Post subject: Reply with quote

vdboor wrote:
But I want to add a password to my vnc session. Seriously. I don't want people to open my gdm login if they connect. :( ..is this possible?
Quote:

BUGS
There are many security problems in current Xvnc implementation. It's recommended
to restrict network access to Xvnc servers from untrusted network adresses. Proba-
bly, the best way to secure Xvnc server is to allow only loopback connections from
the server machine (the -localhost option) and to use SSH tunneling for remote
access to the Xvnc server. For details on SSH tunneling, see
<URL:http://www.uk.research.att.com/vnc/sshvnc.html> .
You could do just that, limit access from the localhost. In this fashion, only users who can login from the outside with ssh could forward the port to localhost:59xx to use vnc.

I've been using vnc for years to access both Windows and X desktops from the outside and I always done it thrue a ssh tunnel. Works like a charm.
_________________
(7 of 9) Installing star-trek/species-8.4.7.2::talax.
Back to top
View user's profile Send private message
ElectricHead1
n00b
n00b


Joined: 29 Oct 2003
Posts: 20
Location: The Netherlands

PostPosted: Thu Jan 15, 2004 12:37 pm    Post subject: Reply with quote

OK .... I've got the following problem. I can run a vncserver without any problems from my Gentoo box and open it with both tightvncviewer and realvnc.

Now the following happens:

I have disabled XDM at startup.
What happens that as soon as I start XDM, and try to connect to 192.168.1.4:71, I get the following error message from the viewer "ReadExact: Socket error while reading error." :?:

When I first tried it, I got that nice and familiar Grey screen with the X mouse cursor that more of you guys have experienced. And now it changed to this state .... All settings are the same as in the tutorial that was presented here.

Anybody have any ideas??? Thanks in advance
Back to top
View user's profile Send private message
ElectricHead1
n00b
n00b


Joined: 29 Oct 2003
Posts: 20
Location: The Netherlands

PostPosted: Thu Jan 15, 2004 12:42 pm    Post subject: Reply with quote

geoffwa wrote:
@people with the KDE problem

Just append :1 to the front of the Xvnc args line to get Xvnc to start from display 1 rather than display 0.

This happens when Xvnc tries to open display 0 which is 'supposed' to the be the console display and a whole heap of crap in Xsetup_0 gets executed which seems to be dependent on KDE being installed (aiee)

[edit]

Appending :1 just mangled the IP address for some weird reason, instead I just deleted console = display 0 line in Xservers to allow Xvnc to use all the available consoles.


And where can I find thos Xvnc args??
Back to top
View user's profile Send private message
vdboor
Guru
Guru


Joined: 03 Dec 2003
Posts: 592
Location: The Netherlands

PostPosted: Thu Jan 15, 2004 3:26 pm    Post subject: Reply with quote

update: this was fixed, when I enabled 'AllowTcpForwarding' in sshd_config.. :)

tecknojunky wrote:
You could do just that, limit access from the localhost. In this fashion, only users who can login from the outside with ssh could forward the port to localhost:59xx to use vnc.

I've been using vnc for years to access both Windows and X desktops from the outside and I always done it thrue a ssh tunnel. Works like a charm.


I've very curious how this works.. :?

I'm currently at a Windows 2000 machine, and I'm using PuTTY for ssh access. I've added the tunnel, and the Windows 2000 machine is indeed listening at 127.0.0.1:59xx. The vncviewer application doesn't work however. With tcpdump I noticed that my Linux machine doesn't receive any packets at the vnc port.

...but the strangest thing of this story: If I run telnet at the Windows 2000 machine, the connection closes immediately, and enters the WAIT_CLOSE state. 8O

please help :(
_________________
The best way to accelerate a windows server is by 9.81M/S²
Linux user #311670 and Yet Another Perl Programmer

[ screenies | Coding on KMess ]


Last edited by vdboor on Fri Jan 16, 2004 12:14 pm; edited 1 time in total
Back to top
View user's profile Send private message
=sasha=
n00b
n00b


Joined: 05 Mar 2003
Posts: 52

PostPosted: Thu Jan 15, 2004 5:58 pm    Post subject: *FAST* realvnc based solution Reply with quote

I found another, much simplier and faster way to use vnc protocol.
Solution is based on latest realvnc (still beta, but it works).

After you compile realvnc 4.x source, you should:

0. stop xdm, kdm, gdm, whatever
1. Place vnc.so to /usr/X11R6/lib/modules/extensions/
2. Edit XF86Config and add
Load "vnc"
to module section
3. start x again

After that you should be able to connect with any vnc viewer. I use it on LAN and its blazing fast (because vncserver is working by not grabbings screens).

I think betavnc is not in portage yet. Go to www.realvnc.com for source.
Back to top
View user's profile Send private message
tecknojunky
Veteran
Veteran


Joined: 19 Oct 2002
Posts: 1937
Location: Montréal

PostPosted: Thu Jan 15, 2004 8:15 pm    Post subject: Reply with quote

vdboor wrote:
tecknojunky wrote:
You could do just that, limit access from the localhost. In this fashion, only users who can login from the outside with ssh could forward the port to localhost:59xx to use vnc.

I've been using vnc for years to access both Windows and X desktops from the outside and I always done it thrue a ssh tunnel. Works like a charm.


I've very curious how this works.. :?

I'm currently at a Windows 2000 machine, and I'm using PuTTY for ssh access. I've added the tunnel, and the Windows 2000 machine is indeed listening at 127.0.0.1:59xx. The vncviewer application doesn't work however. With tcpdump I noticed that my Linux machine doesn't receive any packets at the vnc port.

...but the strangest thing of this story: If I run telnet at the Windows 2000 machine, the connection closes immediately, and enters the WAIT_CLOSE state. 8O

please help :(
http://freesco.no-ip.org/VNC/, with screenshots and all.
_________________
(7 of 9) Installing star-trek/species-8.4.7.2::talax.
Back to top
View user's profile Send private message
tecknojunky
Veteran
Veteran


Joined: 19 Oct 2002
Posts: 1937
Location: Montréal

PostPosted: Thu Jan 15, 2004 8:20 pm    Post subject: Re: *FAST* realvnc based solution Reply with quote

=sasha= wrote:
I found another, much simplier and faster way to use vnc protocol.
Solution is based on latest realvnc (still beta, but it works).

After you compile realvnc 4.x source, you should:

0. stop xdm, kdm, gdm, whatever
1. Place vnc.so to /usr/X11R6/lib/modules/extensions/
2. Edit XF86Config and add
Load "vnc"
to module section
3. start x again

After that you should be able to connect with any vnc viewer. I use it on LAN and its blazing fast (because vncserver is working by not grabbings screens).

I think betavnc is not in portage yet. Go to www.realvnc.com for source.
Interresting in deed. Can you still control access (from localhost or locallan) and does the java viewer also works in this fashion?
_________________
(7 of 9) Installing star-trek/species-8.4.7.2::talax.
Back to top
View user's profile Send private message
ttw22
n00b
n00b


Joined: 06 Jan 2004
Posts: 3

PostPosted: Fri Jan 16, 2004 4:08 am    Post subject: Reply with quote

I had the grey screen problem too, the solution for me was to just run "gdm" again, even though I thought it was running.
Back to top
View user's profile Send private message
vdboor
Guru
Guru


Joined: 03 Dec 2003
Posts: 592
Location: The Netherlands

PostPosted: Fri Jan 16, 2004 12:15 pm    Post subject: Reply with quote

tecknojunky wrote:
vdboor wrote:

I've very curious how this works.. :?

I'm currently at a Windows 2000 machine, and I'm using PuTTY for ssh access. I've added the tunnel, and the Windows 2000 machine is indeed listening at 127.0.0.1:59xx. The vncviewer application doesn't work however. With tcpdump I noticed that my Linux machine doesn't receive any packets at the vnc port.

...but the strangest thing of this story: If I run telnet at the Windows 2000 machine, the connection closes immediately, and enters the WAIT_CLOSE state. 8O

please help :(
http://freesco.no-ip.org/VNC/, with screenshots and all.


I've found a way to fix it. I had to enable AllowTCPForwarding in my sshd_config file. :x :!:
_________________
The best way to accelerate a windows server is by 9.81M/S²
Linux user #311670 and Yet Another Perl Programmer

[ screenies | Coding on KMess ]
Back to top
View user's profile Send private message
Braindead_One
n00b
n00b


Joined: 13 Jan 2004
Posts: 4

PostPosted: Tue Jan 20, 2004 12:49 pm    Post subject: Reply with quote

To those with the infamous grey screen problem: try checking your firewall settings. I my case kdm didn't work because the ip of eth0 was not allowed to connect to the xdmcp-port (the ip i was connecting to (eth0:1) was).
Also check if localhost is allowed to connect.

Hope this helps

Braindead_One
Back to top
View user's profile Send private message
clocKwize
n00b
n00b


Joined: 04 Jan 2004
Posts: 14

PostPosted: Fri Jan 30, 2004 7:11 pm    Post subject: Reply with quote

this howto is great :) worked like a charm, i was just wondering, for added security, can i put a password on vnc some how as well?
Back to top
View user's profile Send private message
rrrkkkttt
Tux's lil' helper
Tux's lil' helper


Joined: 02 Oct 2003
Posts: 96

PostPosted: Mon Feb 02, 2004 9:23 am    Post subject: Reply with quote

I followed all of the steps and I get the grey screen... I replaced the last line in xstartup with /etc/X11/Sessions/Gnome... I still get the grey screen when I start vncviewer... I can ssh into my comp remotely but for some reason cannot forward X11 connection... However, locally when i type http://localhost:5801/ I get an applet and when I enter my password tightvnc works and I see my gnome session... I've forwarded ports 177 UDP for gdm and 5980 to 5984 tcp for tightvnc appropriately... yeah i rebooted lots of times to see if it'd work... but no go.... i'd appreciate it if someone can please help me get tightvnc to work...
Back to top
View user's profile Send private message
rrrkkkttt
Tux's lil' helper
Tux's lil' helper


Joined: 02 Oct 2003
Posts: 96

PostPosted: Mon Feb 02, 2004 11:47 am    Post subject: Reply with quote

nm i got it working now... gdm doesn't work at all... i put /etc/X11/Sessions/fluxbox and I get a fluxbox session... the prob was that when i ran vncserver the output told me that the Xdisplay was running on myhost:1... so instead of vncviewer localhost:71, I did vncviewer myhost:1 and it works! ...
Back to top
View user's profile Send private message
vdboor
Guru
Guru


Joined: 03 Dec 2003
Posts: 592
Location: The Netherlands

PostPosted: Mon Feb 02, 2004 1:55 pm    Post subject: Reply with quote

clocKwize wrote:
this howto is great :) worked like a charm, i was just wondering, for added security, can i put a password on vnc some how as well?


I found an rfbauth option in the Xvnc server parameters. It's a bit hidden, and not very well explaind in the manuals, but I think this is what you're looking for :)

the parameter-value should point to your .vnc/passwd file. Just don't use your system password in that file. The passwords seam to be hashed with a very simple algorithm. (the file contains jus a few bytes.. :?)
_________________
The best way to accelerate a windows server is by 9.81M/S²
Linux user #311670 and Yet Another Perl Programmer

[ screenies | Coding on KMess ]
Back to top
View user's profile Send private message
clocKwize
n00b
n00b


Joined: 04 Jan 2004
Posts: 14

PostPosted: Mon Feb 02, 2004 2:37 pm    Post subject: Reply with quote

ah, thanks very much :D
Back to top
View user's profile Send private message
rrrkkkttt
Tux's lil' helper
Tux's lil' helper


Joined: 02 Oct 2003
Posts: 96

PostPosted: Mon Feb 02, 2004 9:06 pm    Post subject: Reply with quote

i just noticed another problem... whenever i get a gnome or fluxbox session all of the apps are all gtk... i tried running gnome-settings-daemon in the tightvnc session but it says its already running... how do I get my apps to use gtk2 and also use the fonts?
Back to top
View user's profile Send private message
vdboor
Guru
Guru


Joined: 03 Dec 2003
Posts: 592
Location: The Netherlands

PostPosted: Mon Feb 02, 2004 10:15 pm    Post subject: Reply with quote

rrrkkkttt wrote:
i just noticed another problem... whenever i get a gnome or fluxbox session all of the apps are all gtk... i tried running gnome-settings-daemon in the tightvnc session but it says its already running... how do I get my apps to use gtk2 and also use the fonts?


well, off course all your gtk applications are gtk, but I think I understand what you're trying to say; the theme isn't the one you'd expected.

You can copy the .gtk-... files to the home directory of the vnc user. the gtkrc files are read by everty gtk-based application before it starts.
_________________
The best way to accelerate a windows server is by 9.81M/S²
Linux user #311670 and Yet Another Perl Programmer

[ screenies | Coding on KMess ]
Back to top
View user's profile Send private message
rrrkkkttt
Tux's lil' helper
Tux's lil' helper


Joined: 02 Oct 2003
Posts: 96

PostPosted: Wed Feb 04, 2004 7:48 am    Post subject: Reply with quote

I never tried to log in as a different user in vnc... I typed vncviewer logged in as a user... i tried vncserver as root but it gives me an error saying it couldn't find xauth on my PATH... how do I log in as a different user in vnc?

if i'm already logged on as a user in gentoo and i start vncviewer as that user... then i already have all the gtk files in my home directory... so then shouldn't the gtk2 apps read those .gtkrc files?
Back to top
View user's profile Send private message
vdboor
Guru
Guru


Joined: 03 Dec 2003
Posts: 592
Location: The Netherlands

PostPosted: Wed Feb 04, 2004 5:37 pm    Post subject: Reply with quote

rrrkkkttt wrote:
I tried vncserver as root but it gives me an error saying it couldn't find xauth on my PATH... how do I log in as a different user in vnc?

You should run the Xvnc through inetd/xinetd, like this toturial suggests.

If you run the vncserver, it will run as your current user. Type "ps auxf" to see all processes running.. and you'll see that vnc is running as the user logged in.

If you "su" to another user, you might want to run "source /etc/profile" first. This also upgrades your $PATH. An alternative, is using "su -" to start a login process.
_________________
The best way to accelerate a windows server is by 9.81M/S²
Linux user #311670 and Yet Another Perl Programmer

[ screenies | Coding on KMess ]
Back to top
View user's profile Send private message
rrrkkkttt
Tux's lil' helper
Tux's lil' helper


Joined: 02 Oct 2003
Posts: 96

PostPosted: Thu Feb 05, 2004 3:40 am    Post subject: Reply with quote

oh i get it... the xvncserver file in /etc/xinetd.d .... when i do /etc/init.d/xinetd start the vnc server also starts up then i just restart gdm by logging out and logging back in... then i do localhost:71...

ok i tried that... but its not working... now I don't even get the grey screen... i get a connection refused error and unable to connect to server... i think that xinetd is not starting up all the vncservers... unless i start up the vncserver as the user that i'm logged on as... i cannot use vncviewer...
Back to top
View user's profile Send private message
vdboor
Guru
Guru


Joined: 03 Dec 2003
Posts: 592
Location: The Netherlands

PostPosted: Thu Feb 05, 2004 8:45 am    Post subject: Reply with quote

rrrkkkttt wrote:
oh i get it... the xvncserver file in /etc/xinetd.d .... when i do /etc/init.d/xinetd start the vnc server also starts up then i just restart gdm by logging out and logging back in... then i do localhost:71...

ok i tried that... but its not working... now I don't even get the grey screen... i get a connection refused error and unable to connect to server... i think that xinetd is not starting up all the vncservers... unless i start up the vncserver as the user that i'm logged on as... i cannot use vncviewer...


I never thought I would say something like RTFM, because I don't like this word., but... please... read the tutorial again! 8O

Basically you're asking how to run Xvnc through xinetd, and this is exactly what the topic starter just explained... :roll: lol
_________________
The best way to accelerate a windows server is by 9.81M/S²
Linux user #311670 and Yet Another Perl Programmer

[ screenies | Coding on KMess ]
Back to top
View user's profile Send private message
clocKwize
n00b
n00b


Joined: 04 Jan 2004
Posts: 14

PostPosted: Thu Feb 05, 2004 10:05 am    Post subject: Reply with quote

even if you dont understand it properly, just run the commands it says to and it *should* work
Back to top
View user's profile Send private message
rrrkkkttt
Tux's lil' helper
Tux's lil' helper


Joined: 02 Oct 2003
Posts: 96

PostPosted: Fri Feb 06, 2004 4:12 am    Post subject: Reply with quote

yeah i did read the tutorial... and I did follow all the steps he posted but its still not working... it only works if I start vncserver as a user...

here's /etc/xinetd.conf:
Quote:

# Sample configuration file for xinetd

defaults
{
# only_from = localhost
instances = 60
log_type = SYSLOG authpriv info
log_on_success = HOST PID
log_on_failure = HOST
cps = 25 30
}

includedir /etc/xinetd.d


here's /etc/X11/xdm/xdm-config:
Quote:

! $Xorg: xdm-conf.cpp,v 1.3 2000/08/17 19:54:17 cpqbld Exp $
!
!
!
!
! $XFree86: xc/programs/xdm/config/xdm-conf.cpp,v 1.10 2002/11/30 19:11:32 herrb Exp $
!
DisplayManager.errorLogFile: /var/log/xdm.log
DisplayManager.pidFile: /var/run/xdm.pid
DisplayManager.keyFile: /etc/X11/xdm/xdm-keys
DisplayManager.servers: /etc/X11/xdm/Xservers
DisplayManager.accessFile: /etc/X11/xdm/Xaccess
DisplayManager.willing: su nobody -c /etc/X11/xdm/Xwilling
! All displays should use authorization, but we cannot be sure
! X terminals may not be configured that way, so they will require
! individual resource settings.
DisplayManager*authorize: true
! The following three resources set up display :0 as the console.
DisplayManager._0.setup: /etc/X11/xdm/Xsetup_0
DisplayManager._0.startup: /etc/X11/xdm/GiveConsole
DisplayManager._0.reset: /etc/X11/xdm/TakeConsole
!
DisplayManager*resources: /etc/X11/xdm/Xresources
DisplayManager*session: /etc/X11/xdm/Xsession
DisplayManager*authComplain: true



! 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


here's gdm config:
Quote:

# GDM Configuration file. You can use gdmsetup program to graphically
# edit this, or you can optionally just edit this file by hand. Note that
# gdmsetup does not tweak every option here, just the ones most users
# would care about. Rest is for special setups and distro specific
# tweaks. If you edit this file, you should send the HUP or USR1 signal to
# the daemon so that it restarts: (Assuming you have not changed PidFile)
# kill -USR1 `cat /var/run/gdm.pid`
# (HUP will make gdm restart immediately while USR1 will make gdm not kill
# existing sessions and will only restart gdm after all users log out)
#
# You can also use the gdm-restart and gdm-safe-restart scripts which just
# do the above for you.
#
# Have fun! - George

[daemon]
# Automatic login, if true the first local screen will automatically logged
# in as user as set with AutomaticLogin key.
AutomaticLoginEnable=false
AutomaticLogin=
# Timed login, useful for kiosks. Log in a certain user after a certain
# amount of time
TimedLoginEnable=false
TimedLogin=
TimedLoginDelay=30
# A comma separated list of users that will be logged in without having
# to authenticate on local screens (not over xdmcp). Note that 'root'
# is ignored and will always have to authenticate.
LocalNoPasswordUsers=
# If you are having trouble with using a single server for a long time and
# want gdm to kill/restart the server, turn this on
# Note: I've made this default to true now because there seem to be some
# issues ranging from some things not being reset in the X server to
# pam issues with the slave. It is likely that this feature may be removed
# in the future and we're always going to do server restarts.
AlwaysRestartServer=true
# The gdm configuration program that is run from the login screen, you should
# probably leave this alone
Configurator=/usr/bin/gdmsetup --disable-sound --disable-crash-dialog
GnomeDefaultSession=/usr/share/gnome/default.session
# The chooser program. Must output the chosen host on stdout, probably you
# should leave this alone
Chooser=/usr/bin/gdmchooser
# Default path to set. The profile scripts will likely override this
DefaultPath=/bin:/usr/bin:/usr/X11R6/bin:/usr/X11R6/bin:/usr/local/bin:/usr/bin
# Default path for root. The profile scripts will likely override this
RootPath=/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/X11R6/bin:/usr/local/bin:/usr/bin
DisplayInitDir=/etc/X11/gdm/Init
# Greeter for local (non-xdmcp) logins. Change gdmlogin to gdmgreeter to
# get the new graphical greeter.
Greeter=/usr/bin/gdmgreeter
# Greeter for xdmcp logins, usually you want a less graphically intensive
# greeter here so it's better to leave this with gdmlogin
RemoteGreeter=/usr/bin/gdmgreeter
# User and group that gdm should run as. Probably should be gdm and gdm and
# you should create these user and group. Anyone found running this as
# someone too privilaged will get a kick in the ass. This should have
# access to only the gdm directories and files.
User=gdm
Group=gdm
# To try to kill all clients started at greeter time or in the Init script.
# doesn't always work, only if those clients have a window of their own
KillInitClients=true
LogDir=/var/lib/gdm
# You should probably never change this value unless you have a weird setup
PidFile=/var/run/gdm.pid
PostSessionScriptDir=/etc/X11/gdm/PostSession/
PreSessionScriptDir=/etc/X11/gdm/PreSession/
# Distributions: If you have some script that runs an X server in say
# VGA mode, allowing a login, could you please send it to me?
FailsafeXServer=
# if X keeps crashing on us we run this script. The default one does a bunch
# of cool stuff to figure out what to tell the user and such and can
# run an X configuration program.
XKeepsCrashing=/etc/X11/gdm/XKeepsCrashing
# Reboot, Halt and suspend commands, you can add different commands
# separated by a semicolon and gdm will use the first one it can find
RebootCommand=/sbin/shutdown -r now;/usr/sbin/shutdown -r now
HaltCommand=/usr/bin/poweroff;/sbin/poweroff;/sbin/shutdown -h now;/usr/sbin/shutdown -h now
SuspendCommand=
# Probably should not touch the below this is the standard setup
ServAuthDir=/var/lib/gdm
SessionDir=/etc/X11/gdm/Sessions/
# Better leave this blank and HOME will be used. You can use syntax ~/ below
# to indicate home directory of the user
UserAuthDir=
# Fallback if home directory not writable
UserAuthFBDir=/tmp
UserAuthFile=.Xauthority
# The X server to use if we can't figure out what else to run.
StandardXServer=/usr/X11R6/bin/X
# The maximum number of flexible X servers to run.
FlexibleXServers=5
# the X nest command
Xnest=/usr/X11R6/bin/Xnest -audit 0 -name Xnest
# Automatic VT allocation. Right now only works on Linux. This way
# we force X to use specific vts. turn VTAllocation to false if this
# is causing problems.
FirstVT=7
VTAllocation=true

[security]
# If any distributions ship with this one off, they should be shot
# this is only local, so it's only for say kiosk use, when you
# want to minimize possibility of breakin
AllowRoot=true
# If you want to be paranoid, turn this one off
AllowRemoteRoot=false
# This will allow remote timed login
AllowRemoteAutoLogin=true
# 0 is the most anal, 1 allows group write permissions, 2 allows all write permissions
RelaxPermissions=0
RetryDelay=3
# Maximum size of a file we wish to read. This makes it hard for a user to DoS us
# by using a large file.
UserMaxFile=65536
# Maximum size of the session file. This is larger because it matters less as we
# never keep it all in memory. Just has an upper limit so that we don't go into too
# long of a loop
SessionMaxFile=524388

# XDMCP is the protocol that allows remote login. If you want to log into
# gdm remotely (I'd never turn this on on open network, use ssh for such
# remote usage that). You can then run X with -query <thishost> to log in,
# or -indirect <thishost> to run a chooser. Look for the 'Terminal' server
# type at the bottom of this config file.
[xdmcp]
# Distributions: Ship with this off. It is never a safe thing to leave
# out on the net. Alternatively you can set up /etc/hosts.allow and
# /etc/hosts.deny to only allow say local access.
Enable=true
# Honour indirect queries, we run a chooser for these, and then redirect
# the user to the chosen host. Otherwise we just log the user in locally.
HonorIndirect=true
# Maximum pending requests
MaxPending=4
MaxPendingIndirect=4
# Maximum open XDMCP sessions at any point in time
MaxSessions=16
# Maximum wait times
MaxWait=15
MaxWaitIndirect=15
# How many times can a person log in from a single host. Usually better to
# keep low to fend off DoS attacks by running many logins from a single
# host. This is now set at 2 since if the server crashes then gdm doesn't
# know for some time and wouldn't allow another session.
DisplaysPerHost=2
# The number of minutes after which a non-responsive session is logged off.
# Better keep this low. This is the last version where this will be minutes.
# In the current development versions this is replaced with PingIntervalSeconds
# which defaults to 15 which is much nicer.
PingInterval=1
# The port. 177 is the standard port so better keep it that way
Port=177
# Willing script, none is shipped and by default we'll send
# hostname system id. But if you supply something here, the
# output of this script will be sent as status of this host so that
# the chooser can display it. You could for example send load,
# or mail details for some user, or some such.
Willing=/etc/X11/gdm/Xwilling

[gui]
# The 'theme'. By default we're using the default gtk theme
# Of course assuming that gtk got installed in the same prefix,
# if not change this.
GtkRC=/usr/share/themes/Default/gtk/gtkrc
# Maximum size of an icon, larger icons are scaled down
MaxIconWidth=128
MaxIconHeight=128

[greeter]
# Greeter has a nice title bar that the user can move
TitleBar=false
# Configuration is available from the system menu of the greeter
ConfigAvailable=true
# Face browser is enabled. This only works currently for the
# standard greeter as it is not yet enabled in the graphical greeter.
Browser=false
# The default picture in the browser
DefaultFace=/usr/share/pixmaps/nobody.png
# These are things excluded from the face browser, not from logging in
Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,gdm,postgres,pvm,rpm
# As an alternative to the above this is the minimum uid to show
MinimalUID=100
# If user or user.png exists in this dir it will be used as his picture
GlobalFaceDir=/usr/share/faces/
# Icon we use
Icon=/usr/share/pixmaps/gdm.png
# File which contains the locale we show to the user. Likely you want to use
# the one shipped with gdm and edit it. It is not a standard locale.alias file,
# although gdm will be able to read a standard locale.alias file as well.
LocaleFile=/etc/X11/gdm/locale.alias
# Logo shown in the standard greeter
Logo=/usr/share/pixmaps/gdm-foot-logo.png
# The standard greeter should shake if a user entered the wrong username or
# password. Kind of cool looking
Quiver=true
# The system menu is shown in the greeter
SystemMenu=true
# Note to distributors, if you wish to have a different Welcome string
# and wish to have this translated you can have entries such as
# Welcome[cs]=Vitejte na %n
# Just make sure the string is in utf-8
Welcome=Welcome to %n
# Don't allow user to move the standard greeter window. Only makes sense
# if TitleBar is on
LockPosition=false
# Set a position rather then just centering the window. If you enter
# negative values for the position it is taken as an offset from the
# right or bottom edge.
SetPosition=false
PositionX=0
PositionY=0
# Xinerama screen we use to display the greeter on. Not for true
# multihead, currently only works for Xinerama.
XineramaScreen=0
# Background settings for the standard greeter:
# Type can be 0=None, 1=Image, 2=Color
BackgroundType=2
BackgroundImage=
BackgroundScaleToFit=true
BackgroundColor=#363047
# XDMCP session should only get a color, this is the sanest setting since
# you don't want to take up too much bandwidth
BackgroundRemoteOnlyColor=true
# Program to run to draw the background in the standard greeter. Perhaps
# something like an xscreensaver hack or some such.
BackgroundProgram=
# if this is true then the background program is run always, otherwise
# it is only run when the BackgroundType is 0 (None)
RunBackgroundProgramAlways=false
# Show the chooser (you can choose a specific saved gnome session) session
ShowGnomeChooserSession=true
# Show the Failsafe sessions. These are much MUCH nicer (focus for xterm for
# example) and more failsafe then those supplied by scripts so distros should
# use this rather then just running an xterm from a script.
ShowGnomeFailsafeSession=true
ShowXtermFailsafeSession=true
# Always use 24 hour clock no matter what the locale.
Use24Clock=false
# Use circles in the password field. Looks kind of cool actually

UseCirclesInEntry=false
# These two keys are for the new greeter. Circles is the standard
# shipped theme
GraphicalTheme=gentoo-emergence
GraphicalThemeDir=/usr/share/gdm/themes/

# The chooser is what's displayed when a user wants an indirect XDMCP
# session
[chooser]
# Default image for hosts
DefaultHostImg=/usr/share/pixmaps/nohost.png
# Directory with host images, they are named by the hosts: host or host.png
HostImageDir=/usr/share/hosts/
# Time we scan for hosts (well only the time we tell the user we are
# scanning actually)
ScanTime=3
# A comma separated lists of hosts to automatically add (if they answer to
# a query of course). You can use this to reach hosts that broadcast cannot
# reach.
Hosts=
# Broadcast a query to get all hosts on the current network that answer
Broadcast=true

[debug]
# This will enable debugging into the syslog, usually not neccessary
# and it creates a LOT of spew of random stuff to the syslog. However it
# can be useful in determining when something is going very wrong.
Enable=false

[servers]
# These are the standard servers. You can add as many you want here
# and they will always be started. Each line must start with a unique
# number and that will be the display number of that server. Usually just
# the 0 server is used.
0=Standard
#1=Standard
# Note the VTAllocation and FirstVT keys on linux. Don't add any vt<number>
# arguments if VTAllocation is on, and set FirstVT to be the first vt
# available that your gettys don't grab (gettys are usually dumb and grab
# even a vt that has already been taken). Using 7 will work pretty much for
# all linux distributions. VTAllocation is not currently implemented on
# anything but linux since I don't own any non-linux systems. Feel free to
# send patches. X servers will just not get any extra arguments then.
#
#Note: If you want to run an X terminal you could add an X server such as this
#0=Terminal -query serverhostname
# or for a chooser (optionally serverhostname could be localhost)
#0=Terminal -indirect serverhostname

# Definition of the standard X server.
[server-Standard]
name=Standard server
command=/usr/X11R6/bin/X -nolisten tcp -audit 0
flexible=true

# To use this server type you should add -query host or -indirect host
# to the command line
[server-Terminal]
name=Terminal server
# Add -terminate to make things behave more nicely
command=/usr/X11R6/bin/X -nolisten tcp -audit 0 -terminate
# Make this not appear in the flexible servers (we need extra params
# anyway, and terminate would be bad for xdmcp)
flexible=false
# Not local, we do not handle the logins for this X server
handled=false


here's my Xaccess:
Quote:

# $Xorg: Xaccess,v 1.3 2000/08/17 19:54:17 cpqbld Exp $
# Updated for IPv6
# $XFree86: xc/programs/xdm/config/Xaccess,v 1.3 2001/01/17 23:45:24 dawes Exp $
#
# Access control file for XDMCP connections
#
# To control Direct and Broadcast access:
#
# pattern
#
# To control Indirect queries:
#
# pattern list of hostnames and/or macros ...
#
# To use the chooser:
#
# pattern CHOOSER BROADCAST

# or
#
# pattern CHOOSER list of hostnames and/or macros ...
#
# To define macros:
#
# %name list of hosts ...
#
# To control which addresses xdm listens for requests on:
#
# LISTEN address [list of multicast groups ... ]
#
# The first form tells xdm which displays to respond to itself.
# The second form tells xdm to forward indirect queries from hosts matching
# the specified pattern to the indicated list of hosts.
# The third form tells xdm to handle indirect queries using the chooser;
# the chooser is directed to send its own queries out via the broadcast
# address and display the results on the terminal.
# The fourth form is similar to the third, except instead of using the
# broadcast address, it sends DirectQuerys to each of the hosts in the list
# The fifth form tells xdm which addresses to listen for incoming connections
# on. If present, xdm will only listen for connections on the specified
# interfaces and/or multicast groups.
#
# In all cases, xdm uses the first entry which matches the terminal;
# for IndirectQuery messages only entries with right hand sides can
# match, for Direct and Broadcast Query messages, only entries without
# right hand sides can match.
#

192.168.1.* #any host can get a login window

#
# To hardwire a specific terminal to a specific host, you can
# leave the terminal sending indirect queries to this host, and
# use an entry of the form:
#

#terminal-a host-a


#
# The nicest way to run the chooser is to just ask it to broadcast
# requests to the network - that way new hosts show up automatically.
# Sometimes, however, the chooser can't figure out how to broadcast,
# so this may not work in all environments.
#

#* CHOOSER BROADCAST #any indirect host can get a chooser

#
# If you'd prefer to configure the set of hosts each terminal sees,
# then just uncomment these lines (and comment the CHOOSER line above)
# and edit the %hostlist line as appropriate
#

#%hostlist host-a host-b

#* CHOOSER %hostlist #

#
# If you have a machine with multiple network interfaces or IP addresses
# you can control which interfaces accept XDMCP packets by listing a LISTEN
# line for each interface you want to listen on. You can additionally list
# one or more multicast groups after each address to listen on those groups
# on that address.
#
# If no LISTEN is specified, the default is the same as "LISTEN *" - listen on
# all unicast interfaces, but not for multicast packets. If any LISTEN lines
# are specified, then only the listed interfaces will be listened on.
#

#LISTEN * ff02::1


heres my /etc/services:
Quote:

# /etc/services:
# $Id: services,v 1.5 2003/08/04 19:13:15 azarah Exp $
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/services,v 1.5 2003/08/04 19:13:15 azarah Exp $
#
# Network services, Internet style
#
# Note that it is presently the policy of IANA to assign a single well-known
# port number for both TCP and UDP; hence, most entries here have two entries
# even if the protocol doesn't support UDP operations.
# Updated from RFC 1700, ``Assigned Numbers'' (October 1994). Not all ports
# are included, only the more common ones.

tcpmux 1/tcp # TCP port service multiplexer
echo 7/tcp
echo 7/udp
discard 9/tcp sink null
discard 9/udp sink null
systat 11/tcp users
daytime 13/tcp
daytime 13/udp
netstat 15/tcp
qotd 17/tcp quote
msp 18/tcp # message send protocol
msp 18/udp # message send protocol
chargen 19/tcp ttytst source
chargen 19/udp ttytst source
ftp-data 20/tcp
ftp 21/tcp
fsp 21/udp fspd
ssh 22/tcp # SSH Remote Login Protocol
ssh 22/udp # SSH Remote Login Protocol
telnet 23/tcp
# 24 - private
smtp 25/tcp mail
# 26 - unassigned
time 37/tcp timserver
time 37/udp timserver
rlp 39/udp resource # resource location
nameserver 42/tcp name # IEN 116
whois 43/tcp nicname
re-mail-ck 50/tcp # Remote Mail Checking Protocol
re-mail-ck 50/udp # Remote Mail Checking Protocol
domain 53/tcp nameserver # name-domain server
domain 53/udp nameserver
mtp 57/tcp # deprecated
bootps 67/tcp # BOOTP server
bootps 67/udp
bootpc 68/tcp # BOOTP client
bootpc 68/udp
tftp 69/udp
gopher 70/tcp # Internet Gopher
gopher 70/udp
rje 77/tcp netrjs
finger 79/tcp
www 80/tcp http # WorldWideWeb HTTP
www 80/udp # HyperText Transfer Protocol
link 87/tcp ttylink
kerberos 88/tcp kerberos5 krb5 # Kerberos v5
kerberos 88/udp kerberos5 krb5 # Kerberos v5
supdup 95/tcp
# 100 - reserved
hostnames 101/tcp hostname # usually from sri-nic
iso-tsap 102/tcp tsap # part of ISODE.
csnet-ns 105/tcp cso-ns # also used by CSO name server
csnet-ns 105/udp cso-ns
# unfortunately the poppassd (Eudora) uses a port which has already
# been assigned to a different service. We list the poppassd as an
# alias here. This should work for programs asking for this service.
# (due to a bug in inetd the 3com-tsmux line is disabled)
#3com-tsmux 106/tcp poppassd
#3com-tsmux 106/udp poppassd
rtelnet 107/tcp # Remote Telnet
rtelnet 107/udp
pop2 109/tcp pop-2 # POP version 2
pop2 109/udp pop-2
pop-2 109/tcp postoffice # POP version 2
pop-2 109/udp
pop3 110/tcp pop-3 # POP version 3
pop3 110/udp pop-3
pop-3 110/tcp # POP version 3
pop-3 110/udp
sunrpc 111/tcp portmapper # RPC 4.0 portmapper TCP
sunrpc 111/udp portmapper # RPC 4.0 portmapper UDP
auth 113/tcp authentication tap ident
sftp 115/tcp
uucp-path 117/tcp
nntp 119/tcp readnews untp # USENET News Transfer Protocol
ntp 123/tcp
ntp 123/udp # Network Time Protocol
epmap 135/tcp DCE endpoint resolution
epmap 135/udp DCE endpoint resolution
netbios-ns 137/tcp # NETBIOS Name Service
netbios-ns 137/udp
netbios-dgm 138/tcp # NETBIOS Datagram Service
netbios-dgm 138/udp
netbios-ssn 139/tcp # NETBIOS session service
netbios-ssn 139/udp
imap2 143/tcp # Interim Mail Access Proto v2
imap2 143/udp
snmp 161/udp # Simple Net Mgmt Proto
snmp-trap 162/udp snmptrap # Traps for SNMP
cmip-man 163/tcp # ISO mgmt over IP (CMOT)
cmip-man 163/udp
cmip-agent 164/tcp
cmip-agent 164/udp
mailq 174/tcp # Mailer transport queue for Zmailer
mailq 174/udp # Mailer transport queue for Zmailer
xdmcp 177/tcp # X Display Mgr. Control Proto
xdmcp 177/udp
nextstep 178/tcp NeXTStep NextStep # NeXTStep window
nextstep 178/udp NeXTStep NextStep # server
bgp 179/tcp # Border Gateway Proto.
bgp 179/udp
prospero 191/tcp # Cliff Neuman's Prospero
prospero 191/udp
irc 194/tcp # Internet Relay Chat
irc 194/udp
smux 199/tcp # SNMP Unix Multiplexer
smux 199/udp
at-rtmp 201/tcp # AppleTalk routing
at-rtmp 201/udp
at-nbp 202/tcp # AppleTalk name binding
at-nbp 202/udp
at-echo 204/tcp # AppleTalk echo
at-echo 204/udp
at-zis 206/tcp # AppleTalk zone information
at-zis 206/udp
qmtp 209/tcp # The Quick Mail Transfer Protocol
qmtp 209/udp # The Quick Mail Transfer Protocol
z3950 210/tcp wais # NISO Z39.50 database
z3950 210/udp wais
ipx 213/tcp # IPX
ipx 213/udp
imap3 220/tcp # Interactive Mail Access
imap3 220/udp # Protocol v3
rpc2portmap 369/tcp
rpc2portmap 369/udp # Coda portmapper
codaauth2 370/tcp
codaauth2 370/udp # Coda authentication server
ulistserv 372/tcp # UNIX Listserv
ulistserv 372/udp
ldap 389/tcp # Lightweight Directory Access Protocol
ldap 389/udp # Lightweight Directory Access Protocol
https 443/tcp # MCom
https 443/udp # MCom
snpp 444/tcp # Simple Network Paging Protocol
snpp 444/udp # Simple Network Paging Protocol
microsoft-ds 445/tcp Microsoft-DS
microsoft-ds 445/udp Microsoft-DS
saft 487/tcp # Simple Asynchronous File Transfer
saft 487/udp # Simple Asynchronous File Transfer
npmp-local 610/tcp dqs313_qmaster # npmp-local / DQS
npmp-local 610/udp dqs313_qmaster # npmp-local / DQS
npmp-gui 611/tcp dqs313_execd # npmp-gui / DQS
npmp-gui 611/udp dqs313_execd # npmp-gui / DQS
hmmp-ind 612/tcp dqs313_intercell# HMMP Indication / DQS
hmmp-ind 612/udp dqs313_intercell# HMMP Indication / DQS
#
# UNIX specific services
#
exec 512/tcp
biff 512/udp comsat
login 513/tcp
who 513/udp whod
shell 514/tcp cmd # no passwords used
syslog 514/udp
printer 515/tcp spooler # line printer spooler
talk 517/udp
ntalk 518/udp
route 520/udp router routed # RIP
timed 525/udp timeserver
tempo 526/tcp newdate
courier 530/tcp rpc
conference 531/tcp chat
netnews 532/tcp readnews
netwall 533/udp # -for emergency broadcasts
gdomap 538/tcp # GNUstep distributed objects
gdomap 538/udp # GNUstep distributed objects
uucp 540/tcp uucpd # uucp daemon
afpovertcp 548/tcp # AFP over TCP
afpovertcp 548/udp # AFP over TCP
remotefs 556/tcp rfs_server rfs # Brunhoff remote filesystem
klogin 543/tcp # Kerberized `rlogin' (v5)
kshell 544/tcp krcmd # Kerberized `rsh' (v5)
nntps 563/tcp snntp # NNTP over SSL
nntps 563/udp snntp # NNTP over SSL
ldaps 636/tcp # LDAP over SSL
ldaps 636/udp # LDAP over SSL
kerberos-adm 749/tcp # Kerberos `kadmin' (v5)
#
webster 765/tcp # Network dictionary
webster 765/udp
rsync 873/tcp # rsync
rsync 873/udp # rsync
imaps 993/tcp # IMAP over SSL
imaps 993/udp # IMAP over SSL
pop3s 995/tcp # POP-3 over SSL
pop3s 995/udp # POP-3 over SSL
#
# From ``Assigned Numbers'':
#
#> The Registered Ports are not controlled by the IANA and on most systems
#> can be used by ordinary user processes or programs executed by ordinary
#> users.
#
#> Ports are used in the TCP [45,106] to name the ends of logical
#> connections which carry long term conversations. For the purpose of
#> providing services to unknown callers, a service contact port is
#> defined. This list specifies the port used by the server process as its
#> contact port. While the IANA can not control uses of these ports it
#> does register or list uses of these ports as a convienence to the
#> community.
#
socks 1080/tcp # socks proxy server
socks 1080/udp # socks proxy server
ingreslock 1524/tcp
ingreslock 1524/udp
prospero-np 1525/tcp # Prospero non-privileged
prospero-np 1525/udp
datametrics 1645/tcp old-radius # datametrics / old radius entry
datametrics 1645/udp old-radius # datametrics / old radius entry
sa-msg-port 1646/tcp old-radacct # sa-msg-port / old radacct entry
sa-msg-port 1646/udp old-radacct # sa-msg-port / old radacct entry
radius 1812/tcp # Radius
radius 1812/udp # Radius
radacct 1813/tcp # Radius Accounting
radacct 1813/udp # Radius Accounting
cvspserver 2401/tcp # CVS client/server operations
cvspserver 2401/udp # CVS client/server operations
venus 2430/tcp # codacon port
venus 2430/udp # Venus callback/wbc interface
venus-se 2431/tcp # tcp side effects
venus-se 2431/udp # udp sftp side effect
codasrv 2432/tcp # not used
codasrv 2432/udp # server port
codasrv-se 2433/tcp # tcp side effects
codasrv-se 2433/udp # udp sftp side effect
dict 2628/tcp # Dictionary server
dict 2628/udp # Dictionary server
icpv2 3130/tcp icp # Internet Cache Protocol (Squid)
icpv2 3130/udp icp # Internet Cache Protocol (Squid)
mysql 3306/tcp # MySQL
mysql 3306/udp # MySQL
rfe 5002/tcp # Radio Free Ethernet
rfe 5002/udp # Actually uses UDP only
cfengine 5308/tcp # CFengine
cfengine 5308/udp # CFengine
afs3-fileserver 7000/tcp bbs # file server itself
afs3-fileserver 7000/udp bbs # file server itself
afs3-callback 7001/tcp # callbacks to cache managers
afs3-callback 7001/udp # callbacks to cache managers
afs3-prserver 7002/tcp # users & groups database
afs3-prserver 7002/udp # users & groups database
afs3-vlserver 7003/tcp # volume location database
afs3-vlserver 7003/udp # volume location database
afs3-kaserver 7004/tcp # AFS/Kerberos authentication
afs3-kaserver 7004/udp # AFS/Kerberos authentication
afs3-volser 7005/tcp # volume managment server
afs3-volser 7005/udp # volume managment server
afs3-errors 7006/tcp # error interpretation service
afs3-errors 7006/udp # error interpretation service
afs3-bos 7007/tcp # basic overseer process
afs3-bos 7007/udp # basic overseer process
afs3-update 7008/tcp # server-to-server updater
afs3-update 7008/udp # server-to-server updater
afs3-rmtsys 7009/tcp # remote cache manager service
afs3-rmtsys 7009/udp # remote cache manager service
wnn6 22273/tcp # wnn6
wnn6 22273/udp # wnn6
#
#=========================================================================
# The remaining port numbers are not as allocated by IANA.
#
# Kerberos (Project Athena/MIT) services
# Note that these are for Kerberos v4, and are unofficial. Sites running
# v4 should uncomment these and comment out the v5 entries above.
#
kerberos4 750/udp kerberos-iv kdc # Kerberos (server) udp
kerberos4 750/tcp kerberos-iv kdc # Kerberos (server) tcp
kerberos_master 751/udp # Kerberos authentication
kerberos_master 751/tcp # Kerberos authentication
passwd_server 752/udp # Kerberos passwd server
krb_prop 754/tcp # Kerberos slave propagation
krbupdate 760/tcp kreg # Kerberos registration
kpasswd 761/tcp kpwd # Kerberos "passwd"
kpop 1109/tcp # Pop with Kerberos
knetd 2053/tcp # Kerberos de-multiplexor
zephyr-srv 2102/udp # Zephyr server
zephyr-clt 2103/udp # Zephyr serv-hm connection
zephyr-hm 2104/udp # Zephyr hostmanager
eklogin 2105/tcp # Kerberos encrypted rlogin
#
# Unofficial but necessary (for NetBSD) services
#
supfilesrv 871/tcp # SUP server
supfiledbg 1127/tcp # SUP debugging
#
# Datagram Delivery Protocol services
#
rtmp 1/ddp # Routing Table Maintenance Protocol
nbp 2/ddp # Name Binding Protocol
echo 4/ddp # AppleTalk Echo Protocol
zip 6/ddp # Zone Information Protocol
#
# Services added for the Debian GNU/Linux distribution
#
linuxconf 98/tcp # LinuxConf
poppassd 106/tcp # Eudora
poppassd 106/udp # Eudora
ssmtp 465/tcp # SMTP over SSL
moira_db 775/tcp # Moira database
moira_update 777/tcp # Moira update protocol.
moira_ureg 779/udp # Moira user registration.
omirr 808/tcp omirrd # online mirror
omirr 808/udp omirrd # online mirror
swat 901/tcp # Samba configuration tool
skkserv 1178/tcp # skk jisho server port
rmtcfg 1236/tcp # Gracilis Packeten remote config server
xtel 1313/tcp # french minitel
ms-sql-s 1433/tcp Microsoft-SQL-Server
ms-sql-s 1433/udp Microsoft-SQL-Server
ms-sql-m 1434/tcp Microsoft-SQL-Monitor
ms-sql-m 1434/udp Microsoft-SQL-Monitor
support 1529/tcp # GNATS
cfinger 2003/tcp # GNU Finger
ninstall 2150/tcp # ninstall service
ninstall 2150/udp # ninstall service
afbackup 2988/tcp # Afbackup system
afbackup 2988/udp # Afbackup system
njp 3689/tcp Network Jukebox Protocol
njp 3689/udp Network Jukebox Protocol
fax 4557/tcp # FAX transmission service (old)
hylafax 4559/tcp # HylaFAX client-server protocol (new)
noclog 5354/tcp # noclogd with TCP (nocol)
noclog 5354/udp # noclogd with UDP (nocol)
hostmon 5355/tcp # hostmon uses TCP (nocol)
hostmon 5355/udp # hostmon uses TCP (nocol)
postgres 5432/tcp # POSTGRES
postgres 5432/udp # POSTGRES
canna 5680/tcp # cannaserver
saned 6566/tcp # SANE network scanner daemon
ircd 6667/tcp # Internet Relay Chat
ircd 6667/udp # Internet Relay Chat
webcache 8080/tcp # WWW caching service
webcache 8080/udp # WWW caching service
tproxy 8081/tcp # Transparent Proxy
tproxy 8081/udp # Transparent Proxy
mandelspawn 9359/udp mandelbrot # network mandelbrot
amanda 10080/udp # amanda backup services
kamanda 10081/tcp # amanda backup services (Kerberos)
kamanda 10081/udp # amanda backup services (Kerberos)
amandaidx 10082/tcp # amanda backup services
amidxtape 10083/tcp # amanda backup services
isdnlog 20011/tcp # isdn logging system
isdnlog 20011/udp # isdn logging system
vboxd 20012/tcp # voice box system
vboxd 20012/udp # voice box system
binkp 24554/tcp # Binkley
binkp 24554/udp # Binkley
asp 27374/tcp # Address Search Protocol
asp 27374/udp # Address Search Protocol
tfido 60177/tcp # Ifmail
tfido 60177/udp # Ifmail
fido 60179/tcp # Ifmail
fido 60179/udp # Ifmail
#
# Services added for cyrus-imapd
#
imsp 406/tcp # Interactive Mail Support Protocol
acap 674/tcp # Application Configuration Access Protocol
sieve 2000/tcp # Sieve mail filter daemon
lmtp 2003/tcp # Local Mail Transfer Protocol
fud 4201/udp # finger support

# Local services

#
# VNC Servers
#
vnc-640x480x8 5950/tcp
vnc-800x600x8 5951/tcp
vnc-1024x768x8 5952/tcp
vnc-1280x1024x8 5953/tcp
vnc-1600x1200x8 5954/tcp

vnc-640x480x16 5960/tcp
vnc-800x600x16 5961/tcp
vnc-1024x768x16 5962/tcp
vnc-1280x1024x16 5963/tcp
vnc-1600x1200x16 5964/tcp

vnc-640x480x24 5970/tcp
vnc-800x600x24 5971/tcp
vnc-1024x768x24 5972/tcp
vnc-1280x1024x24 5973/tcp
vnc-1600x1200x24 5974/tcp

vnc-640x480x32 5980/tcp
vnc-800x600x32 5981/tcp
vnc-1024x768x32 5982/tcp
vnc-1280x1024x32 5983/tcp
vnc-1600x1200x32 5984/tcp


and here's my /etc/xinetd.d/xvncserver:
Quote:

service vnc-640x480x8
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 640x480 -depth 8
}

service vnc-800x600x8
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 800x600 -depth 8
}

service vnc-1024x768x8
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 1024x768 -depth 8
}

service vnc-1280x1024x8
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 1280x1024 -depth 8
}

service vnc-1600x1200x8
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 1600x1200 -depth 8
}

service vnc-640x480x16
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 640x480 -depth 16
}

service vnc-800x600x16
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 800x600 -depth 16
}

service vnc-1024x768x16
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 1024x768 -depth 16
}

service vnc-1280x1024x16
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 1280x1024 -depth 16
}

service vnc-1600x1200x16
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 1600x1200 -depth 16
}

service vnc-640x480x24
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 640x480 -depth 24
}

service vnc-800x600x24
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 800x600 -depth 24
}

service vnc-1024x768x24
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 1024x768 -depth 24
}

service vnc-1280x1024x24
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 1280x1024 -depth 24
# port = 5973
}

service vnc-1600x1200x24
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 1600x1200 -depth 24
}

service vnc-640x480x32
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 640x480 -depth 32
}

service vnc-800x600x32
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 800x600 -depth 32
}

service vnc-1024x768x32
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 1024x768 -depth 32
}

service vnc-1280x1024x32
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 1280x1024 -depth 32
}

service vnc-1600x1200x32
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 1600x1200 -depth 32
}


here's my .vnc/xstartup:
Quote:

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
gdm &



i do have xinetd startup at bootup and i dont get any error mesgs.... I just don't know wut else to do...
Back to top
View user's profile Send private message
rrrkkkttt
Tux's lil' helper
Tux's lil' helper


Joined: 02 Oct 2003
Posts: 96

PostPosted: Sat Feb 07, 2004 5:56 am    Post subject: Reply with quote

i decided to start from scratch so I unmerged tightvnc and xinetd and followed the tutorial again... the server starts up now... vncviewer is connecting to the server but i still get the gray screen... and my .vnc folder is deleted now... when i start vncviewer it doesn't create the .vnc folder automatically... the tutorial doesn't say anything about that... so do I have to run any program to create it or do I create it myself and also create the xstartup file ?
Back to top
View user's profile Send private message
vdboor
Guru
Guru


Joined: 03 Dec 2003
Posts: 592
Location: The Netherlands

PostPosted: Sat Feb 07, 2004 10:47 am    Post subject: Reply with quote

rrrkkkttt wrote:
vncviewer is connecting to the server but i still get the gray screen... and my .vnc folder is deleted now...


The .vnc folder isn't used in the xinetd setup. you run "Xvnc -inetd", and this changes the rules ;)

Do you have XDMCP running? If the Xvnc server can't find a xdmcp server, your X server stays empty, that's why you have the gray green. Enable xdmcp in the display-manager you use (xdm/gdm/kdm), and make sure the server is running. Type "netstat -anpA inet", or "netstat -lnpA inet" to see all network connections. (or listening in the second example)
_________________
The best way to accelerate a windows server is by 9.81M/S²
Linux user #311670 and Yet Another Perl Programmer

[ screenies | Coding on KMess ]
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Goto page Previous  1, 2, 3 ... 5, 6, 7 ... 15, 16, 17  Next
Page 6 of 17

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum