From owner-freebsd-questions  Wed Mar 29  9:56: 7 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from noc.mainstreet.net (noc.mainstreet.net [207.5.0.45])
	by hub.freebsd.org (Postfix) with ESMTP id E92F537C190
	for <freebsd-questions@FreeBSD.ORG>; Wed, 29 Mar 2000 09:55:20 -0800 (PST)
	(envelope-from mark@noc.mainstreet.net)
Received: (from mark@localhost)
	by noc.mainstreet.net (8.9.2/8.9.2) id JAA24418;
	Wed, 29 Mar 2000 09:55:18 -0800 (PST)
Date: Wed, 29 Mar 2000 09:55:18 -0800 (PST)
Message-Id: <200003291755.JAA24418@noc.mainstreet.net>
From: Mark Kent <mark@noc.mainstreet.net>
To: doc@wcug.wwu.edu
Cc: freebsd-questions@FreeBSD.ORG
In-reply-to: <Pine.LNX.3.96.1000329091523.20404A-100000@sloth> (message from
	David Daugherty on Wed, 29 Mar 2000 09:20:49 -0800 (PST))
Subject: Re: Xwin32
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

== > setenv DISPLAY x.y.z.w:0.0
== > xterm
== >
== > where x.y.z.w is your win box IP address.
== > If that doesn't work then make sure you are
== > actually running xwin32 on the win box...

>> I'm not exactly sure what this does other then storing the remote IP into
>> a var DISPLAY.

X applications need to know where to display, and (in csh at least,
sorry for the shell-specific notation) the "setenv DISPLAY
x.y.z.w:0.0" sets up a variable that X applications look at
to determine where to display.

>> What's happening is X is starting on the server, I can see it running
>> under top.

Server?  top?  Sounds like you are running the X server on the
freeBSD box.  There is no need for this, nor would it affect the
xwin32 on the windows box.  You want to run an X application on a
freeBSD box and display it on a windows box, right?

>> Nothing ever shows up in xwin. And, I keep having to reboot because I'm
>> not sure what to kill to stop X in my ssh window.

ssh?  The fact that xwin32 doesn't work for you but it works for
others is a mystery to you, so start to strip things away.  Drop ssh,
open up telnet, forget about running the X server on the freebsd box.
Treat the freeBSD box as a server snd sit in front of the windows box,
start Xwin32 on the windows box.  Start a telnet window and telnet into the
freebsd box and do:

csh
setenv DISPLAY x.y.z.w:0.0
xterm

where x.y.z.w is your win box IP address.
This is a basic test and once it works you can then
try to get it working the way you really want it to work.

However, the fact that you are using ssh makes me believe that you
might have something (firewall, router with packet filters) between
the windows box and the freebsd box.  Do you?

-mark


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message