Reflection X

[Michelle Barton]

I have a server at a remote location that I want to use ReflectionX to log in to. I attempt to log on just like I do on my other servers, and it acts like it's working but the terminal screen never appears. I've tried this remotely and also on an NT workstation (using Terminal Services) local to the server. Same thing, no error messages or anything.

I need to resolve this ASAP as I need to perform some Omniback admin.

Thanks,
Michelle

[Dave Hutton]

I've only seen this where I exported my DISPLAY to the wrong place. It gives the feeling its working, but the motif never shows up on my pc. Kind of what your suggesting.

Pretty obvious but sometimes those kind of things are overlooked.

Dave

[Sanjay_6]

Hi,

You can do it this way.

From your desktop, do a reflection x to any workstation / server close to you.
Do a telnet to the remote server from this window.
in the remote server telnet window, export the display,
# export DISPLAY=your_win_workstation_ip:0.0
# xomni &

You should be able to see the xomni session on your desktop.

Hope this helps.

Regds

[A. Clay Stephenson]

How are you trying to connect XDMCP (Broadcast,Direct,Indirect)? Probably the most foolproof method is to start Reflection X, open a telnet session to your UNIX host, login, and export DISPLAY=PC_IP_ADDRESS:0.0

I would then start xclock; if that works then xomni should start.

I would look under Relection X -> X Server Settings -> Server and View the log file. This will probably point out your error.

If this were me, I would use the Windows OB2/DP client to access my Unix Cell Server.
This will be much faster than using the Motif version.

[Mark Grant]

Also,

Make sure you host can resolve your IP address. It doesn't matter what it resolves to, as long as it resolves.

To test, add your PC ip address to /etc/hosts

[John Collier]

Michelle,

The could be some issues to consider beyond what you have been told. If you are using the default CDE desktop, then all should be good with the above.

If you have Gnome installed, then we would need to know that.

have you ever been able to use your Reflections X to connect to this box from anywhere?

John

[Michelle Barton]

I can't get the reflection X telnet session open.

I tried opening from here and get this error message:

Can't open display: 10.200.4.47:0.0
couldn't find per display information

Thanks!

[Michelle Barton]

I used to be able to connect Reflection X until we moved locations and began using a VPN tunnel.

Michelle

[Dave Hutton]

I wonder if your not running into acl problems. Maybe X/motif ports are now blocked after you went with your vpn solution? Is there a firewall between you and your server?


Dave

[Michelle Barton]

Here's the logfile:

Feb 26 10:40:48: Starting server 'C:\Program Files\Reflection\Rx.exe' (RX271)
Feb 26 10:40:48: Server startup command line parameters: '-c "C:\My Documents\Reflection\uxwdbs.rxc"' (RX280)
Feb 26 10:40:50: Choosing PFD 5 for window visual 0x00000020
Feb 26 10:40:50: Choosing PFD 15 for pixmap visual 0x00000020
Feb 26 10:40:50: Choosing PFD 7 for window visual 0x00000021
Feb 26 10:40:50: Choosing PFD 15 for pixmap visual 0x00000021
Feb 26 10:40:50: Choosing PFD 9 for window visual 0x00000022
Feb 26 10:40:50: Choosing PFD 29 for pixmap visual 0x00000022
Feb 26 10:40:50: Choosing PFD 11 for window visual 0x00000023
Feb 26 10:40:50: Choosing PFD 29 for pixmap visual 0x00000023
Feb 26 10:40:51: rxstart.exe (508) - Client startup is initializing (RX5006)
Feb 26 10:40:51: rxstart.exe (44c) - Client startup processing hpterm (uxwdbs via TELNET) (RX5129)
Feb 26 10:46:13: rxstart.exe (508) - Client startup is closing down (RX5007)
Feb 26 10:57:22: rxstart.exe (530) - Client startup is initializing (RX5006)
Feb 26 10:57:22: rxstart.exe (5e0) - Client startup processing hpterm (10.200.1.20 via TELNET) (RX5129)
Feb 26 11:02:42: rxstart.exe (530) - Client startup is closing down (RX5007)

[Michelle Barton]

Yes there is a firewall between me and the server. However, I tried it locally to the server using windows which doesn't go out to the firewall.

Michelle

[Dave Hutton]

I'm used to hummingbird. But theres a process on my windows box that I need running to accept X data. Basically a X-server on my pc.

Maybe thats not running?

[Michael Schulte zur Sur]

Hi,

reflection is waiting for a prompt, which if it does not appear, will stall it.
Are there any changes recently to .profile?

Michael

[Michelle Barton]

no changes that I'm aware of.

Michelle

[Michael Schulte zur Sur]

Hi,

can you login via telnet? If so, are there any inputs you have to make to get to the shell, or is there a menu of some kind, which is started automatically?

Michael

[Michelle Barton]

I can login through telnet, just not Xwindows. I'm wondering if it's a port issue or security thing.

Michelle

[Michael Schulte zur Sur]

One more thing,

I think, it has to do with vpn and the firewall. We use that too and I was told, that the firewall would block X-Windows.

so get to your firewall guys. ;-)

Michael

[Lisa Mauer]

We had to open port 6000. First, Reflection X uses the X11 Display Manager Control Protocol (XDMCP) to treat your Windows desktop as an X terminal accessing a Unix-based host. Using XDMCP isn't a problem if you're accessing X Window applications over an intranet, where X clients can access the X server directly without going through a firewall or using Network Address Translation (NAT). However, when accessing a a remote Unix host through a router, firewall or over the Internet, you need to understand that XDMCP uses UDP port 177 and TCP port 6000 for communications. So if your Reflection X sessions are going through a router or a firewall, those ports must be open for internal users so that the remote host can respond to your desktop sessions.