• Can't close or stealth port 22

    From Black Baptist@21:1/5 to All on Sat Dec 10 13:21:23 2016
    I'm running windows 10 pro x64 I've tried port forwarding the port in
    my Home Hub 3000 to 127.0.0.1 and closing the port via windows
    firewall I've done a port scan via GRC.com and a friend did a port
    scan along with other sites and all still show port 22 as open I know
    the port is SSH and I'm not running any RDP or SSH server. Any help on
    this issue would be grateful.
    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Char Jackson@21:1/5 to All on Sun Dec 11 00:14:38 2016
    On Sat, 10 Dec 2016 13:21:23 -0400, Black Baptist <pray@the.church.com>
    wrote:

    I'm running windows 10 pro x64 I've tried port forwarding the port in
    my Home Hub 3000 to 127.0.0.1 and closing the port via windows
    firewall I've done a port scan via GRC.com and a friend did a port
    scan along with other sites and all still show port 22 as open I know
    the port is SSH and I'm not running any RDP or SSH server. Any help on
    this issue would be grateful.

    Port forwarding and Windows firewalls are all on the LAN side of the
    device. Since nothing you've tried seems to change the status of port
    22, my guess would be that your 3000 itself has port 22 open, possibly
    so that your ISP can do remote management.

    It's easy enough to test that theory by disconnecting all PCs from the
    LAN side of the 3000, wired and wireless, then have your buddy run the
    scan again. If port 22 is still open, it's open on the 3000, not on a
    device behind the 3000.

    As for the Home Hub 3000, Google says it's a combo modem/router/access point/switch. Ugh, I hate combo units. They tend to offer very little
    control to the end user.
    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)