I'm installing SuSE 9.2 on a system here. The installation goes fine.
after reboot, I can start X just fine. I can also use CygwinX from my
Windows machine and connect using xwin. Everything is great!!

Then we take that same hard disk, move it to a new machine (because we use
a separate machine for Linux installation), but when we boot that machine,
though Xwindows itself starts fine, when we try to run any other
application, or connect from CygwinX, we get the dreaded "cannot connect to
XServer" failure.

I looked at the environment, and the DISPLAY environment variable is not
present. If I manually define this variable, I can run applications
locally, but I still cannot log in remotely via CygwinX (because it is
using a different display number...).

Why is the DISPLAY variable disappearing when we move the drive?? And why
is DISPLAY not defined if Xwindows is in fact running?? Can anyone help me
with this??



----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= East/West-Coast Server Farms - Total Privacy via Encryption =---

Daniel Miller <dan@imi-test.com> did eloquently scribble:
> I'm installing SuSE 9.2 on a system here. The installation goes fine.
> after reboot, I can start X just fine. I can also use CygwinX from my
> Windows machine and connect using xwin. Everything is great!!
>
> Then we take that same hard disk, move it to a new machine (because we use
> a separate machine for Linux installation), but when we boot that machine,
> though Xwindows itself starts fine, when we try to run any other
> application, or connect from CygwinX, we get the dreaded "cannot connect to
> XServer" failure.
>
> I looked at the environment, and the DISPLAY environment variable is not
> present. If I manually define this variable, I can run applications
> locally, but I still cannot log in remotely via CygwinX (because it is
> using a different display number...).
>
> Why is the DISPLAY variable disappearing when we move the drive?? And why
> is DISPLAY not defined if Xwindows is in fact running?? Can anyone help me
> with this??

Check the IP address of the machines...
If it's grabbing the ip via dhcp, then.... well, both machines have
different network cards, with different MAC addresses, so the DHCP server
will be assigning them different addresses... The cygwin is still trying to
contact the machine you moved the disk from.

Try setting the up address to a fixed IP, see if that fixes it.

--
| |What to do if you find yourself stuck in a crack|
| spike1@freenet.co.uk |in the ground beneath a giant boulder, which you|
| |can't move, with no hope of rescue. |
|Andrew Halliwell BSc(hons)|Consider how lucky you are that life has been |
| in |good to you so far... |
| Computer Science | -The BOOK, Hitch-hiker's guide to the galaxy.|

spike1@freenet.co.uk wrote in news:4vnej2-h74.ln1@ridcully.fsnet.co.uk:

> Daniel Miller <dan@imi-test.com> did eloquently scribble:
>> I'm installing SuSE 9.2 on a system here. The installation goes
>> fine. after reboot, I can start X just fine. I can also use CygwinX
>> from my Windows machine and connect using xwin. Everything is
>> great!!
>>
>> Then we take that same hard disk, move it to a new machine (because
>> we use a separate machine for Linux installation), but when we boot
>> that machine, though Xwindows itself starts fine, when we try to run
>> any other application, or connect from CygwinX, we get the dreaded
>> "cannot connect to XServer" failure.
>>
>> I looked at the environment, and the DISPLAY environment variable is
>> not present. If I manually define this variable, I can run
>> applications locally, but I still cannot log in remotely via CygwinX
>> (because it is using a different display number...).
>>
>> Why is the DISPLAY variable disappearing when we move the drive??
>> And why is DISPLAY not defined if Xwindows is in fact running?? Can
>> anyone help me with this??
>
> Check the IP address of the machines...
> If it's grabbing the ip via dhcp, then.... well, both machines have
> different network cards, with different MAC addresses, so the DHCP
> server will be assigning them different addresses... The cygwin is
> still trying to contact the machine you moved the disk from.
>
> Try setting the up address to a fixed IP, see if that fixes it.
>
Okay, we'll try that. What we've typically been doing with these systems
is, when we move a disk to a new machine, we delete the Ethernet
interface completely, then add it back in and re-configure it. However,
maybe names don't get resolved properly when we do that. We'll try
static IP and see what happens.

