Click to See Complete Forum and Search --> : Does anyone know of a X-win32 application for Linux?


Mears
10-19-2001, 01:16 PM
I would like to log in remotely to the computer science servers on my university remotely in a windowed environment. Does anyone know of a program that is similar to X-win32 that is available on Linux?

bdg1983
10-19-2001, 04:04 PM
VNC though I don't have the url handy.

Just do a search for VNC at freshmeat.net

Strike
10-20-2001, 04:06 AM
Um, XWin32 is an X server for Windows. XFree86 (http://www.xfree86.org) is what you want, as it is the most popular X server for Linux.

bdg1983
10-20-2001, 05:43 AM
XFree come with Xnest that can do this.

Xnest :1 -query 172.16.1.145 &

172.16.1.145 would be the address of the server you are trying to connect to.

Mears
10-20-2001, 12:33 PM
Here is what I've been trying to do:

X :1 -query arctic.cse.msu.edu

However, all it would do is bring up a blank black and white pok-a-dot screen with the mouse icon. I know it connected because the mouse icon changed to the cross hairs that the Unix machines over there used. Since, it requires a SSH connection, somone told me that I needed to edit the file ssh_config and change ForwardX11 to yes. I found two instances of ForwardX11 in the file. The first was inbetween *Host and Host* and was turned off, then at the bottom of the page there was another ForwardX11 that was set to yes. I ended up changing the other ForwardX11 to yes as well, but when I entered the command X :1 -query arctic.cse.msu.edu it still brought up the blank screen and wouldn't let me do anything else. Anyone have any ideas?

bdg1983
10-20-2001, 01:44 PM
Here's an article from Caldera's knowledgebase.

Description:

Can I get a graphical login to a remote computer?

Solution:

Remote X-sessions are possible, but recommended only for fast connections with plenty of bandwidth, as a graphical session requires alot of communication.

NOTE: To start additional X-session you will need to be logged in as the root user.

In short, a remote session requires the cooperation of both computers. The X access of the computer you wish to access must be modified to include any client that you want to connect from,
and you must start a new X-session on your local computer.

To allow a graphical connection to a remote linux box, the computer you wish to connect to must allow graphical connections from your system. This is done by editing the Xaccess file in
/etc/X11/kdm/ to allow the client computer(s) -- None is the default for Caldera Openlinux, but uncommenting the line

#*#any host can get a login window

allows all clients to connect, which may be a security risk, so you may want to specify clients. For this faq, we will just uncomment this line (it is the first non-comment commented line). Once
this change is made, you will need to re-start the X-server. You can use the login manager, or just use a terminal to go to runlevel 3 then back to 5:

init 3
init 5

Second, the client will execute this command:
X :1 -query 192.168.1.5

The numbers will be different for your system; the ":1" is the next X-session - If you already have 2 X-sessions, use :2, etc. The ip, obviously is the system you want to connect to - this can be a
fully qualified domain name if it is known by your system. This session will be on the next virtual terminal (typically F9) and will be the active one until you switch back.

To start a new X-session in a window of your current X-session (nested), use the Xnest command in place of X:

Xnest :1 -query 192.168.1.5

NOTES:

- To run this in the background, you just add the ampersand [&], and to disconnect it from a terminal, just [ctrl]-[d] out of the terminal window once it is in the background. If you forgot to send the
process to the background, type [ctrl]-[z], then 'bg' [enter], then [ctrl]-[d] out.

- You can connect to any computer which can run an X-session and which uses standard X protocols, such as SCO unixware. They may require changes to X access as well, but configuring
them is beyond the scope of this faq. Some systems default to allow all clients to connect, in which case you may not need to change anything.

- Firewalls will disrupt this setup. You will need to find out what ports are being used and how to get through before this will work for those systems.

thedexman
10-20-2001, 05:05 PM
This makes the second post today with this question on 2 different boards :)