Recently, I've been having an issue with all my devices, and my R6080 router. A few days ago, I tried to enable a Port Foward. When I found out the packets were still being dropped, I tried to enable a DMZ on the device. No effect. I've came to the conclusion that either my ISP is dropping the packets, or the settings aren't taking effect. Any feedback would be useful.
Hi, Currently, as far as I know, it's on all my devices. I'm using the generic Windows packet tool with some generic port scanners. It's connected to an Arris modem, and it's over wireless and wired. I can't connect directly to my modem.
> Recently, I've been having an issue with all my devices, [...]
"an issue"? Care to elaborate?
> [...] I tried to enable a Port Foward. [...]
That could mean almost anything. What did you actually do? Why? Is there some actual problem which you are trying to solve?
> [...] When I found out the packets were still being dropped, [...]
How, exactly, did you find out what, exactly?
> [...] I tried to enable a DMZ on the device. No effect. [...]
"tried"? How, exactly? Doing port forwarding and using a DMZ server do not go well together.
None of that is a useful problem description. It does not say what you did. It does not say what happened when you did it. As usual, showing actual actions (commands) with their actual results (error messages, LED indicators, ...) can be more helpful than vague descriptions or interpretations.
> [...] I've came to the conclusion [...]
You don't seem to know enough about this stuff to make your analysis of the problem worth anything. What _might_ be helpful would be if you described accurately what you're doing, and what happens when you do it. What you think it all means is much less interesting.
> [...] or the settings aren't taking effect.
With my weak psychic powers, I can't see any of your "the settings". What "effect" were you expecting to detect how?
The issue was with port fowarding/using a DMZ. I was using the 192.168.1.1 interface and inputted all the values needed. The problem I'm experiencing is, either the settings are having no effect, (no error logs indicate errors), or my packets are being dropped before they reach my computer. As mentioned before, I used various tools to come to the conclusion. I used the DMZ and port foward seperately, and they still had no effect on the packets. The effect I was expecting is for the packets in question to not be dropped. It's a Modem + Router combo.
> The issue was with port fowarding/using a DMZ. [...]
Does that "was" mean that you've solved the problem?
> [...] I was using the 192.168.1.1 interface and inputted all the > values needed. [...]
What, exactly, were all those "all the values needed"? It's nice that you're happy with what you did, but that non-description conveys exactly no useful information to the non-psychics in your audience.
> You don't seem to know enough about this stuff to make your analysis > of the problem worth anything. [...]
The same holds true for your judgement of what "all the values needed" might be. You might be right, or you might be wrong, but if you keep everything secret, then we might never learn which.
> [...] As mentioned before, I used various tools to come to the > conclusion. [...]
Swell. So, if I wanted to replicate your problem here, that tells me to do what, exactly? Also, as stated above, I'm much less interested in your conclusion than I am in the actual evidence which led you to it.
> [...] I used the DMZ and port foward seperately, and they still had no > effect on the packets. [...]
Swell. So, if I wanted to replicate your problem here, that tells me to do what, exactly? Also, you can't see "the packets". I don't know what you actually can see, but I doubt that it's packets. Which part of "actual" was unclear to you?
> [...] It's a Modem + Router combo.
> Cascading multiple routers has implications for port forwarding.
Still true.
With my weak psychic powers, I can't see any IP address(es) of any of your devices, or your port-forwarding rules, or how you tested anything, or what happened when you did whatever you did.
Did you read any of that, or answer the questions, or perform the tests? Or am I talking to a wall, here?
If your (unspecified) "an Arris modem" is actually "a Modem + Router combo", and its router section is active, the you'd need to do any port forwarding on it, not on a separate R6080 router.
In such a case, most likely, you'd also want to configure the R6080 as a wireless access point, rather than as a full-function router.
Visit http://netgear.com/support , put in your model number, and look for Documentation. Get the User Manual (at least). Read. Look for "Use the Router as a WiFi Access Point Only".
> [...] Is there some actual problem which you are trying to solve?
You might also want to consider answering some of the many still-pending questions.
As far as I know, the values are the internal IP of the host, the TCP or UDP service, the external and internal port range, and service name. For tools, as stated above, I used the Command Prompt (ping + telnet) to execute commands to determine the status of a port. I used port fowarding, not triggering. Also, my modem is out-of-date. I can't access a web interface for it, as far as I know. It's an Arris TM822.
> As far as I know, the values are the internal IP of the host, the TCP > or UDP service, the external and internal port range, and service name. > [...]
Strangely, I still can't see any of the actual values which you might have specified for anything. "the host"? Are you running some kind of server on your (unspecified) "the host", or what?
> [...] I used the Command Prompt (ping + telnet) to execute commands to > determine the status of a port. [...]
Which part of "actual actions (commands) with their actual results" did you find confusing? Copy+paste is your friend.
> [...] It's an Arris TM822.
Whew. That's a modem, not a modem+router. Should be harmless.
> [...] I can't access a web interface for it, as far as I know. [...]
Have you tried "http://192.168.100.1/"? But with a simple modem, I doubt that it matters.
The problem I'm trying to solve is for the packets to arrive at my computer. I have a Netgear R6080 + Arris TM822. When I try to connect to google.com for example, the connection is unable to open. When I use telnet, this shows up. (I used port 1578 as a random port, for this test.) Connecting To www.google.com...Could not open connection to the host, on port 1578: Connect failed. This is the problem.
P.S.: I'm not a computer expert, so some of the imformation is difficult to interpret. Please bare with me.
> The problem I'm trying to solve is for the packets to arrive at my > computer. [...]
That's meaningless. _Which_ "the packets"?
> [...] When I try to connect to google.com for example, the connection > is unable to open. [...]
Are you trying to say that using some web browser or other, running on some computer/device or other, a (partial) URL like "google.com" gives you some error or other?
See "As usual, [...]" above.
> [...] When I use telnet, this shows up. [...]
"this"? "When [you] use telnet" _how_, _what_ "shows up"?
See "As usual, [...]" above.
> [...] Connecting To www.google.com...Could not open connection to the > host, on port 1578: Connect failed. [...]
I have no idea what that means.
> [...] This is the problem.
I don't know what "This" is.
> P.S.: I'm not a computer expert, [...]
I'd already guessed that.
The less you know, the more important accurate, detailed, precise descriptions become. What you see, what you did, and what happened when you did it, are what matter. Non-descriptions like "unable" (or anything involving "packets") often convey little or no useful information. (In this case, "no".)
After not getting a straight answer to the most basic questions, repeatedly, I'm worn out. Perhaps someone else has more time to waste this way than I.
