[BlackKnight]

@khx73 I had to do DMZ and the port forward in order to connect to any program that used said ports. Not sure why, but it wouldn't work unless I did otherwise. I think the router or the firmware is bugged when it comes to port forwarding.

And yes, I know that being to connect to my own external IP needs to have to support on the modem in order to do so. I'm just a little annoyed that this is the first modem I've had in a very, very long time that wouldn't allow it. It's really no biggie in the end, if it all works fine. (my 2Wire had it, and even when I was on DSL prior to FiberOP being released, can't recall the name of the modem, but it was a good one)

As for the testing the ports on this router. It will now say "open" port almost every time I check. Whereas, before trying to connect to it from an outside source, it would say "closed". I have a feeling after I shut down and restart the PC it will say closed again haha... Bizarre behavior going on...

 

[khx73]

Weird! I think I'll try some with my own R3000 just to see if I can reproduce it.
It's just been set to advanced dmz since install...

 

[BlackKnight]

Good luck.
Now they're back to saying 'closed', and I can't get them to say 'open'... It's like a cruel joke, but access still works...
Advanced DMZ shuts down my whole internet connection for some reason.

 

[khx73]

What method are you using to test those ports and what's telling you "open" or "closed"?

btw, did some quick reading on that fullcone NAT option.. pretty sure that's not something you'd want on.

 

[BlackKnight]

I'm using just a couple web domains that probe for open or closed ports. One is from yougetsignal.com , whatismyip.com and then the other is from the Shield's Up general probe test. I'll try testing it with fullcone off tomorrow.

 

[Arinoth]

I am using GRC.com to see if the ports are open, but I've tried a few applications that have tested it themselves and they report ports blocked too. Honestly feel like giving up since it shouldn't be THIS complicated for ports to be forwarded properly, either with their modem/router or a commercial one.

 

[khx73]

Yeah I don't blame you for wanting to give up. It *shouldn't* be that complicated at all, I agree. It's just hard for me to imagine why it's being like that for either of you. Forwarding and DMZ has always worked for me, so I naturally figure it should work for anyone on the same service...and when it doesn't, I'm inclined to want to help, and figure out why.
However, it's frustrating sometimes over text-based forums..there are a lot of details that get lost or omitted based on assumptions of the other person's configurations, experience, etc.

 

[Arinoth]

That's why I picked up the Asus router, put it on VLAN35 and tried just port forwarding using it with the same lack of results, leaving me to believe it's not the actiontec router but something else..

 

[khx73]

So, please don't be offended when I ask... but just have to cover the simple stuff... when you actually test for successful forwarding, the service that you are trying to forward TO is *actually* running, right? For example.. trying to forward a port for a mumble server, the mumble server actually has to be running, or the "test" will still say port is closed even though it's forwarded correctly.
Silly I know..but believe me.. people can be mislead.

 

[Arinoth]

Yes, the service says it can't connect via the port I am forwarding and GRC.com agrees the port is blocked too.

 

[doscott]

When you say the service indicates it can't connect to the port, this is the service you are remotely connecting to? Because the ability of a service to connect to a port has nothing to do with port forwarding; it sounds like you have a firewall blocking this port on the computer the service is running on.

Forgive me if I interpreted that statement incorrectly.

 

[Arinoth]

Some applications/services will let you check to see if it is connectable via a certain port, which all report that they cannot. And I have tried with the windows firewall disabled, as well as enabled and forwarding the correct ports too.

 

[habskilla]

Who else wants to go on a road trip to Halifax?

 

[khx73]

Hopefully these services/applications aren't just trying to reach themselves with your own public IP.. that will surely fail due to lack of NAT loopback support. Testing from GRC should work though..as long as the service is actually running.

You said it's a murmur server you're trying to get going , right? I'm going to try it when I get home this evening on my windows 10 machine...and forward the port..then test with grc etc like you have been... I'll get back to you.

 

[Arinoth]

Murmur is just one example, there's other applications, some of which are ones I've programmed for some projects of mine that also fail to connect through a port.

 

[khx73]

Ok fair enough. Anyway, I tried it.. and as expected it works fine.. grc reports "Open" status. If I shut down the service, grc reports "Closed". If I leave it firewalled, it reports "Stealth".
Were yours showing up as closed or stealth?

 

[Arinoth]

Nope, never could get that far, Mumur would kick back this error
<W>2015-10-20 20:34:27.930 1 => Server: TCP Listen on MYIP:64738 failed: The address is not available
<W>2015-10-20 20:34:27.937 1 => Stopped

IF I leave the host IP blank then Murmur says it can launch, grc.com shows it as open but if I try to connect to it using my external IP address the server always times out and cannot connect

 

[khx73]

Ok, but remember you can't connect to your own server using your own public IP address. That is why GRC says it's open - because the grc probe comes from out in the public internet. Anyone outside your own home LAN should be able to connect. If you are home in your own LAN, you can't connect out-and-back-in to your own public ip. Know what I mean? You yourself would have to use the private IP of the pc hosting instead.

 

[Arinoth]

I tried connecting it to it with it's local internal IP address and it reports the same timeout which is why I've been lead to believe the port is blocked.

 

[khx73]

Yet grc probe on that port still reports Open?