Find the answer to your Linux question:
Results 1 to 7 of 7
Hello, I'm having a strange issue with networking a Linux and Unix machine. The Linux distribution is Red Hat, and the Unix uses tsch rather than Bash. I'm trying to ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Sep 2012
    Posts
    10

    Help! Networking Problem with Linux and Unix


    Hello,

    I'm having a strange issue with networking a Linux and Unix machine. The Linux distribution is Red Hat, and the Unix uses tsch rather than Bash. I'm trying to get the Linux to get access to the Unix's terminal and get visuals through X11 forwarding.

    As of now, neither the Linux nor Unix has an internet connection. They're connecting directly through a network switch. They can SSH into one another fine, but lack X11 forwarding (for visuals) and I can't enable it as I can't download the SSH server and config files.

    As a result, I'm trying to get the Linux to access the Unix through telnet (I know it's unsecure but like I said there's no internet connection). Normally you would just telnet onto the Unix and use the tsch command:
    Code:
    setenv DISPLAY <Linux's IP Address>:0
    However, when I call this command and then try to open a terminal, it claims it cannot find the display. I already used "xhost +". I though the problem might be in xauth but when I try to generate a key (xauth generate) it once again claims it cannot detect the display.

    Both computers have their networks up and both computers can ping one another, but for some reason the Unix simply can't detect the display of the Linux.

    Any help would be welcome.

  2. #2
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    Hey,

    Yeah, i would have tried the xauth stuff, too. Maybe it is that the X server has the nolisten option enabled? Check in the output of "ps auxww|grep X". Also, is there anything in the X server logs?

  3. #3
    Just Joined!
    Join Date
    Sep 2012
    Posts
    10
    Quote Originally Posted by atreyu View Post
    Hey,

    Yeah, i would have tried the xauth stuff, too. Maybe it is that the X server has the nolisten option enabled? Check in the output of "ps auxww|grep X". Also, is there anything in the X server logs?
    Thank you for your reply.

    Unfortunately I don't know how to change X server configuration. Do you know where the files would be located on a Unix machine? Also I'll try that command as soon as I have access to the computer.

    EDIT: Alright, I have access to the computer, but that command doesn't work in tsch.

    EDIT2: I figured out the commands myself. Turns out it was the receiving Linux that had a problem, not the Unix server. Thanks for your help!
    Last edited by Dodosaur; 06-11-2013 at 04:09 AM.

  4. #4
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    Quote Originally Posted by Dodosaur View Post
    EDIT2: I figured out the commands myself. Turns out it was the receiving Linux that had a problem, not the Unix server.
    Hey, just glad you got it sorted! For posterity, would you mind terribly posting what you found to be your problem, and your ultimate solution? It may be a hidden gem to some seeker of wisdom in the distant googley future...(and you've got me curious).

    Also, note that when you are satisfied with a thread, you can mark it as Solved using the Thread Tools link at the top of the page. It's no big deal if you don't, but again, it helps others surfing the boards and/or using a search engine to find answers.

  5. #5
    Just Joined!
    Join Date
    Sep 2012
    Posts
    10
    Quote Originally Posted by atreyu View Post
    Hey, just glad you got it sorted! For posterity, would you mind terribly posting what you found to be your problem, and your ultimate solution? It may be a hidden gem to some seeker of wisdom in the distant googley future...(and you've got me curious).

    Also, note that when you are satisfied with a thread, you can mark it as Solved using the Thread Tools link at the top of the page. It's no big deal if you don't, but again, it helps others surfing the boards and/or using a search engine to find answers.
    On the receiving end make sure you called "xhost +" and make sure the computer has an xauth key to the server. I'm no sure if that was supposed to fix it but it did somehow.

  6. #6
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    Quote Originally Posted by Dodosaur View Post
    On the receiving end make sure you called "xhost +" and make sure the computer has an xauth key to the server. I'm no sure if that was supposed to fix it but it did somehow.
    i read that you had run "xhost +", but perhaps you did it on the remote side, instead of on the local side? It needs to be run on the local side, by the user who "owns" the X session to which the remote client will attempt to connect to (when running "export DISPLAY=blah" and exporting back the display, etc.).

  7. #7
    Just Joined!
    Join Date
    Sep 2012
    Posts
    10
    Quote Originally Posted by atreyu View Post
    i read that you had run "xhost +", but perhaps you did it on the remote side, instead of on the local side? It needs to be run on the local side, by the user who "owns" the X session to which the remote client will attempt to connect to (when running "export DISPLAY=blah" and exporting back the display, etc.).
    I *thought* I ran it on both sides, as well as fix the xauth stuff, but apparently I didn't in the same session. Silly mistake I think.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •