[Solved] xdm won't listen on xdmcp port 177

Hi,
I'm Trying to setup xdm to accept xdmcp request. Using the steps in the wiki listed here:
https://wiki.archlinux.org/index.php/Xdmcp
I commented out the line in xdm-conf
! 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
Also modified Xaccess to allow all hosts:
* #any host can get a login window
Then i check if it's listening by issuing this command:
[root@myhost ~]# ss -lnut
Netid Recv-Q Send-Q Local Address:Port Peer Address:Port
tcp 0 50 *:139 *:*
tcp 0 50 :::139 :::*
tcp 0 64 *:5901 *:*
tcp 0 128 *:6000 *:*
tcp 0 128 :::6000 :::*
tcp 0 128 :::22 :::*
tcp 0 128 *:22 *:*
tcp 0 50 *:445 *:*
tcp 0 50 :::445 :::*
tcp 0 5 *:33092 *:*
Doesn't appear to be listening on port 177 and it is definitely not working.
Any ideas?
Last edited by jmandawg (2011-10-21 21:02:05)

Nevermind, i used the wrong command:
ss -ua
shows that it is listening

Similar Messages

[solved] GDM won't start after update

Hello.
Today I made a pacman -Syu and gdm was updated.
On the next boot i only get a console and not the usual gdm login.
I loged in and tried to start gdm manualy with /etc/rc.d/gdm restart
wich results in an error message : "gdm already running. Aborting!", but it isnt
The X Server works (tried startx).
Any ideas what happend to gdm and how to fix it?
/edit : additional info: using current repository

Does your gdm.conf file contains paths like this: /usr/X11R6/bin
I think pacman just overwrites the config files if you never changed anything to them. In my case I did some modifications, so pacman made a backup of my modified file.
In case your file don't contain any /usr/X11R6/... , you may try do diff your file between mine:
# 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.
# For full reference documentation see the gnome help browser under
# GNOME|System category. You can also find the docs in HTML form on
# http://www.gnome.org/projects/gdm/
# NOTE: Some of these are commented out but still show their default values.
# If you wish to change them you must remove the '#' from the beginning of
# the line. The commented out lines are lines where the default might
# change in the future, so set them one way or another if you feel
# strongly about it.
# 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=tom
# Timed login, useful for kiosks. Log in a certain user after a certain
# amount of time
TimedLoginEnable=false
TimedLogin=
TimedLoginDelay=30
# The gdm configuration program that is run from the login screen, you should
# probably leave this alone
#Configurator=/opt/gnome/sbin/gdmsetup --disable-sound --disable-crash-dialog
# The chooser program. Must output the chosen host on stdout, probably you
# should leave this alone
#Chooser=/opt/gnome/libexec/gdmchooser
# The greeter for local (non-xdmcp) logins. Change gdmlogin to gdmgreeter to
# get the new graphical greeter.
#Greeter=/opt/gnome/libexec/gdmlogin
Greeter=/opt/gnome/libexec/gdmgreeter
# The greeter for xdmcp logins, usually you want a less graphically intensive
# greeter here so it's better to leave this with gdmlogin
#RemoteGreeter=/opt/gnome/libexec/gdmlogin
RemoteGreeter=/opt/gnome/libexec/gdmgreeter
# Launch the greeter with an additional list of colon seperated gtk
# modules. This is useful for enabling additional feature support
# e.g. gnome accessibility framework. Only "trusted" modules should
# be allowed to minimise security holes
#AddGtkModules=false
# By default these are the accessibility modules
#GtkModulesList=gail:atk-bridge:/opt/gnome/lib/gtk-2.0/modules/libdwellmouselistener:/opt/gnome/lib/gtk-2.0/modules/libkeymouselistener
# Default path to set. The profile scripts will likely override this
DefaultPath=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/opt/gnome/bin
# Default path for root. The profile scripts will likely override this
RootPath=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/opt/gnome/sbin:/opt/gnome/bin
# 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
#AlwaysRestartServer=false
# User and group used for running gdm GUI applicaitons. By default this
# is set to user gdm and group gdm. This user/group should have very
# limited permissions and access to ony the gdm directories and files.
User=nobody
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/log/gdm
# You should probably never change this value unless you have a weird setup
PidFile=/var/run/gdm.pid
# Note that a post login script is run before a PreSession script.
# It is run after the login is successful and before any setup is
# run on behalf of the user
PostLoginScriptDir=/opt/gnome/etc/gdm/PostLogin/
PreSessionScriptDir=/opt/gnome/etc/gdm/PreSession/
PostSessionScriptDir=/opt/gnome/etc/gdm/PostSession/
DisplayInitDir=/opt/gnome/etc/gdm/Init
# 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=/opt/gnome/etc/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 "Rebooted from gdm menu."
HaltCommand=/sbin/shutdown -h now "Halted from gdm menu."
SuspendCommand=/usr/bin/apm --suspend
# Probably should not touch the below this is the standard setup
ServAuthDir=/opt/gnome/var/gdm
# This is our standard startup script. A bit different from a normal
# X session, but it shares a lot of stuff with that. See the provided
# default for more information.
BaseXsession=/opt/gnome/etc/gdm/Xsession
# This is a directory where .desktop files describing the sessions live
# It is really a PATH style variable since 2.4.4.2 to allow actual
# interoperability with KDM. Note that <sysconfdir>/dm/Sessions is there
# for backwards compatibility reasons with 2.4.4.x
SessionDesktopDir=/etc/X11/sessions/:/etc/dm/Sessions/:/usr/share/xsessions/:/opt/gnome/share/gdm/BuiltInSessions/:/opt/gnome/share/xsessions/
# This is the default .desktop session. One of the ones in SessionDesktopDir
#DefaultSession=gnome.desktop
# Better leave this blank and HOME will be used. You can use syntax ~/ below
# to indicate home directory of the user. You can also set this to something
# like /tmp if you don't want the authorizations to be in home directories.
# This is useful if you have NFS mounted home directories. Note that if this
# is the home directory the UserAuthFBDir will still be used in case the home
# directory is NFS, see security/NeverPlaceCookiesOnNFS to override this behaviour.
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
# And after how many minutes should we reap the flexible server if there is
# no activity and no one logged on. Set to 0 to turn off the reaping.
# Does not affect Xnest flexiservers.
#FlexiReapDelayMinutes=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
# Should double login be treated with a warning (and possibility to change
# vts on linux and freebsd systems for console logins)
#DoubleLoginWarning=true
# Should a second login always resume the current session and
# switch vts on linux and freebsd systems for console logins
#AlwaysLoginCurrentSession=true
# If true then the last login information is printed to the user before
# being prompted for password. While this gives away some info on what
# users are on a system, it on the other hand should give the user an
# idea of when they logged in and if it doesn't seem kosher to them,
# they can just abort the login and contact the sysadmin (avoids running
# malicious startup scripts)
#DisplayLastLogin=false
# Program used to play sounds. Should not require any 'daemon' or anything
# like that as it will be run when no one is logged in yet.
#SoundProgram=/usr/bin/play
# These are the languages that the console cannot handle because of font
# issues. Here we mean the text console, not X. This is only used
# when there are errors to report and we cannot start X.
# This is the default:
#ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh
# This determines whether gdm will honor requests DYNAMIC requests from
# the gdmdynamic command.
#DynamicXServers=false
# This determines whether gdm will send notifications to the console
#ConsoleNotify=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=false
# If you want to be paranoid, turn this one off
AllowRemoteRoot=false
# This will allow remote timed login
AllowRemoteAutoLogin=false
# 0 is the most restrictive, 1 allows group write permissions, 2 allows all
# write permissions
RelaxPermissions=0
# Check if directories are owned by logon user. Set to false, if you have, for
# example, home directories owned by some other user.
CheckDirOwner=true
# Number of seconds to wait after a bad login
#RetryDelay=1
# 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
# If true this will basically append -nolisten tcp to every X command line,
# a good default to have (why is this a "negative" setting? because if
# it is false, you could still not allow it by setting command line of
# any particular server). It's probably better to ship with this on
# since most users will not need this and it's more of a security risk
# then anything else.
# Note: Anytime we find a -query or -indirect on the command line we do
# not add a "-nolisten tcp", as then the query just wouldn't work, so
# this setting only affects truly local sessions.
DisallowTCP=true
# By default never place cookies if we "detect" NFS. We detect NFS
# by detecting "root-squashing". It seems bad practice to place
# cookies on things that go over the network by default and thus we
# don't do it by default. Sometimes you can however use safe remote
# filesystems where this is OK and you may want to have the cookie in your
# home directory.
#NeverPlaceCookiesOnNFS=true
# 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. Setting up /etc/hosts.allow and /etc/hosts.deny to only
# allow local access is another alternative but not the safest.
# Firewalling port 177 is the safest if you wish to have xdmcp on.
# Read the manual for more notes on the security of XDMCP.
Enable=false
# 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 seconds after which a non-responsive session is logged off.
# Better keep this low.
#PingIntervalSeconds=15
# 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=/opt/gnome/etc/gdm/Xwilling
[gui]
# The specific gtkrc file we use. It should be the full path to the gtkrc
# that we need. Unless you need a specific gtkrc that doesn't correspond to
# a specific theme, then just use the GtkTheme key
#GtkRC=/opt/gnome/share/themes/Default/gtk-2.0/gtkrc
# The GTK+ theme to use for the gui
#GtkTheme=Default
# If to allow changing the GTK+ (widget) theme from the greeter. Currently
# this only affects the standard greeter as the graphical greeter does
# not yet have this ability
#AllowGtkThemeChange=true
# Comma separated list of themes to allow. These must be the names of the
# themes installed in the standard locations for gtk themes. You can
# also specify 'all' to allow all installed themes. These should be just
# the basenames of the themes such as 'Thinice' or 'LowContrast'.
#GtkThemesToAllow=all
# 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=true
# 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=true
# The default picture in the browser
#DefaultFace=/opt/gnome/share/pixmaps/nobody.png
# User ID's less than the MinimalUID value will not be included in the
# face browser or in the gdmselection list for Automatic/Timed login.
# They will not be displayed regardless of the settings for
# Include and Exclude.
MinimalUID=1000
# Users listed in Include will be included in the face browser and in
# the gdmsetup selection list for Automatic/Timed login. Users
# should be separated by commas.
#Include=
# Users listed in Exclude are excluded from the face browser and from
# the gdmsetup selection list for Automatic/Timed login. Excluded
# users will still be able to log in, but will have to type their
# username. Users should be separated by commas.
Exclude=bin,daemon,mail,nobody
# By default, an empty include list means display no users. By setting
# IncludeAll to true, the password file will be scanned and all users
IncludeAll=true
# will be displayed except users excluded via the Exclude setting and
# user ID's less than MinimalUID. Scanning the password file can be
# slow on systems with large numbers of users and this feature should
# not be used in such environments. The setting of IncludeAll does
# nothing if Include is set to a non-empty value.
#IncludeAll=false
# If user or user.png exists in this dir it will be used as his picture
#GlobalFaceDir=/opt/gnome/share/pixmaps/faces/
# 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=/opt/gnome/etc/gdm/locale.alias
# Logo shown in the standard greeter
#Logo=/opt/gnome/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 Actions menu (formerly system menu) is shown in the greeter, this is the
# menu that contains reboot, shutdown, suspend, config and chooser. None of
# these is available if this is off. They can be turned off individually
# however
SystemMenu=true
# Should the chooser button be shown. If this is shown, GDM can drop into
# chooser mode which will run the xdmcp chooser locally and allow the user
# to connect to some remote host. Local XDMCP does not need to be enabled
# however
#ChooserButton=true
# Welcome is for all console logins and RemoteWelcome is for remote logins
# (through XDMCP).
# DefaultWelcome and DefaultRemoteWelcome set the string for Welcome
# to "Welcome" and for DefaultWelcome to "Welcome to %n", and properly
# translate the message to the appropriate language. Note that %n gets
# translated to the hostname of the machine. These default values can
# be overridden by setting DefaultWelcome and/or DefaultRemoteWelcome to
# false, and setting the Welcome and DefaultWelcome values as desired.
# Just make sure the strings are in utf-8 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".
DefaultWelcome=true
DefaultRemoteWelcome=true
#Welcome=Welcome
#RemoteWelcome=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=#76848F
# 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 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
# Normally there is a session type called 'Last' that is shown which refers to
# the last session the user used. If off, we will be in 'switchdesk' mode where
# the session saving stuff is disabled in GDM
#ShowLastSession=true
# Always use 24 hour clock no matter what the locale.
#Use24Clock=false
# Use circles in the password field. Looks kind of cool actually,
# but only works with certain fonts.
#UseCirclesInEntry=false
# Do not show any visible feedback in the password field. This is standard
# for instance in console, xdm and ssh.
#UseInvisibleInEntry=false
# These two keys are for the new greeter. Circles is the standard
# shipped theme. If you want gdm to select a random theme from a list
# then provide a list that is delimited by /: to the GraphicalThemes key and
# set GraphicalThemeRand to true. Otherwise use GraphicalTheme and specify
# just one theme.
#GraphicalTheme=circles
GraphicalTheme=happygnome-list
#GraphicalThemes=circles/:happygnome
GraphicalThemes=circles
GraphicalThemeDir=/opt/gnome/share/gdm/themes/
GraphicalThemeRand=false
# If InfoMsgFile points to a file, the greeter will display the contents of the
# file in a modal dialog box before the user is allowed to log in.
#InfoMsgFile=
# If InfoMsgFile is present then InfoMsgFont can be used to specify the font
# to be used when displaying the contents of the file.
#InfoMsgFont=Sans 24
# If SoundOnLogin is true, then the greeter will beep when login is ready
# for user input. If SoundOnLogin is a file and the greeter finds the
# 'play' executable (see daemon/SoundProgram) it will play that file
# instead of just beeping
#SoundOnLogin=true
SoundOnLogin=false
#SoundOnLoginFile=
# If SoundOnLoginSuccess, then the greeter will play a sound (as above)
# when a user successfully logs in
#SoundOnLoginSuccess=false
#SoundOnLoginSuccessFile=
# If SoundOnLoginFailure, then the greeter will play a sound (as above)
# when a user fails to log in
#SoundOnLoginFailure=false
#SoundOnLoginFailureFile=
# The chooser is what's displayed when a user wants an indirect XDMCP
# session, or selects Run XDMCP chooser from the system menu
[chooser]
# Default image for hosts
#DefaultHostImg=/opt/gnome/share/pixmaps/nohost.png
# Directory with host images, they are named by the hosts: host or host.png
HostImageDir=/opt/gnome/share/hosts/
# Time we scan for hosts (well only the time we tell the user we are
# scanning actually, we continue to listen even after this has
# expired)
#ScanTime=4
# 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
# Set it to true if you want to send a multicast query to hosts.
Multicast=false
# It is an IPv6 multicast address.It is hardcoded here and will be replaced when
# officially registered xdmcp multicast address of TBD will be available
#Multicast_Addr=ff02::1
# Allow adding random hosts to the list by typing in their names
#AllowAdd=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 and freebsd.
# 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 and freebsd. Feel free to send patches.
# X servers will just not get any extra arguments then.
# 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
# If you wish to run the XDMCP chooser on the local display use the following
# line
#0=Chooser
## Note:
# is your X server not listening to TCP requests? Perhaps you should look
# at the security/DisallowTCP setting!
# Definition of the standard X server.
[server-Standard]
name=Standard server
command=/usr/X11R6/bin/X -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 -audit 0 -terminate
# Make this not appear in the flexible servers (we need extra params
# anyway, and terminate would be bad for xdmcp choosing). You can
# make a terminal server flexible, but not with an indirect query.
# If you need flexible indirect query server, then you must get rid
# of the -terminate and the only way to kill the flexible server will
# then be by Ctrl-Alt-Backspace
flexible=false
# Not local, we do not handle the logins for this X server
handled=false
# To use this server type you should add -query host or -indirect host
# to the command line
[server-Chooser]
name=Chooser server
command=/usr/X11R6/bin/X -audit 0
# Make this not appear in the flexible servers for now, but if you
# wish to allow a chooser server then make this true. This is the
# only way to make a flexible chooser server that behaves nicely.
flexible=false
# Run the chooser instead of the greeter. When the user chooses a
# machine they will get this same server but run with
# "-terminate -query hostname"
chooser=true

Please help me creating a new listener with different port#.

I have two instances in a server. both have different homes. I want to create a seperate listener for the second one i created.
But that is not happening.
here i tried to give name from LISTENER TO LISTENER1 & Port# from 1521 to 1524.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /apps2/oracle)
(PROGRAM = extproc)
LISTENER1 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(ADDRESS = (PROTOCOL = TCP)(HOST = aixth53)(PORT = 1524))
When I check lsnrctl status with LISTENER1 , it still shows the other instance home with port#: 1521
Please help me creating a new listener with different port#.
Thanks,

marist89 wrote:
sb92075 wrote:
marist89 wrote:
sybrand_b wrote:
The listener is a broker only and doesn't play any role in normal communications.
It just forks a process or a thread, and that's it.And the listener is a single point of failure. Listener goes down, you can't connect to the db. That's why you need two listeners.If listener one goes down, then listener two goes down for exact same reason since it is a single executable file.I'm not playing tit-for-tat with you. Fact is, there are situations where people who are not you might want to use more than one listener.Some folks might want to jab a sharp pencil into their eye, too.
Just because you can do something, it does not necessarily mean it should be done.

If port is unavailable then which service is listening on that port

hi all
I am writing one module to check 1) which ports are available in system and 2) if port is unavailable then which service is listening on that port. I want to run that module on Windows platform and also UNIX platform.
I have done first part but i am not finding way to do the second part. Is there any way in Java or any other prog language (C, C++) to do so. please share idea or code i am awaiting for response.
Thanks in advance :)
Message was edited by:
Codeword_Swan