Dan Miller




----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= East/West-Coast Server Farms - Total Privacy via Encryption =---

spike1@freenet.co.uk wrote in news:4vnej2-h74.ln1@ridcully.fsnet.co.uk:

> Daniel Miller <dan@imi-test.com> did eloquently scribble:
>> I'm installing SuSE 9.2 on a system here. The installation goes
>> fine. after reboot, I can start X just fine. I can also use CygwinX
>> from my Windows machine and connect using xwin. Everything is
>> great!!
>>
>> Then we take that same hard disk, move it to a new machine (because
>> we use a separate machine for Linux installation), but when we boot
>> that machine, though Xwindows itself starts fine, when we try to run
>> any other application, or connect from CygwinX, we get the dreaded
>> "cannot connect to XServer" failure.
>>
>> I looked at the environment, and the DISPLAY environment variable is
>> not present. If I manually define this variable, I can run
>> applications locally, but I still cannot log in remotely via CygwinX
>> (because it is using a different display number...).
>>
>> Why is the DISPLAY variable disappearing when we move the drive??
>> And why is DISPLAY not defined if Xwindows is in fact running?? Can
>> anyone help me with this??
>
> Check the IP address of the machines...
> If it's grabbing the ip via dhcp, then.... well, both machines have
> different network cards, with different MAC addresses, so the DHCP
> server will be assigning them different addresses... The cygwin is
> still trying to contact the machine you moved the disk from.
>
> Try setting the up address to a fixed IP, see if that fixes it.
>
Okay, this just keeps getting more exciting!!

1. I tried static IP address, no effect
2. I tried moving the hard disk back to the original machine, where it
*had* worked previously, deleted the Ethernet interface and added it back
in, tried both static and DHCP addresses;

In *all* cases, I cannot run Xwindows applications from the local
machine, $DISPLAY is undefined.

Something that we're doing on these machines causes $DISPLAY to not get
generated, even though X is in fact running. What can cause this??





----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= East/West-Coast Server Farms - Total Privacy via Encryption =---

spike1@freenet.co.uk wrote in news:4vnej2-h74.ln1@ridcully.fsnet.co.uk:

> Daniel Miller <dan@imi-test.com> did eloquently scribble:
>> I'm installing SuSE 9.2 on a system here. The installation goes
>> fine. after reboot, I can start X just fine. I can also use CygwinX
>> from my Windows machine and connect using xwin. Everything is
>> great!!
>>
>> Then we take that same hard disk, move it to a new machine (because
>> we use a separate machine for Linux installation), but when we boot
>> that machine, though Xwindows itself starts fine, when we try to run
>> any other application, or connect from CygwinX, we get the dreaded
>> "cannot connect to XServer" failure.
>>
>> I looked at the environment, and the DISPLAY environment variable is
>> not present. If I manually define this variable, I can run
>> applications locally, but I still cannot log in remotely via CygwinX
>> (because it is using a different display number...).
>>
>> Why is the DISPLAY variable disappearing when we move the drive??
>> And why is DISPLAY not defined if Xwindows is in fact running?? Can
>> anyone help me with this??
>
> Check the IP address of the machines...
> If it's grabbing the ip via dhcp, then.... well, both machines have
> different network cards, with different MAC addresses, so the DHCP
> server will be assigning them different addresses... The cygwin is
> still trying to contact the machine you moved the disk from.
>
> Try setting the up address to a fixed IP, see if that fixes it.
>
Another note is that this appears to be a SuSE 9.2 issue; we just did an
identical install with SuSE 9.1 and we don't have any of these
problems...



----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= East/West-Coast Server Farms - Total Privacy via Encryption =---

spike1@freenet.co.uk wrote in news:4vnej2-h74.ln1@ridcully.fsnet.co.uk:

