1748171 Members
4662 Online
108758 Solutions
New Discussion юеВ

Pb X server

 
letters
Occasional Advisor

Pb X server

Hello,

When i want launch xclck for example
i have :
Xlib: connection to "X.X.X.X:0.0" refused by server
Xlib: No protocol specified

Error: Can't open display: X.X.X.X:0.0
Error: Couldn't find per display information

can anyone help me
13 REPLIES 13
letters
Occasional Advisor

Re: Pb X server

i forgot to add i want to do a export display from windows

Mel Burslan
Honored Contributor

Re: Pb X server

since you can see this information (assuming again from your windows box) how do you obtain this information, in other words what is the terminal emulation software you are using to (or trying to) launch the xclock ? What is the x-server you are running on the windows PC ? Reflections-X ? eXceed ?

If you give a chronological order of actions you take on your windows PC and commands you run on the ternminal, it might make more sense.

I do not sound like a broken record and another forum member but two lines of error code pasted into the forum post, without the commands that coused the display of them, doesn't help much if you are expecting a meaningful answer.
________________________________
UNIX because I majored in cryptology...
klb
Valued Contributor

Re: Pb X server


This looks like your X-server is restricted. I know with some others, you have to do the equivalent of...

xhosts +

... which allows to connect or if you want to open the entire thing up to any inbound connections...

xhosts +

In the case of your X-server, I don't know exactly how you would open the access up to it. Maybe look at the help files or read other docs to figure that out.

In general though, you run a PC-X server on your PC ( either eXceed, Xming, Reflections, etc ), then go to your remote machine and fire up the X application after setting your DISPLAY variable to point to your PC...

DISPLAY=XXX.XXX.XXX.XXX:0
export DISPLAY

/usr/bin/X11/xeyes # or whatever

...depending on your shell, you may have to set that variable in different manner.

Given your error messages, you may also be having some sort of configuration problem on the host where you get the Xlib messages.

Can you send your X-app to some other DISPLAY without error and this is just failing on your PC with the errors above?

-klb
Steven Schweda
Honored Contributor

Re: Pb X server

> Xlib: connection to "X.X.X.X:0.0" refused by server

Normally, "connection refused" suggests that
there's no one running the right stuff on the
server system.

> This looks like your X-server is
> restricted. [...]

Or you don't have one. Do you think that you
are running an X server on your Windows
system? (Which one? Configured how?)
letters
Occasional Advisor

Re: Pb X server

so I repeat at the beginning :

On HP 11-31
I do :
export DISPLAY=X.X.X.X:0.0

[root@X2R3 /root]# echo $DISPLAY
X.X.X.X:0.0

On my Windows i use Xming

when i launch xclock i have :
Xlib: connection to "X.X.X.X:0.0" refused by server
Xlib: No protocol specified

Error: Can't open display: X.X.X.X:0.0
Error: Couldn't find per display information

When i try with xterm :
[root@X2R3 /root]# xterm
xterm Xt error: Can't open display: %s
[root@RX-2-R3 /root]#

*******
XF86Config :
#
# The ServerLayout section specifies the input and output devices that are
# connected to the server. Multiple ServerLayout sections may be contained in
# the XF86Config file. However, the first one in the file is the active
# layout, unless otherwise specified by the -layout option from the command
# line. Check the "Graphics Administration Guide" (GAG) for other options that
# may be set here, or elsewhere, in the XF86Config file. An online
# version of the "Graphics Administration Guide" is available at:
#
# http://www.hp.com/support/workstation_manuals
#
# after selecting the link appropriate for a given workstation model.
#
Section "ServerLayout"

#
# The ServerLayout ID. A required line.
#

Identifier "Main Layout"

#
# The first field on the Screen line specifies the screen number. It is
# optional. The second field is the Screen ID. It must match an entry in
# a Screen section. Only Screens specified here will be active. The
# remaining fields specify relative or absolute positions of the screen
# relative to other screens. Check the GAG for full details on
# specifying the Screen.
#

Screen 0 "Screen 0" 0 0

#
# Each InputDevice line specifies an InputDevice section ID name and
# optionally some options that specify the way the device is to be used.
# Typically there is a pointer device (mouse) and a keyboard. They
# usually are specified with a CorePointer and CoreKeyboard option
# respectively. Additional pointers and keyboards are specified with
# the SendCoreEvents option. The options may also be specified in the
# InputDevice section. It is not necessary to specify an InputDevice.
#

InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"

#
# Uncomment this to force OGL indirect contexts to be rendered in
# software. Indirect rendering is done with the hardware driver by
# default. However, some features such as rendering to a glXPixmap
# may not be available in all hardware drivers.
#

#Option "AccelerateIndirectRendering" "false"

# Uncomment the following line and update the time to turn on Xserver
# screen blanking. The time is in minutes.

#Option "blank time" "10"

# Uncomment the following lines to set the DPMS time periods. The
# time is in minutes. The DPMS Monitor Option must be on for these
# to have an effect (see the "Monitor" section).

#Option "standby time" "20"
#Option "suspend time" "30"
#Option "off time" "40"
EndSection

#
# The Files section is used to specify the location of various files
# to the X server. There may only be one Files section in the XF86Config
# file.
#
Section "Files"

#
# FontPaths. Specifies the font paths. You may want to
# specify a different font path for the following reasons.
# 1) An application delivers its own fonts.
# 2) A font server is to be used instead of the default path.
#
EndSection

#
# The Module section is used to inform the server which loadable libraries are
# to be loaded at run time. There may only be one Module section in the
# XF86Config file.
# See the GAG for more details.
#
Section "Module"
EndSection

#
# There may be multiple InputDevice sections. An InputDevice section is active
# only if it is specified by the active ServerLayout section. The Identifief
# is a required line and must be identical to an InputDevice line in the
# active ServerLayout in order for the device to be active. Normally there
# are two InputDevice sections in the XF86Config file. One for the pointer
# (mouse) and the other for the keyboard. The Driver line is required. It
# specifies which driver is to be loaded at run time. See the GAG for more
# details on what input devices are supported and which options may be selected.
#
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "PS/2"
EndSection

#
# There may be multiple Monitor sections. The purpose of this section is
# is to specify the range of operation of a monitor. For a Monitor to be
# in use the Identifier must match the Monitor line in an active Screen.
# HorizSync and VertRefresh are required fields. See the GAG for more
# options that may be set.
#
Section "Monitor"
Identifier "Monitor 0"
HorizSync 30.0 - 110.0
VertRefresh 50.0 - 75.0

# DPMS is not enabled by default. Uncomment the following line to
# enable it.

#Option "DPMS" "on"
EndSection

#
# There may be multiple Device sections. This section is used to specify
# parameters for the graphics device. The Identifier string must match
# the Device string in the active Screen section for this device to be
# in use. See the GAG for more options that may be set for this particular device.
#
Section "Device"
Identifier "Console"
Devicefile "/dev/gvid"
EndSection

#
# There may be multiple Screen sections. The Identifier string must match
# the Device string in the active ServerLayout section for the Screen to
# be active.
#
Section "Screen"
Identifier "Screen 0"
Device "Console"
Monitor "Monitor 0"

#
# Set the default depth.
#
DefaultDepth 24

#
# The subsection associates a buffer depth with a screen size.
#
SubSection "Display"
Depth 24
Modes "1280x1024"
EndSubSection
EndSection
****

Steven Schweda
Honored Contributor

Re: Pb X server

> On my Windows i use Xming

Ok. What happens if you do this on the HP-UX
system?:

telnet windows_system 6000

If it says "connection refused", then you're
not running a useful X server where you think
you are. If you can talk to port 6000, then
there's an X server there, but it may not be
configured to allow your HP-UX system to use
its display. I don't know enough about Xming
to tell you how to show and set the list of
permitted clients. ("xhost" is the old UNIX
thing.)
letters
Occasional Advisor

Re: Pb X server

[root@X2R3 /etc]# telnet X.X.X.X 6000
Trying...
Connected to X.X.X.X.
Escape character is '^]'.
klb
Valued Contributor

Re: Pb X server


To make Xming work.

Go to the program group menu under your Windows button, click XLaunch.

click...
Multiple Windows => Next
Start No Client => Next
check No Access Control => Next
Then click finish.

Xming has now been started with no access control.

-klb

uz
Occasional Advisor

Re: Pb X server

It 's not a problem on XMing because I already use it on others machines