Under Unix there is the command "fuser" to tell which process has open a given file. With -n you can tell another space like tcp for sockets. Thus:
$ fuser -n tcp 7777
here: 7777
7777/tcp:             3753
$ ps -p 3753 -f
UID        PID PPID C STIME TTY          TIME CMD
oracle    3753 3722 0 Aug28 ?        00:00:53 /opt/oracle/product/AS/10g/R2/webcache/bin/webcached -OPMN -U 1325072547

Question: one weblogic server listening on several port

can i start one weblogic server that listening on several port, one for
different application?
for example,
7001 for general user, and
7005 for admistrators and ask for two way authentification?
can i do this? or do i have to start two weblogic instance? does that
violate it's license for one computer and one ip address?
thank u.

Ummm.. how would this help security? If I want to bypass authentication, I just go to the unprotected port.
I don't think you can listen to different ports in the same instance
. You can listen to different IP addresses in the same instance.
WL is licensed by CPU so this would not cost any more to license.
mike
"Gong Wenxue" <[email protected]> wrote:
can i start one weblogic server that listening on several port, one for
different application?
for example,
7001 for general user, and
7005 for admistrators and ask for two way authentification?
can i do this? or do i have to start two weblogic instance? does that
violate it's license for one computer and one ip address?
thank u.

