f



Can't close or stealth port 22

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.
0
Black
12/10/2016 5:21:23 PM
comp.windows.networking.tcp-ip 1889 articles. 0 followers. Post Follow

1 Replies
321 Views

Similar Articles

[PageSpeed] 35

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.

0
Char
12/11/2016 6:14:38 AM
Reply: