Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Can't access remote console

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    38 Posts 3 Posters 4.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • cdsJerryC
      cdsJerry @stephenw10
      last edited by

      @stephenw10 I don't have a way to Copy/paste from that machine but here's a photo of the last lines.screen.jpg

      I'm not familiar with screen.

      1 Reply Last reply Reply Quote 0
      • cdsJerryC
        cdsJerry @stephenw10
        last edited by

        @stephenw10 Was that screen post any help?

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Ok the screenshot looks as expected. Nothing wrong there.

          @stephenw10 said in Can't access remote console:

          I can then open ttyUSB0 with screen /dev/ttyUSB0 115200.
          You may need to use sudo with that depending on your user.
          To escape screen press ctl+a then k then answer y.

          Try connecting to it with screen instead of putty as I showed.

          Steve

          cdsJerryC 1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Reviewing this whole thread it seems likely Putty is just not configured correctly on either Windows or Linux.
            When you click Open and it does nothing or just the Windows error sound it pretty much has to be because it's trying to open something invalid or doesn't have all the settings necessary.

            If screen doesn't work (I believe it will though) lets see some screenshots of your putty config.

            Steve

            1 Reply Last reply Reply Quote 0
            • cdsJerryC
              cdsJerry @stephenw10
              last edited by

              @stephenw10 Tried it with screen. I get an error message "Cannot exec '/dev/ttyUSB0' : No such file or directory

              You said Putty probably isn't configured correctly but I've used Putty to access this same appliance in the past with the same computer (as well as the other four computers we've now also tried).

              I agree that it's trying to open something invalid... because none of the programs is able to communicate with the 3100. It's being non-responsive which makes it invalid. Attached are images from Putty with both Windows and Linux

              Windows putty.jpg Linux Putty.jpg

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Ok when running screen you have to run it using this command:

                screen /dev/ttyUSB0 115200
                

                It looks like you just tried to run /dev/ttyUSB0 dircetly.

                Those Putty screenshots show the serial console settings but not the actual session you're trying to open which will be ssh and nor serial by default.

                Make sure you have set 'serial' in the session section at the top.

                Steve

                cdsJerryC 1 Reply Last reply Reply Quote 0
                • cdsJerryC
                  cdsJerry @stephenw10
                  last edited by

                  @stephenw10 said in Can't access remote console:

                  screen /dev/ttyUSB0 115200

                  That IS the command I was running.

                  I have however gotten back into the remote console. I did another reboot and then use Putty on my original Windows machine and I got into the console. I have access again.

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Ah, good news. Any idea what changed?

                    At least that shows the console port is good still.

                    Steve

                    cdsJerryC 1 Reply Last reply Reply Quote 0
                    • cdsJerryC
                      cdsJerry @stephenw10
                      last edited by

                      @stephenw10 I have no idea. Something in the reboot must have done the trick.

                      The computer was still up and running the same instance of Putty from my earlier tests. All I did was plug in the cable (because it had been plugged into the Linux computer), checked to make sure it was still COM3, and hit connect. I got a blank window (which did not happen before) hit enter a couple of times and was presented a # prompt.

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        Hmm, OK. Well glad you were able to connect.

                        The putty interface can be confusing at times. It's all too easy to think you're opening a serial connection when in fact it's just showing you the serial settings and the session is still set as SSH.

                        Steve

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.