Java.rmi.server.ExportException: Listen failed on port: 1099;

Hi All,
I am trying to run RMI tutorial from sun's java tutorial. It has 8 parts. The last two parts are "Compiling the Example Programs" and "Running the Example Programs".
Until "Compiling the Example Programs", I am okay.
But I am stuck in the last part, "Running the Example Programs". When I use the command "rmiregistry", it gives me a list of exceptions as follows.
c:\home\ann\src>rmiregistry
java.rmi.server.ExportException: Listen failed on port: 1099; nested exception is:
java.net.SocketException: Permission denied: listen failed
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:312)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393)
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:129)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:190)
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:78)
at sun.rmi.registry.RegistryImpl.main(RegistryImpl.java:322)
Caused by: java.net.SocketException: Permission denied: listen failed
at java.net.PlainSocketImpl.socketListen(Native Method)
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:380)
at java.net.ServerSocket.bind(ServerSocket.java:320)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at java.net.ServerSocket.<init>(ServerSocket.java:97)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:27)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:333)
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:649)
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:299)
... 7 more
c:\home\ann\src>
Then, I try to use "start rmiregistry" command. At that time, a command window stating the above exception popup just for a while and closed automatically.
Now, I use jdk1.6.0_16 on Windows Vista.
Previously, I used j2sdk1.4.2_19. That time, I could run "start rmiregistry" properly and could try testing another RMI example application.
But if I use j2sdk1.4.2_19, compiling some statements in the sun's RMI tutorial gives me error. So, I change to use jdk1.6.0_16 for this tutorial. "jdk1.6.0_16" compiles all programs in the tutorial with no error. But I can't run the statement "start rmiregistry".
I use the command prompt from Vista's default Administrator account and already disable User Account Control too.
Any help, please!
Thanks a lot,
atzm111