> Daniel Miller <dan@imi-test.com> did eloquently scribble:
>> I'm installing SuSE 9.2 on a system here. The installation goes
>> fine. after reboot, I can start X just fine. I can also use CygwinX
>> from my Windows machine and connect using xwin. Everything is
>> great!!
>>
>> Then we take that same hard disk, move it to a new machine (because
>> we use a separate machine for Linux installation), but when we boot
>> that machine, though Xwindows itself starts fine, when we try to run
>> any other application, or connect from CygwinX, we get the dreaded
>> "cannot connect to XServer" failure.
>>
>> I looked at the environment, and the DISPLAY environment variable is
>> not present. If I manually define this variable, I can run
>> applications locally, but I still cannot log in remotely via CygwinX
>> (because it is using a different display number...).
>>
>> Why is the DISPLAY variable disappearing when we move the drive??
>> And why is DISPLAY not defined if Xwindows is in fact running?? Can
>> anyone help me with this??
>
> Check the IP address of the machines...
> If it's grabbing the ip via dhcp, then.... well, both machines have
> different network cards, with different MAC addresses, so the DHCP
> server will be assigning them different addresses... The cygwin is
> still trying to contact the machine you moved the disk from.
>
> Try setting the up address to a fixed IP, see if that fixes it.
>
Another note is that this appears to be a SuSE 9.2 issue; we just did an
identical install with SuSE 9.1 and we don't have any of these
problems...



----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= East/West-Coast Server Farms - Total Privacy via Encryption =---

On 19 Apr 2005 13:02:53 -0500, Daniel Miller
<dan@imi-test.com> wrote:>
> In *all* cases, I cannot run Xwindows applications from the local
> machine, $DISPLAY is undefined.
>
> Something that we're doing on these machines causes $DISPLAY to not get
> generated, even though X is in fact running. What can cause this??
>
>
You are in a shell that is not a child of the X server.
If X starts with a window manager or an xterm, they should inherit
$DISPLAY.


--
"I deleted a file from my PC last week and I have just realized that I
need it. If I turn my system clock back two weeks will I have my file
back again?"

Bill Marcum <bmarcum@iglou.com.urgent> wrote in news:ngcgj2-3qv.ln1
@don.localnet:

> On 19 Apr 2005 13:02:53 -0500, Daniel Miller
> <dan@imi-test.com> wrote:>
>> In *all* cases, I cannot run Xwindows applications from the local
>> machine, $DISPLAY is undefined.
>>
>> Something that we're doing on these machines causes $DISPLAY to not get
>> generated, even though X is in fact running. What can cause this??
>>
>>
> You are in a shell that is not a child of the X server.
> If X starts with a window manager or an xterm, they should inherit
> $DISPLAY.
>
Hmmm... well, whatever the problem is, it only exists with SuSE 9.2; we
went back to SuSE 9.1, installed it exactly the same way, installed all the
same software on it, and we *never* have these connection problems. Cygwin
connects every time, with no argument, and the DISPLAY variable never
disappears on us, so our applications just work. I guess that'll just be
our solution for now.


----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

Bill Marcum <bmarcum@iglou.com.urgent> wrote in news:ngcgj2-3qv.ln1
@don.localnet:

> On 19 Apr 2005 13:02:53 -0500, Daniel Miller
> <dan@imi-test.com> wrote:>
>> In *all* cases, I cannot run Xwindows applications from the local
>> machine, $DISPLAY is undefined.
>>
>> Something that we're doing on these machines causes $DISPLAY to not get
>> generated, even though X is in fact running. What can cause this??
>>
>>
> You are in a shell that is not a child of the X server.
> If X starts with a window manager or an xterm, they should inherit
> $DISPLAY.
>
Hmmm... well, whatever the problem is, it only exists with SuSE 9.2; we
went back to SuSE 9.1, installed it exactly the same way, installed all the
same software on it, and we *never* have these connection problems. Cygwin
connects every time, with no argument, and the DISPLAY variable never
disappears on us, so our applications just work. I guess that'll just be
our solution for now.



----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----