QVision or XDM; was: Intriguing sticker on my Jensen [...] - DEC

This is a discussion on QVision or XDM; was: Intriguing sticker on my Jensen [...] - DEC ; Hiya, On April 1st, 3.30 AM (not April Fools joke) Jensen nodenamed Brahms has been set to life, running VMS 7.3-1 with hobbyist license. As expected, the OakVision card is unsupported, so if anyone has any EISA card, that would ...

+ Reply to Thread
Results 1 to 9 of 9

Thread: QVision or XDM; was: Intriguing sticker on my Jensen [...]

  1. QVision or XDM; was: Intriguing sticker on my Jensen [...]

    Hiya,

    On April 1st, 3.30 AM (not April Fools joke) Jensen nodenamed Brahms
    has been set to life, running VMS 7.3-1 with hobbyist license.
    As expected, the OakVision card is unsupported, so if anyone has any
    EISA card, that would be supported, laying around and doesn't want to
    trash it- I want it.

    The second question is: I enabled and fired up XDM service, but it
    doesn't seem to accept connections nor broadcast. How do I edit XDM
    config so it would?

    Rambo


  2. Re: QVision or XDM; was: Intriguing sticker on my Jensen [...]

    Rambo wrote:
    > I enabled and fired up XDM service, but it
    > doesn't seem to accept connections nor broadcast. How do I edit XDM
    > config so it would?


    Perhaps reading the documentation would help? :-)
    http://h71000.www7.hp.com/doc/73fina...l#h1_xdm_files

    cu,
    Martin
    --
    One OS to rule them all | Martin Vorlaender | OpenVMS rules!
    One OS to find them | work: mv@pdv-systeme.de
    One OS to bring them all | http://www.pdv-systeme.de/users/martinv/
    And in the Darkness bind them.| home: martin@radiogaga.harz.de

  3. Re: QVision or XDM; was: Intriguing sticker on my Jensen [...]

    > Perhaps reading the documentation would help? :-)
    > http://h71000.www7.hp.com/doc/73fina...l#h1_xdm_files


    Thanks, but it seems that most of U*X X servers use TCP instead of
    UDP, so while my
    oldish Envizex still works, I can't connect with any "modern" system.

    Is there a way to enable TCP transport for XDM?



  4. Re: QVision or XDM; was: Intriguing sticker on my Jensen [...]

    In article <1175888411.712060.70750@d57g2000hsg.googlegroups.c om>, "Rambo" writes:
    >The second question is: I enabled and fired up XDM service, but it
    >doesn't seem to accept connections nor broadcast. How do I edit XDM
    >config so it would?


    $ COPY/LOG SYS$SPECIFIC:[TCPIP$XDM]*.TEMPLATE SYS$SPECIFIC:[TCPIP$XDM].TXT
    $ EDIT them
    $ TYPE SYS$SPECIFIC:[TCPIP$XDM]XDM_CONFIG.CONF
    !
    ! Default SYS$SPECIFIC:[TCPIP$XDM]XDM_CONFIG.CONF file
    !
    DisplayManager.accessFile: SYS$SPECIFIC:[TCPIP$XDM]XACCESS.TXT
    DisplayManager.keyFile: SYS$SPECIFIC:[TCPIP$XDM]XDM_KEYS.TXT
    DisplayManager.servers: SYS$SPECIFIC:[TCPIP$XDM]XSERVERS.TXT
    DisplayManager*RemoveDomainname: true

    $ TYPE SYS$SPECIFIC:[TCPIP$XDM]XACCESS.TXT
    ....

    * #any host can get a login window

    ....

    as a start

    $ TCPIP SHOW SERVICE XDM/FULL/PERMANENT

    Service: XDM

    Port: 177 Protocol: UDP Address: 0.0.0.0
    Inactivity: 0 User_name: TCPIP$XDM Process: TCPIP$XDM
    Limit: 1

    File: TCPIP$SYSTEM:TCPIP$XDM_RUN.COM
    Flags: TCPIP

    Socket Opts: Rcheck Scheck
    Receive: 0 Send: 0

    Log Opts: Acpt Actv Dactv Conn Error Exit Logi Logo Mdfy Rjct TimO Addr
    File: SYS$SPECIFIC:[TCPIP$XDM]TCPIP$XDM_RUN.LOG

    Security
    Reject msg: not defined
    Accept host: 0.0.0.0
    Accept netw: 0.0.0.0

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

  5. Re: QVision or XDM; was: Intriguing sticker on my Jensen [...]

    In article <1175945438.780057.34710@n59g2000hsh.googlegroups.c om>, "Rambo" writes:
    >> Perhaps reading the documentation would help? :-)
    >> http://h71000.www7.hp.com/doc/73fina...l#h1_xdm_files

    >
    >Thanks, but it seems that most of U*X X servers use TCP instead of UDP, so while my
    >oldish Envizex still works, I can't connect with any "modern" system.
    >
    >Is there a way to enable TCP transport for XDM?


    Don't know. Had never the need to enable the TCP transport though I use
    "modern" systems. Maybe defining another service on TCP port 177 may help

    $ TCPIP SET SERVICE/FILE=TCPIP$SYSTEM:TCPIP$XDM_RUN.COM/PROTOCOL=TCP/...

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

  6. Re: QVision or XDM; was: Intriguing sticker on my Jensen [...]

    Rambo wrote:
    > but it seems that most of U*X X servers use TCP instead of
    > UDP, so while my oldish Envizex still works, I can't connect
    > with any "modern" system.
    >
    > Is there a way to enable TCP transport for XDM?


    Sorry, I have no idea. I always thought that XDM was UDP-based.
    The xdm manpage on my SuSE 10 system doesn't mention TCP as a
    transport, though the /etc/services file has entries for xdm
    as 177/tcp and 177/udp.

    cu,
    Martin
    --
    One OS to rule them all | Martin Vorlaender | OpenVMS rules!
    One OS to find them | work: mv@pdv-systeme.de
    One OS to bring them all | http://www.pdv-systeme.de/users/martinv/
    And in the Darkness bind them.| home: martin@radiogaga.harz.de

  7. Re: QVision or XDM; was: Intriguing sticker on my Jensen [...]

    > > Is there a way to enable TCP transport for XDM?
    >
    > Sorry, I have no idea. I always thought that XDM was UDP-based.
    > The xdm manpage on my SuSE 10 system doesn't mention TCP as a
    > transport, though the /etc/services file has entries for xdm
    > as 177/tcp and 177/udp.


    Well, it turns out you and Peter may be right- it's something else...
    I'm firing up tcp services, XDM is enabled- I can connect from Envizex
    but with Xorg's Xnest (X11R7.1) I'm getting
    root@beethoven:~# Xnest :1 -query brahms -geometry 1200x900
    [...]
    AUDIT: Sat Apr 7 19:29:18 2007: 5558 Xnest: client 1 rejected from IP
    192.168.1.30

    Needless to say, it's the only system that refuses to cooperate that
    way

    Rambo


  8. Re: QVision or XDM; was: Intriguing sticker on my Jensen [...]

    Rambo wrote:
    > I'm firing up tcp services, XDM is enabled- I can connect from Envizex
    > but with Xorg's Xnest (X11R7.1) I'm getting
    >
    > root@beethoven:~# Xnest :1 -query brahms -geometry 1200x900
    > [...]
    > AUDIT: Sat Apr 7 19:29:18 2007: 5558 Xnest: client 1 rejected from IP
    > 192.168.1.30


    Can't try it here (no Xnest), but you could look into the DECwindows
    system for error messages:
    - there's SYS$MANAGERECW$SERVER_0_ERROR.LOG (not sure on that filename)
    that tends to have log entries for X security issues
    - VMS' XDM probably has its own logfile; you can find its location with
    a $TCPIP SHOW SERVICE /FULL XDM
    - after $REPLY/ENABLE (with sufficient privileges) there might be messages
    in the console.

    HTH,
    Martin
    --
    One OS to rule them all | Martin Vorlaender | OpenVMS rules!
    One OS to find them | work: mv@pdv-systeme.de
    One OS to bring them all | http://www.pdv-systeme.de/users/martinv/
    And in the Darkness bind them.| home: martin@radiogaga.harz.de

  9. Re: QVision or XDM; was: Intriguing sticker on my Jensen [...]

    Google's refused to post, so retrying...

    > - there's SYS$MANAGERECW$SERVER_0_ERROR.LOG (not sure on that filename)


    This one is for local screen, however I did some more experimenting
    and found the
    solution: by default, even when not authenticating, access control
    lists are enabled by
    default on new X releases.

    running
    X :1 -ac -query brahms
    brought me the xdm login screen. Now if anyone could tell if it's
    possible to get dtlogin
    instead, I'd be happiest man on Earth [j/k] :-D

    Rambo


+ Reply to Thread