Hi,
This is the result of netstat -an
c:\home\ann\src>netstat -an
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2868 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3999 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 192.168.1.102:139 0.0.0.0:0 LISTENING
TCP 192.168.1.102:49475 64.233.189.17:80 ESTABLISHED
TCP 192.168.1.102:49620 64.233.189.83:80 ESTABLISHED
TCP 192.168.1.102:49625 72.5.124.102:80 ESTABLISHED
TCP 192.168.1.102:49626 72.5.124.102:80 ESTABLISHED
TCP 192.168.1.102:49627 72.5.124.102:80 ESTABLISHED
TCP 192.168.1.102:49628 72.5.124.102:80 ESTABLISHED
TCP 192.168.1.102:49629 72.5.124.102:80 ESTABLISHED
TCP 192.168.1.102:49631 72.5.124.61:80 TIME_WAIT
TCP 192.168.1.102:49634 124.155.222.16:80 ESTABLISHED
TCP [::]:135 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5355 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:51196 *:*
UDP 127.0.0.1:64757 *:*
UDP 192.168.1.102:137 *:*
UDP 192.168.1.102:138 *:*
UDP 192.168.1.102:1900 *:*
UDP 192.168.1.102:51195 *:*
UDP [::]:123 *:*
UDP [::]:500 *:*
UDP [::]:5355 *:*
UDP [::1]:1900 *:*
UDP [::1]:51193 *:*
UDP [fe80::100:7f:fffe%16]:1900 *:*
UDP [fe80::100:7f:fffe%16]:51194 *:*
UDP [fe80::18c1:1fa4:382b:261%12]:1900 *:*
UDP [fe80::18c1:1fa4:382b:261%12]:51191 *:*
UDP [fe80::69bc:321e:5e99:dc7c%11]:1900 *:*
UDP [fe80::69bc:321e:5e99:dc7c%11]:51192 *:*
UDP [fe80::a0a0:89c2:b2fd:e4b9%13]:1900 *:*
UDP [fe80::a0a0:89c2:b2fd:e4b9%13]:51190 *:*
c:\home\ann\src>
So, port 1099 is not in use. I don't know how to check your second fact. I'll find it out coz I can't ask you. :D
Thanks!

Listening to multiple ports(socets) for data?

