x problem

[Josh_13]

i'm not even sure the problem is with hpux 10.20. i think it might be the win 2000 pro that i'm tryiing to run xterm from. if it is it's an interaction bug.

xterm runs fine from solaris, redhat 7.2, basically anything unix based. exceed, the x client on the windows 2k pro machine kkeeps telling me it can't start x witht he method it wants to on the 10.20. it works fine on 11i. as far as i know it's the same method.

this gets a bit more interesting. if i ssh or telnet directly to a box running 10.20 i can't start x. however, if i bounce through a box running any unix variant aside from hpux, it will let me start x and use it. then there's the quirk that exceed must be running or it won't let it run. so i don't know how it all fits together. i know there's a problem with how exceed and hpux talk to each other on hpux 10.20, buti don't know anything beyond that.

is there some change in how x is started between 10.20 and 11i? is there something else i should look at as a possible problem?
likei said, i suspect the problem lies in the windows box. let's face it, microsoft operating systems aren't exactly something to rave about. however, since it works right with 11i, i wonder if there's something that can be done to get it to talk correctly with 10.20.

[Craig Rants]

Josh,

I run reflection on a W2K machine with no problem. Don't know of a reason why exceed would not work as well. What type of connection are you making with exceed? Can you make a failsafe connection to your hpux box? If so I would look at your CDE config.

Let us know,
C

[Jason VanDerMark]

Maybe your 10.20 box isn't using CDE. You may have the box configured to run HP-VUE. VUE looks like CDE except that it has a little cpu chart where the clock should be in your CDE session. You might just want to see. If so, it may require you to stop the HP-VUE services and start up the X11 stuff. Just a thought...I miss that nifty little cpu chart from VUE. Oh well. I hope that this is helpful.

Regards,
Jason V.

[Steven Gillard_2]

Josh,

What happens when you try the following:

- start your exceed X server on your PC
- telnet into the HPUX system via normal MS telnet
- export your DISPLAY environment variable to you PC's display (eg export DISPLAY=:0.0)
- run an X client (eg xclock or xterm)

Do you get an error?

Regards,
Steve

[Josh_13]

just got in today (i work 12-5pm until after christmas, then i start real hours (9-5) until break ends) and haven't had a chance to check on the questions of Craig or Jason. However, i can already answer Steve's question. (it was the first thing i checked hoping someone here would be able to help once i found i could bounce through a linux bot and have it work)
it gives me if i go directly via telnet or ssh to the 10.20 box, use setenv DISPLAY and it tells me:
Error: can't open display:
Error: Couldn't find the per display information

mind you, it tells me this whether or not exceed is running. i have double checked that it was set each time andit does set the display.

[Josh_13]

ok.umm.. searching for cde...

# du -a | /usr/bin/grep cde
2 ./etc/rc.config.d/cde
0 ./etc/ocdebug
20 ./home/aryeh/ssh-1.2.26/gmp-2.0.2-ssh-2/mpn/generic/gcdext.c
0 ./home/aryeh/ssh-1.2.26/gmp-2.0.2-ssh-2/mpn/gcdext.c
12 ./home/aryeh/ssh-1.2.26/gmp-2.0.2-ssh-2/mpn/gcdext.o
6 ./home/aryeh/ssh-1.2.26/gmp-2.0.2-ssh-2/mpz/gcdext.c
4 ./home/aryeh/ssh-1.2.26/gmp-2.0.2-ssh-2/mpz/gcdext.o
144 ./home/usr/sbin/ocdebug
144 ./usr/sbin/ocdebug
10 ./usr/share/man/cat1m.Z/ocdebug.1m
8 ./usr/share/man/man1m.Z/ocdebug.1m
10 ./usr/dt/appconfig/help/C/cdelogo.pm
4 ./usr/dt/config/dtspcdenv
12 ./usr/dt/share/man/man4/dtspcdenv.4
2 ./usr/sam/lbin/cde_check
144 ./var/adm/sw/patch/PHNE_6190/usr/sbin/ocdebug
4 ./var/adm/sw/patch/PHSS_15795/usr/dt/config/dtspcdenv
#

[Josh_13]

