NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Night Hawk R8000 Open ports -I DONT KNOW WHERE TO START or Begin!
I'm going to try not to rant too much. My apologies if i do. I have XFINITY internet svcs, I have a Netgear Modem CM1000, and a NIGHTHAWK router R8000. I attend a local college, Univ. of Houston D...
> Okay Let me try to be a bit more precise. [...]
That didn't happen.
> [...] I completed the task to ssh into the box. [...]
I have no idea what that means to you. To me, "completed the task"
means success. With my weak psychic powers, I can't see what session
parameters you specified in PuTTY for this connection (other than the
apparent destination domain name).> [...] yes they did provide instructions [...]
That's swell, but no one provided them to _me_, so I can't see them
any better than I can see what you're doing.
From here, Telnet to "gator.uhd.edu" (216.145.162.35) returns
"Connection refused", which suggests that it's not listening on port 23.
Which is entirely reasonable. It does seem to be listening on port 22
(SSH), but I lack any valid credentials there, so all that I can do is
get to the "<user>'s password: " request. But I do get that far.> [...] I also tried to sftp into the box [...]
If you can't get a simple SSH connection, then I wouldn't expect more
from SFTP.> Figures 5 - 11 shows you the current setting on my router. [...]
As I said before, all those settings relate to incoming connections,
not to what you're trying to do (an outgoing connection).> > [...] Returned everything back [...]
> "everything"? Did you undo all those misguided setting changes
> involving DMZ and/or port forwarding/triggering? If you've lost track,
> then a full settings reset might be a reasonable step.> [...] My laptop ends with x.x.x.6. [...]
"15.72.90.6"??? That's a _public_ IP address (belonging to HP[E]).
You should not be using it (or anything like it) on your LAN.https://whois.arin.net/rest/net/NET-15-0-0-0-1/pft?s=15.72.90.6
Again, I'd suggest a settings reset on your router. And, this time,
when you're configuring it after that, leave the LAN subnet at its
default ("192.168.1.*"). And don't play with any settings which deal
with incoming connections.Curiosity compels me to ask how you decided that "15.72.90.*" was a
reasonable choice for your LAN subnet.
> Okay Let me try to be a bit more precise. [...]
That didn't happen.
> [...] I completed the task to ssh into the box. [...]
I have no idea what that means to you. To me, "completed the task"
means success. With my weak psychic powers, I can't see what session
parameters you specified in PuTTY for this connection (other than the
apparent destination domain name).
> [...] yes they did provide instructions [...]
That's swell, but no one provided them to _me_, so I can't see them
any better than I can see what you're doing.
From here, Telnet to "gator.uhd.edu" (216.145.162.35) returns
"Connection refused", which suggests that it's not listening on port 23.
Which is entirely reasonable. It does seem to be listening on port 22
(SSH), but I lack any valid credentials there, so all that I can do is
get to the "<user>'s password: " request. But I do get that far.
> [...] I also tried to sftp into the box [...]
If you can't get a simple SSH connection, then I wouldn't expect more
from SFTP.
> Figures 5 - 11 shows you the current setting on my router. [...]
As I said before, all those settings relate to incoming connections,
not to what you're trying to do (an outgoing connection).
> > [...] Returned everything back [...]
> "everything"? Did you undo all those misguided setting changes
> involving DMZ and/or port forwarding/triggering? If you've lost track,
> then a full settings reset might be a reasonable step.
> [...] My laptop ends with x.x.x.6. [...]
"15.72.90.6"??? That's a _public_ IP address (belonging to HP[E]).
You should not be using it (or anything like it) on your LAN.
https://whois.arin.net/rest/net/NET-15-0-0-0-1/pft?s=15.72.90.6
Again, I'd suggest a settings reset on your router. And, this time,
when you're configuring it after that, leave the LAN subnet at its
default ("192.168.1.*"). And don't play with any settings which deal
with incoming connections.
Curiosity compels me to ask how you decided that "15.72.90.*" was a
reasonable choice for your LAN subnet.
Something out of all that made sense.. I had all the incoming and nothing about outgoing. So i went to port trigger and added 22-23 in there.. Now VOILA, it works like a charm..
Thanks
I wish you wouldve just said that though.. Something tells me you already knew this was the problem..
Thanks
> I wish you wouldve just said that though.. [...]
If I had believed it, then I might have suggested it.
> [...] Something tells me you already knew this was the problem..
Wrong again.
> As I said before, all those settings relate to incoming connections,
> not to what you're trying to do (an outgoing connection).Still my claim. But, with practically no actual information on what
you were doing at any point in this ordeal, and no real hope of getting
any, I'm willing to move along.