Hi
EDIT: Added some detail on other things I've tried/seen...
Quite a few people have written about this topic on this forum and elsewhere... There seem to be two camps; those for whom it works without issue and those that cannot get it to work at all. I'm in the latter
. Sorry if I've missed the answer, but here goes...
I am trying to get my HP 16700 headless Logic Analyser to work with an X-Terminal emulator running on my Windows 10 computer. The LA is second hand and I have no way of knowing if it's been meddled with in any way. I have a strong feeling that it
could work (based on partial success, see below). My W10 box is running MobaXTerm. Both systems have static IP address on the same subnet as follows;
LA | 192.168.0.16 |
W10 | 192.168.0.72 |
I think that the "normal" way of getting remote X working is to start a telnet session with the LA and log in like this;
telnet 192.168.0.16
Logic Analysis System
Please Log in as: logic [displayname:0]
login: logic 192.168.0.72:0
Starting Session Manager on display '192.168.0.72:0'
When I do this, four pop-ups appear on the W10 display in quick succession as long as I press "Yes", each showing the prompt attached. The telnet session is closed after about 8 seconds (even if I don't press "Yes").
The fact that my W10 box shows these prompts makes me think that;
- The X Server is running on the W10 box
- The W10 firewall is not blocking anything.
Not withstanding the above, I've tried turning off the firewall and there is no meaningful change in behavior.
An interesting thing I've found is that if I enter the following;
telnet 192.168.0.16
Logic Analysis System
Please Log in as: logic [displayname:0]
login: logic 192.168.0.16:0
Starting Session Manager on display '192.168.0.16:0'
(In other words telnet form the W10 box on to the LA
but start the X Terminal session on the LA), the LA session does indeed start. This to me means that the script or what ever it is that runs when you log in as "logic" does work, it's just that it does not work to a remote X server.
Using a prompt here;
https://www.mattmillman.com/16702b/I've managed to make it work, but this seems like a work around. I'd like to make starting a remote session work as (I feel) it should. For reference, the bones of Matt's solution is to enter the following on the LA;
logic:/home/hplogic> export DISPLAY=192.168.0.31:0.0 (my IP address is .72 of course)
logic:/home/hplogic> vp &
As I say, this works, but to me, I should be able to make the first way work...
I have roamed around the LA file system looking for either an X or maybe HP-UX log of login attempts/results etc but to no avail. I must be missing something here because this must exist; sorry if I have!
I have not enabled "Secure mode" on the LA (System Administration tools -> Security) because I don't feel that I know what I'm doing.
I have read this;
https://xdevs.com/doc/HP_Agilent_Keysight/HP%2016700A%2C%20B%20Help%20Volume.pdfBut this only seems to refer to using one LA to talk with another.... I can't map the information on to my use case. Perhaps I need to read it all again!
The only other thing to say is that I've tried the above with and without a LA session running. In other words, using the LA Session Manager to start (or not start) an "Exclusive session (console or remoteX)".
If anyone has any pointers, I'd be really pleased to hear from you.
Thanks for your attention.
Dave