Cygwin/X has problem when running on IBM X32 ThinkPad
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Cygwin/X has problem when running on IBM X32 ThinkPad
I have an IBM ThinkPad X32 , with Microsoft Windows XP installed. Here is the hardware configurations:
CPU 1.7GHz, Memory 256MB, 1000Mbps NIC.
To login into a remote Linux host with XMDCP, I also installed Cygwin/X to this machine. The problem is :
It takes the machine about ten minutes to pass the login screen, almost about ten minutes or even longer. But this process does not take more than 20 second on a desktop machine running Windows2000.
Later I upgrade memory to 512MB, but the problem is still not solved!
This is a generic problem I have seen with cygwin, but if your Windows username has spaces, then cygwin will try to use that name, and this can goof some stuff up in a weird way.
I use cygwin/X on XP all the time, so its not XP. Hardware is likely not the problem either, b/c I think cygwin/X uses pseudo-drivers. Be sure your windows user name has no spaces, and your DISPLAY env variable is set properly.
Does Xmdcp tunnel the X packets like ssh can? or send them straight to the XP box? I am not familiar with Xmdcp and a quick google turns up a bunch of French pages.
Win2k has no default firewall but WinXP SP2 does I believe. The XP firewall would block non-tunneled, regular X packets, unless you specifically told it not. Even if the all the firewall is opened, you gotta do "xhost +" (unsafe) in cygwin to allow remote X connections to your cygwin/X server.
1. Check if your cygwin/X server works locally by running "export DISPLAY=:0; xterm&", assuming X is running on display :0 (run "startx -- :0" first).
2. See if it works through a tunneled ssh connection to a Linux ssh server.
3. If Xmdcp is non tunneling. its probably XP's firewall, or Norton internet security, or one of the other hundred windows hoops you gotta jump through to run an X server on your WinXP box.
I use cygwin/X on XP - on an IBM A30 laptop, as it happens - every day. What is Xmdcp? I use ssh to tunnel into my Linux server; works well and is quite fast.
I use cygwin/X on XP all the time, so its not XP. Hardware is likely not the problem either, b/c I think cygwin/X uses pseudo-drivers. Be sure your windows user name has no spaces, and your DISPLAY env variable is set properly.
Does Xmdcp tunnel the X packets like ssh can? or send them straight to the XP box? I am not familiar with Xmdcp and a quick google turns up a bunch of French pages.
Win2k has no default firewall but WinXP SP2 does I believe. The XP firewall would block non-tunneled, regular X packets, unless you specifically told it not. Even if the all the firewall is opened, you gotta do "xhost +" (unsafe) in cygwin to allow remote X connections to your cygwin/X server.
1. Check if your cygwin/X server works locally by running "export DISPLAY=:0; xterm&", assuming X is running on display :0 (run "startx -- :0" first).
2. See if it works through a tunneled ssh connection to a Linux ssh server.
3. If Xmdcp is non tunneling. its probably XP's firewall, or Norton internet security, or one of the other hundred windows hoops you gotta jump through to run an X server on your WinXP box.
XDMCP is a network protocol to let you to connect to the desktop of a remote linux host.
In fact, the login process does not fail, it just takes a long time. So does the logout process.
I also doubt it is the firewal that makes the trouble; I shut down the firewall and the problem is not solved !
I will try the ways you tell me, and tell you the result later.
I use cygwin/X on XP - on an IBM A30 laptop, as it happens - every day. What is Xmdcp? I use ssh to tunnel into my Linux server; works well and is quite fast.
Yes, my "ssh" also works well and is fast, it is the XDMCP that makes the trouble.
I don't think people use XDMCP to connect remotely very much anymore. SSH's X forwarding is secure and automatically handles the forwarding of the display without user configuration. Do "ssh -Y user@host" when connecting and you can run any X apps and they will use your X server.
I did as you told me, but the trouble did not disappear. Later I carefully checked the rules of my firewall, and found I it was the firewall rules that made the trouble. I add a new rule that allow local access to port 1157, then everything is ok!
But the trouble of XDMCP that I mentioned above is still there!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.