I know that this topic has been covered before, but is either simplistic questions or overly complex things (that I don't understand... yet)
Here is my issue: I have data coming from two ports (TCP/IP) an array of 210 bytes and I'm not sure which port will be activated first. The data is asyncronus. So basically I want to figure out how to listen to the ports. I have this code...
import java.io.*;
import java.util.*;
import java.net.*;
public class SocketListener{
    public static void main(String[] argv){
        ServerSocket mySocket = null;
        ServerSocket mySocket2 = null;
        try {
            mySocket=new ServerSocket(12000);
            mySocket2= new ServerSocket (13000);
        catch (IOException e){
            System.err.println("error");
            System.exit(-1);
        try {
            Socket client = mySocket.accept();
            System.out.println("The server has connected to 12000\n");
            // do what I need it to do a.k.a. get data array
            client.close();
        catch(IOException e){
            System.err.println("error");
            System.exit(-1);
        try {
            Socket client2 = mySocket2.accept();
            System.out.println("The server has connected to 13000\n");
            // do what I need it to do a.k.a. get data array
            client2.close();
        catch (IOException e){
            System.err.println("error");
            System.exit(-1);
}I'm not sure if it works or not... but thats what I got. Is this the best way to go about this or is there something else that I should look up in documentation / look for examples / someone might have a link to something.
Thanks a lot!!!!
Edited by: KTLightning on Sep 12, 2007 1:25 PM

There are two issues at hand here, one being networking and the second being threading. Threading is an extensive subject and I don't want to shortchange you here, so you may want to read this tutorial if you are not familiar with Java threading concepts: http://java.sun.com/docs/books/tutorial/essential/concurrency/index.html
That being said, if you want to concurrently listen to the sockets, you will need a thread for each socket you are listening. Otherwise you can use Java NIO, but unless you are going to be listening to many sockets at once, this complication is not necessary since the learning curve of Java NIO can be quite steep.
You might want to start out creating a new class that will handle the task of listening to a socket and retrieving the data in its own thread. You can do this by either extending the Thread class or implementing the Runnable interface. From your main class, you can then spawn as many of those objects as you need. The trick to this approach is knowing when the data has been read from the socket and stored in the object. For only two objects this is simple as you can have a hasData() method on your worker objects and then just put a loop in your main class checking to see if the condition has been met on the objects.
Here's some code fragments as an example...
public class SocketReader extends Thread ...
ServerSocket ss = null;
boolean hasData = false;
SocketReader(int port) {
ss = new ServerSocket(port);
public void run() {
ss.accept();
// do your stuff
hasData =true;
public boolean hasData() {
return hasData;
main() {
SocketReader sr1 = new SocketReader(12000);
SocketReader sr2 = new SocketReader(12000);
sr1.start();
sr2.start();
// keep looping until we have data in both
while (!sr1.hasData() && !sr2.hasData()) {
try {
Thread.sleep(100);
} catch (InterrruptedException ie) {/ do something}
} // end main
Keep in mind that this is a very simplistic example to demonstrate the concepts and would not be a good design for pretty much any other case.

Can a Selector listen on 2 ports?

Hi.
Can a Selector thread, listen on 2 ports, making a tcp server that accepts connections on 2 ports?
Thanks.

tpmaster wrote:
Hi.
Can a Selector thread, listen on 2 ports, making a tcp server that accepts connections on 2 ports?
Thanks.Sure you can; register the ServerSocketChannels at the Selector and off you go.
kind regards,
Jos

How to extract Weblogic Listen Address and port.

Hi All,
I want to extract Weblogic Admin server's Listen address and port via Java to perform some admin actions.
Can someone please help on this.
Thanks,
GJ

Hi,
Try this code.
import java.io.IOException;
import java.net.MalformedURLException;
import java.util.Hashtable;
import javax.management.MBeanServerConnection;
import javax.management.MalformedObjectNameException;
import javax.management.ObjectName;
import javax.management.remote.JMXConnector;
import javax.management.remote.JMXConnectorFactory;
import javax.management.remote.JMXServiceURL;
import javax.naming.Context;
import java.lang.*;
public class ServerDetails
private static MBeanServerConnection connection;
private static JMXConnector connector;
private static final ObjectName service;
static
try {
service=new ObjectName("com.bea:Name=DomainRuntimeService,Type=weblogic.management.mbeanservers.domainruntime.DomainRuntimeServiceMBean");
catch (MalformedObjectNameException e)
throw new AssertionError(e.getMessage());
public static void initConnection(String hostname, String portString,String username, String password) throws IOException,MalformedURLException
System.out.println("ServerDetails---Started in initConnection");
String protocol="t3";
Integer portInteger=Integer.valueOf(portString);
int port=portInteger.intValue();
String jndiroot="/jndi/";
String mserver="weblogic.management.mbeanservers.domainruntime";
JMXServiceURL serviceURL=new JMXServiceURL(protocol, hostname,port, jndiroot + mserver);
Hashtable h=new Hashtable();
h.put(Context.SECURITY_PRINCIPAL, username);
h.put(Context.SECURITY_CREDENTIALS, password);
h.put(JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES,"weblogic.management.remote");
connector=JMXConnectorFactory.connect(serviceURL, h);
connection=connector.getMBeanServerConnection();
public static ObjectName[] getServerRuntimes() throws Exception
return (ObjectName[]) connection.getAttribute(service,"ServerRuntimes");
public void printServerDetails() throws Exception
ObjectName[] serverRT=getServerRuntimes();
for (int i=0;i < serverRT.length;i++)
String name=(String)connection.getAttribute(serverRT,"Name");
String listenAddress=(String)connection.getAttribute(serverRT[i],"ListenAddress");
Integer listenPort=(Integer)connection.getAttribute(serverRT[i],"ListenPort");
System.out.println("Server Name : " + name +"\t Address: "+listenAddress+"\t Port: "+listenPort);
public static void main(String[] args) throws Exception
System.out.println("ServerDetails---Started");
String hostname=args[0];
String portString=args[1];
String username=args[2];
String password=args[3];
System.out.println("Hostname : " + hostname);
System.out.println("PortString : " + portString);
System.out.println("Username : " + username);
System.out.println("Password : " + password);
ServerDetails sd=new ServerDetails();
initConnection(hostname, portString, username, password);
sd.printServerDetails();
connector.close();
Regards,
Kal

Mac mail service isnt listening on default ports at all other than SMTP

Mac mail service isnt listening on default ports at all other than SMTP.
I can port scan locally and here is what's listening
Port Scan has started…
Port Scanning host: <IPADDRESS>
     Open TCP Port:     25             smtp
     Open TCP Port:     53             domain
     Open TCP Port:     80             http
     Open TCP Port:     88             kerberos
     Open TCP Port:     106            3com-tsmux
     Open TCP Port:     311            asip-webadmin
     Open TCP Port:     389            ldap
     Open TCP Port:     443            https
     Open TCP Port:     464            kpasswd
     Open TCP Port:     587            submission
     Open TCP Port:     625            dec_dlm
     Open TCP Port:     749            kerberos-adm
Port Scan has completed…
Mail service is on.

first place to start is always /var/log/system.log
stop/start mail service while watching that log.
You will probably catch some dovecot/imap lines that will yield clues.
Post results.

Can imapd listen on multiple ports?

For historical reasons, we've got some multiplexors that expect to make the back-end imap connecto to port 993, and some others that want to talk to 994. Is it possible to configure imapd to listen on multiple ports?
Thanks!

I just realized this would be doable if the MMP would do STARTTLS to the back-end (since then I could enable STARTTLS on the default port and keep SSL on connect on the other port).
If only.....

Listen on two ports on the cfp

I tried posting this in the cFP forum, but I didn't get an answer, so I figured I try here. I have tried to do this twice, and neither time did it work. On a cFP 21xx is it possible to listen on two ports, using TCP over ethernet, at the same time? Or is it possible to talk on one port and listen on another? I know this is not standard, and it seems not to work, but I can't figure out a reason why not. Is it possible, or is there something in the cFP that prevents this type of communication system from working?
Regards,
Jo-Jo

Hi Jo-Jo,
I posted an answer to this question in your original post listen on two ports on one cFP.
Please refrain from posting the same question to several forums. If you are not getting an answer in one forum please repost to notify any new browsers of the question. This keeps several people from the same answer several times in different places.
Michael K | Applications Engineer | National Instruments.
| Michael K | Project Manager | LabVIEW R&D | National Instruments |

Configure Virtual Host to Listen on Two Ports

Oracle App Server 9.0.4
I need my mid-tier HTTP server to listen for SSL traffic on 2 ports: 443 and 4443. I also need it to listen for non-SSL traffic on port 80 (this traffic should only come from localhost).
We have an SSL certificate for our web address already and unfortunately it will take quite a while to get another certificate, so I'd prefer not to have to setup a different url for the second SSL port if I can help it.
Currently there is one virtual host set as type default.
The Virtual Hosts properties page provides the following 3 options for Listening Ports (host is set for https protocol):
(1) Listen on all main ports
(2) Listen on specific port (443 by default)
(3) Listen only on the main server default port
If I set it to option (1) then the server will not respond on port 80 for non-SSL traffic.
If I set it to option (2) then it will not respond to ssl traffic on port 4443.
If I set it to option (3) then it is listening on port 80 only (the default port for the HTTP server)
Is there a way to have this default virtual host listen to both 443 and 4443 for SSL traffic and non-SSL traffic on 80?
Appreciate your time.
Message was edited by:
dredstar

Thanks for the reply Kjell, I ended up doing the same thing. I left my default host servicing all ports with https, so it would respond to incoming requests on ports 443 and 4443. Then I created a new http protocol virtual host listening only on 127.0.0.1 port 80 and that allowed non-SSL traffic to be serviced coming from the machine itself.

How to have a module listening a socket port?

Hi,
who know how to make a module of adapter and let it listening a socket port?
thanks in advance

Hi,
Take a look at this blog,
/people/saravanakumar.kuppusamy2/blog/2005/12/15/socket-integration-with-xi
Regards,
Bhavesh

SocketServer Listen on Multiple Ports

What is the optimal way to have a SocketServer listen on more than one IP/port combination? I'm looking for various ways of doing this including a quick and easy way and the best-practices way.
Thanks.

There is no way to 'have a SocketServer listen on more than one IP/port combination'. A SocketServer can only listen at one port. You need multiple SocketServer objects, and you should use multiple threads executing accept loops.

[Solved] xdm won't listen on xdmcp port 177

Similar Messages

Maybe you are looking for