searching for "VUE" turns nothing. searching for "vue" spits back pages. i think i have both CDE and HP-VUE on the system. how do i find out which one it is using? and then how do i override that to the other one?

[Josh_13]

trying to find the problem i decided to install xemacs since i don't like vi. xemacs can't find X. result: we're trying to find out why. in doing s we updated the make to 3.79.1, added gnubinutils, and are now updating the gcc since that never had use of the binutils and doesn't support a function xemacs wants. this is to get rid of the warnings and other problems to see why xemacs can't find X. we're hoping that systematically taking away errors from xemacs will show why it can't find X, and that problem will lead to fixing the problem with X. if i get something that looks like it might help in solving this i'll post it. thanks for all the help so far.

-Josh

[Craig Rants]

How about going to /usr/dt/config and looking in the Xfailsafe file for XDIR, it should look something like this: XDIR=/usr/bin/X11. That tells the failsafe session that X should be in that dir (there with a lot of other apps).

Also you may want to get the CDE cum patch, your patch level looks a little old, this "may" straighten things up for you.

HH,
C

[Karvendhan M]

Hi

Check by telnetting and runnig X cliets.

it seems last time you did't set the DISPLAY variable. If you don't have a DISPLAY varibable then only we get this error.

If you want your hp machine to answer XDMCP queries from your exceed, check /etc/dt/config/Xaccess or /etc/vue/config/Xaccess. If these files are not there copy them from /usr/(dt|vue)/config/Xaccess.

Then Check vue or DT is running.
# ps -ef | grep dtlogin
# ps -ef | grep vuelogin

~ Kars

[K.Vijayaragavan.]

Hope CDE is running and you are able to use CDE atleast on the server console.

If you are trying to access X Windows of HPUX 10.20 using exceed in any windows platform
then,

1)please check "/var/adm/inetd.sec" file for the entry "dtspc deny" if any specified. If specified you may comment it out.

2)check "/etc/inetd.conf" for the line strating with "dtspc". If it is commented out please uncomment it.

3)check the entries of the file "/usr/dt/config/Xaccess". specialy line with entries " * # grant service to all remote display "

3)check the entries of the file "/usr/dt/config/Xaccess". specialy line with entires " * CHOOSER BROAD CAST # any indirect host can get a chooser"

4) content of "/etc/dt/config/Xaccess" and "/usr/dt/config/Xaccess" should be same.

5)check the DISPLAY variable setting by
using the command #echo $DISPLAY

6)use the command " xhost + " to grant x access to all.

7) In the exceed software's startup menu if you start "Exceed(Xdmcp broadcast)" then it should display the list of Xservers running on your network and that should display the expected server's (HPUX10.20) ip address too.

I hope this would answer your question.

-Vijay

[Josh_13]

Craig-

the file was set correctly, but i can't find patches for a d370 running hpux 10.20

Kars-

turns out it whether or not i tell it the command setenv DISPLAY ip (only using the dotted decimal of anything running windows, any variation) it won't display at least certain things. SAM and xterm being the two constants.

DT is what's running, those two files don't exist in VUE. what's more i had to copy /usr/dt/config/Xaccess to /etc/dt/config/Xaccess

however, that doesn'tseem to be doing much.

the one machine tht gets more than the one i use that's got a windows os is running exceed 6.x instead of 7.1 which is what everything else is using.


Vijay-

3)check the entries of the file "/usr/dt/config/Xaccess". specialy line with entries " * # grant service to all remote display "

3)check the entries of the file "/usr/dt/config/Xaccess". specialy line with entires " * CHOOSER BROAD CAST # any indirect host can get a chooser"


there are no entries for either one.

the only thing i didn't do from your list is check exceed's start up thingy. the reason i didn't is becuase it won't display for me. it flashes on the start up on the screen and then disappears. i'm going to check it on 6.x next chance i get. right now i think that the biggest issue deals with changes in the version being used.

[Josh_13]

vijay: although your advice is helpful, it didn't solve anything. it's still only going over telnet, which we would like to eventually turn off.

[Alex Glennie]

You say "DISPLAY and it tells me:
Error: can't open display:
Error: Couldn't find the per display information"

it will unless this was a typo .... DISPLAY takes the form of ip_address:0.0 or hostname:0.0.

OK I have Exceed , post clear instructions on what I need to do to reproduce the problem ?

However the following may help ?

On the 10.20 hpux hosts you will need the following processes running dtlogin or vuelogin. At 11.00 dtlogin is your only option due to the discontinuance of VUE. If you have both I'd stick with vue : edit your inittab accordingly.

Next : I'd ensure hostname resolution and ip addresses resolve on all hosts envolved include PC, hpux and any other "intermediate" hosts that may be involved here.

I'd also suggest you try using dtterm as well just in case you get different results :

Both CDE and VUE have diagnostic tools in /usr/contrib/bin/X11 : dr_dt or dr_vue they may help ?

Let me know how to reproduce your problem ... i got lost in the descriptins above.

[Josh_13]

taken from a telnet session (i have no clue what's causeing this. if i knew what caused it i'd tell ya how to make it happen., i'd also know how to fix it. i'm going to try your suggestion but figured this would be good or you and others trying to help to see in the meantime.)


TERM = (hp) vt100
hal 21: env
HOME=/
PATH=/usr/bin:/usr/contrib/bin:/opt/gnu.gnubinutils:/usr/ccs/bin:/opt/nettladm/n
LOGNAME=root
TERM=vt100
SHELL=/sbin/tcsh
MAIL=/var/mail/root
SHLVL=1
PWD=/
USER=root
HOST=hal
HOSTTYPE=hp9000s700
MANPATH=/usr/share/man/%L:/usr/share/man:/usr/contrib/man/%L:/usr/contrib/man:/n
TZ=EST5EDT
hal 22: netscape
Error: Can't open display:
Error: Couldn't find per display information
hal 23: setenv DISPLAY 129.64.5.249
hal 24: env
HOME=/
PATH=/usr/bin:/usr/contrib/bin:/opt/gnu.gnubinutils:/usr/ccs/bin:/opt/nettladm/n
LOGNAME=root
TERM=vt100
SHELL=/sbin/tcsh
MAIL=/var/mail/root
SHLVL=1
PWD=/
USER=root
HOST=hal
HOSTTYPE=hp9000s700
MANPATH=/usr/share/man/%L:/usr/share/man:/usr/contrib/man/%L:/usr/contrib/man:/n
TZ=EST5EDT
DISPLAY=129.64.5.249

hal 25: netscape
Error: Can't open display:
Error: Couldn't find per display information

[Wodisch]

Hello Josh,

just like Alex wrote: your $DISPLAY variable is set wrong!

The syntax is this:
[IP-address]:Server-No[.Screen-No]

which means, you MUST have at least have a colon in your DISPLAY adress!

DISPLAY=129.64.5.129:0.0

should be fine for you, as your PC certainly only has one X-servre (read: X-Windows Emulation) running and probably only one CRT/screen ist connected to that PC...

Modify it, and try again - now you should be fine!

And if you would have used the "XDMCP" startup with the "-query" option, everything would have been working from the very start :-)

HTH,
Wodisch

[Josh_13]

Wodish:

TERM = (hp) vt100
hal 11: setenv DISPLAY 129.64.5.249:0.0
hal 12: env
HOME=/
PATH=/usr/bin:/usr/contrib/bin:/opt/gnu.gnubinutils:/usr/ccs/bin:/opt/nettladm/n
LOGNAME=root
TERM=vt100
SHELL=/sbin/tcsh
MAIL=/var/mail/root
SHLVL=1
PWD=/
USER=root
HOST=hal
HOSTTYPE=hp9000s700
MANPATH=/usr/share/man/%L:/usr/share/man:/usr/contrib/man/%L:/usr/contrib/man:/n
TZ=EST5EDT
DISPLAY=129.64.5.249:0.0
hal 13: netscape
Error: Can't open display: 129.64.5.249:0.0
Error: Couldn't find per display information
hal 14:


