1834447 Members
2286 Online
110067 Solutions
New Discussion

Re: x problem

 
Mark Fenton
Esteemed Contributor

Re: x problem

Josh, to echo what Joseph said in last post:

On the win2k box, you should run exceed in XDMCP Broadcast mode, either active (looks for server on port 177) or passive (allows connection from server on port 177).

With Exceed in passive mode, you should be able to telnet to the HP-UX box, set your DISPLAY=:0.0 (or which ever server number you set for exceed) and run an X app.

This really should work (it's the way I run X in my environment)

Regards

Mark
Josh_13
Super Advisor

Re: x problem

ack. a legato networker problem kept me from this. right now that seems to be in limbo.. in any case, how do i access the Xaccess file? i tried looking for an xaccess file and couldn't fdind it going through the exceed things. how do i set it to do that? (i'm new to the software)

thanx in advance

-Josh
Joseph C. Denman
Honored Contributor

Re: x problem

Josh,

Xaccess is on the unix box. Take a look at the top of this thread for Vijay's response.


As far as I can tell from what has been stated thus far, you need to concentrate on the exceed win2k box. Go into xconfig and check all your settings.


...jcd...
If I had only read the instructions first??
Sanjay_6
Honored Contributor

Re: x problem

Sanjay_6
Honored Contributor

Re: x problem

Josh_13
Super Advisor

Re: x problem

Sanjay: the second set of links didn't work. the first would be great if it weren't for hte fact the hpux side is fine.

Joe: Xaccess looks correct. i went into xconfig, but couldn't find the place to specify "XDMCP Broadcast mode"

Mark: see my comment to Joe. i think that is how to fix my problem, ut am not sure of how to set up the prefs to access it like that.

Vijay: like Mark you may not have single-handedly solved my problem, but from what you've said gthe solution seems obvious. i'm waiting until i get it working to give the two of you 10s. if the problem was on the hpux side you would have solved it, instead you allowed me to know it's ont he windows side, which Mark's reponse should sovle.

between the two of you this thread should pretty much cover X problems anyone has in the future.

-Josh