Solaris 10 Display setting Headache

DatisDataDatis

This is my issue:

Open Xwin Server on windows XP machine (my desktop machine)
Open putty session and set Enable X11 forwarding
Using putty I then connect to db server (Solaris 10) logged in as "oracleuser"

$ set
BASH=/bin/bash
BASH_ARGC=()
BASH_ARGV=()
BASH_LINENO=()
BASH_SOURCE=()
BASH_VERSINFO=([0]="3" [1]="00" [2]="16" [3]="1" [4]="release" [5]="sparc-sun-solaris2.10")
BASH_VERSION='3.00.16(1)-release'
COLUMNS=126
DIRSTACK=()
DISPLAY=localhost:10.0
EDITOR=vi
EUID=101
GROUPS=()
HISTFILE=/export/home/oracle//.bash_history
HISTFILESIZE=500
HISTSIZE=500
HOME=/export/home/oracle/
...
PATH=/usr/bin:/usr/local/bin:/oracle/product/db/11gR202/bin:/usr/ccs/bin:/usr/bin/X11:/usr/local/bin
....
TERM=xterm
.........etc


As you can see DISPLAY is set

$/usr/openwin/bin/xclock

Xclock displayed on windows XP machine

Success!

Now connecting to an identical box.


open Xwin Server on windows XP machine
open putty session and set Enable X11 forwarding
using putty open connection to Solaris 10 db server logged in as "oracleuser"
$ set
BASH=/bin/bash
BASH_ARGC=()
BASH_ARGV=()
BASH_LINENO=()
BASH_SOURCE=()
BASH_VERSINFO=([0]="3" [1]="00" [2]="16" [3]="1" [4]="release" [5]="sparc-sun-solaris2.10")
BASH_VERSION='3.00.16(1)-release'
COLUMNS=126
DIRSTACK=()
EDITOR=vi
EUID=101
GROUPS=()
HISTFILE=/export/home/oracle//.bash_history
HISTFILESIZE=500
HISTSIZE=500
HOME=/export/home/oracle/
...
PATH=/usr/bin:/usr/local/bin:/oracle/product/db/11gR202/bin:/usr/ccs/bin:/usr/bin/X11:/usr/local/bin
....
TERM=xterm

...etc

DISPLAY is NOT set

So

$export DISPLAY=localhost:10.0

$echo $DISPLAY
localhost:10.0


$/usr/openwin/bin/xclock
Error: Can't open display: localhost:10.0

So

$/usr/openwin/bin/xhost
/usr/openwin/bin/xhost: unable to open display "localhost:10.0"

any and all attempts to run anything X11 related end up with the same message

other checks

$cat /etc/ssh/sshd_config | grep -i x11

# X11 tunneling options
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost yes

$more /etc/hosts

#
# Internet host table
#
10.100.200.10 name-of-server.dev.orgnameint.net name-of-server loghost
::1 localhost
127.0.0.1 localhost
10.1.2.16 ntp1 ntp1.orgnameint.net
10.1.2.17 ntp2 ntp2.orgnameint.net


$./xauth list
name-of-server/unix:10 MIT-MAGIC-COOKIE-1 7b39a111db9b71932c7742f752815073
name-of-server/unix:11 MIT-MAGIC-COOKIE-1 1abaa8baded63a3beceb34f3b0a4ea89


all settings that are set for the box that works are also set for the box that does not work.

I have tried the above as root - still no Joy.


It feels like I have checked every web page designated to this problem and tried all of the solutions that are relevant to Solaris (and even some that aren't) but still had no joy.

Does anyone know of any logs that I can use to try and identify the issue, or think of something I may be missing.

Regards,
JP

Srini Chavali-Oracle

Moving this to the Solaris 10 forum from the Database Install forum

Srini

989800

1. can you check if your Windows XServer display can be reached from Solaris10 machine directly (without ssh/X11 forwarding), like

Solaris$ xterm -display a.b.c.d:0 &

where a.b.c.d is the IP address of the Windows machine where XServer runs?

2. Can you try some other XServer on Winwows PC, like Cygwin/X?
Also, once Cygwin ssh/X forwarding proves to work, you can start your original XServer, but use Cygwin ssh to further trouble-shoot X forwarding. Basically, having two different X11 servers and two different ssh clients should give you some more trouble-shooting options.

DatisDataDatis

Fantastic!

On the good box I used
/usr/openwin/bin/xterm -display localhost:10

Success Xterminal popped up on Windows machine

from problem box I got
/xterm Xt error: Can't open display: localhost:10

Arrrgh!

But! I noticed something this time.

so I shutdown all putty sessions

deleted my saved entry for the Problem Solaris box
And low and behold - Success

The entry in putty must have been corrupt. When I was connecting to the Solaris box the connection was failing to register in .Xauthority (this is what i noticed!) so, i guess, the key in there was out of date and so... issues.

Thanks for the advice. It opened up a new avenue of investigation which is what I needed.

Regards,
JP