hoever, this gets a little more intersting, because of a problem with the router ( http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x9bd85a3e6e0bd6118ff40090279cd0f9,00.html ), some things changed and we tried to put this back on the backup list. while doing so we found out the backup software is installed incorrectly, and for some reason, at least part of the exceed software is in that subdirectory. both have to come off so they can be put on properly.

when that's been done, i'll let everyone know what happened with the X problem. if the X problem solved itself, then next time someone has a similar issue we can have them make sure it's installed properly as their first move. since it was one of many things that was installed previously since we got this box form a different subsection of network operations, i figured it would have been installed correctly. apparently i shouldn't have taken anything for granted.

-Josh

[Josh_13]

ok. in one of the networker sub directories i noticed a "rexecd" which i thought would belong to exceed since rexec is a start up method it uses. however i can't find "exceed" anywhere on the machine, so i'm not sure i was right on that. however, if it's a product of networker, then after the new one is installed it might be usable for exceed...

[K.Vijayaragavan.]

Josh,
Hi,

I would like to share couple of points with you,

Just see that rexec service is enabled on the HP server/wks in the file "/etc/inetd.conf" for the line "exec stream tcp nowait root /usr/lbin/rexecd rexecd". This line may not have to be commented out for the execeed to work.(I suppose)

If you want to secure rexec services then you can add the entry "rexec allow " in the "var/adm/inetd.sec" file.

I found that the exceed is mostly depending on the rpc services specified in the"/etc/inetd.conf" file. if you open those services then exceed should work.
You can always secure any services by adding required entries in "/var/adm/inetd.sec".

Hope you have configured Exceed properly in the PC and you are using "Exceed(XDMCP) " to access Xwindows of unix system.

-Vijay

[Joseph C. Denman]

Josh,

As always, I'm a little confused here????

Are you attempting to run the gui from a win2k telnet session--that will not work. Try this:

--You said exceed worked fine on your 11i box. Use exceed to login to CDE on the 11i box.
--From the 11i box, telnet over to the 10.20 box.
--Then, "export DISPLAY=ip.of.win2kbox:0.0"
--run "xterm"

Do you get the same errors? Do you get an xterm box?

Just attempting to clear things up????


...jcd...

[Josh_13]

i know i need exceed up in order to get x to run. however, exceed is not even starting correctly over telnet. that is the problem here. after going through the files mentioned, i found the method was not commented out, and yet the method was set to deny. i changed that so it is now correct and it only allows connections from the proer subnet.

this didn't fix the problem though. it now is giving me differnt errors about the connection not being able to remain open.

[Joseph C. Denman]

Josh,

Now I'm really confused????

You post:
"however, exceed is not even starting correctly over telnet. that is the problem here."



You do not start exceed over telnet????? You start exceed on the client.(your win2k box)
Telnet has nothing to do with exceed.

Start with the basics:

What happens when you attempt to start exceed on the win2k box? Do you just get the familiar grey screen???

You probably need to go into xconfig on the win2k box and set it up to connect to the unix box.

Just need some specifics.


...jcd...

[Josh_13]

let's see if i can actually phrase things in a way that isn't convoluted and confusing.



1: when the win2k machine starts, exceed is in the start up, however, when it tries to start there are two things it may do.

if set to use telnet (currently not the default), then it crashes for some reason i can't figure out.

if set to use rexec (currently the default), then it gives an audit error and keeps giving the error until you hit cancel.

2: if you telent to the hal from a windows box, then no matter how one tries to set the display variable, it gives that per display error.

3: if one uses ssh from a linux/unix/solaris box, then it works fine, even if you neglect to set the display variable.

-Josh

[Joseph C. Denman]

Josh,

Sorry it took so long to get back on this...very busy...plus I figured someone else would have answered.!!!

I think this is the problem is what is happening.

The reason it works from the linix/unix/solaris box is they all ready have cde running on the system, thus have a so called??built-in and working terminal emulater. So when you telnet over to another unix box and set your display to the linix/unix/solaris box, the X traffic has no problems.

The reason you can't set your display to the win2k box is because you do not have the exceed configured correctly. I have my exceed configure for broadcast. If you set up your Xaccess file as stated above, you should see the servers when you bring up exceed.

Good Luck and Hope this helps..

...jcd...