AIX

Hi,

I want to display a program on my local workstation, that is running on a remote AIX, and I have done the following:

but it displayed this :

Code:

>xclock &
[1]     1769700
Error: Can't open display: 10.0.0.9:0
[1] +  Done(1)                 xclock &

could you help me with this
Rgards

This is basically meaning that the X server on your Windows system is refusing to accept the X client as one of its clients. The X protocol has its own authorisation devices, which are based on the hostnames of the systems X-clients are allowed to connect from.

For a simple try if this is the case issue a

Code:

xhost +

on the command line of your client, which will disable authentication completely. Then start the X client on the remote system again.

In the long run you will probably not want to disable authentication completely but only accept X connections from a few select remote systems. Depending on the X-Server you use there should be a configuration where you can enter one (or several) hostnames from which X clients will be accepted.

I hope this helps.

bakunin

Hi Bakunin,
I tried this command on the client (AIX) and it displayed this :

Code:

>xhost +
1356-200 xhost unable to open display "10.0.0.9:0"

any ideas ?

I thought that i made it quite clear above that you have to configure the access control ON THE X-SERVER!

If you are unsure about how X-Windows works in general or what an "X-server" or an "X-client" is i suggest you read this thread.

In addition, from the error message i can see that your DISPLAY-variable is set incorrectly. It should be:

Code:

DISPLAY=<your client IP or DNSname>:0.0

In this case "client" means the system - the one with the X-server running.

I hope this helps.

bakunin

don't know if you solved this already but here's my input:
in putty under ssh, go to x11. click enable x11 forwarding.
enter this info:

Code:

x display location: localhost:0

next, launch the xming app.
go back to the putty window and enter your server info.
(ensure you're using SSH, unless default is changed, putty's default is telnet)
when terminal is open type these commands to confirm everything is working:

Code:

xauth list    -  This output should show something like MIT-MAGIC-COOKIE *****
echo $DISPLAY    -   This should display localhost:10.0
(if display does not show the localhost, then something is wrong)

Thank you techy1 for your reply
it displays the following:

Code:

1356-364 xauth:  creating new authority file

apparently it's still not working

---------- Post updated at 04:49 AM ---------- Previous update was at 04:31 AM ----------

Hi Bakunin, thanks that thread helped me to understand more clearly the different concepts
I Tried to change DISPLAY to my IP:0.0 (my IP= windows IP)
I have added AIX to access control list of windows
but still have the same error

---------- Post updated at 04:54 AM ---------- Previous update was at 04:49 AM ----------

reading other similar problem, I found out that it can be caused by TCP (port 6000) was being blocked, how can I handle this in AIX ?
Moreover I tried :

Code:

>telnet My_Windows_IP
Trying...
telnet: connect: Connection timed out

Please post the EXACT description of this. What does "xauth list" say when executed on the Windows machine? Where did you set the "DISPLAY"-variable? Windows-machine? AIX-machine? What exactly did you do to "add AIX to access control list"? Where did you do that? ....

This may sound petty, but fact is: i have seen many many problems where some "small, insignificant" omissions made all the difference between "not working" and "working".


Ports 6000-6063/udp and 6000-6063/tcp, to be precise. A problem with blocked ports arises only if there are firewalls between the client and the server. Yes, these ports need to be allowed, because the common default firewall rule is to block everything until explicitly allowed. (Otherwise you wouldn't need a firewall at all.)

It is possible to run a firewall and/or packet filter on AIX (IPSec, IPtables, ...), but this is unlikely. Most probably the firewall (if there is one) is a separate machine and you need the firewall admin to configure the rule that the relevant ports are unobstructed.


This can have possible reasons: firewall, as above; telnet daemon not running on Windows (more likely), misconfigured routing table (less likely, but possible) and probably some more. Without more information it is anybodies guess.

I hope this helps.

bakunin