|
What do you mean by "connected to the server using Hummingbird"? Is the Hummingbird you talk about, the Excede X server package? If so, how did you connect to the server?
I sense that you are in the usual confusion about X; distinguishing what is a server and what is a client. In your case, the Hummingbird X server is what runs on your Windows host. The X client is any application that can send its graphics to the X server. In the Windows/Hummingbird Excede scenario, you would typically login to a Linux/UNIX host using something like an SSH or (gasp!) telnet. You would then invoke some application that calls your Windows-hosted X server. Sorry, if this is all stuff you already knew; many people that are new to X find this part unintuative.
There are a couple of places where things can go off the rails. One might be that your SSH client is providing a secure tunnel for the X traffic. If so, your setting the DISPLAY variable to windows_IP:0 will contradict this, and the X server will not receive the client's call. If there is a tunnel, it will probably have created a DISPLAY variable for you, which will look something like 'localhost:dd', where dd is some low positive integer, like 10 or 12. Perhaps your startup shell script has tried to be helpful, and reset the DISPLAY variable.
The other place is that plain, untunelled, X traffic travels on ports 6100, 6101, 6102... for X servers :0, :1, :2, etc. There may be a firewall blocking these ports, which would need to be penetrated. This problem is alleviated by using a SSH tunnel.
--- rod.
Last edited by theNbomr; 02-05-2007 at 06:12 PM.
|
