Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mellowfish]

Up until about a week ago I was able to access my outside facing router admin page, two linux boxes via ssh connections, the web server running on one of those boxes and my windows pc's remote desktop all from outside my home network via the virtual server system on my router (such a great system, I love it).

Now, though, nothing (not even pings) get through from the outside, even though internet traffic originating inside and network traffic between computers on my network work fine.

*I* haven't done anything to it for about a month (since the last time I added a mac address to my network filter).

I am at a total loss for why this happened, and especially why it happened *now*

Important: My router's IP hasn't changed, I checked. I have also rebooted both my cable modem and my router several times and talked to my cable company. They haven't a clue.

Also, it may be incidental but the US Robotics NIC on my web server went belly up a couple days ago (a few days after my router stopped responding to outside stimulus).

[smlunatick]

Have you tried a different Ethernet cable and a different Ethernet port on router?  The description seems to indicated a "blown" port or bad cable.

[mellowfish]

I am curious what make you say this.

I can reach all the computers on my network and the outside world, so it would appear to me that all ports/cables are working in both directions.

If there is something I missed, it wouldn't surprise me.

[kthaddock]

http(s)://123.123.123.123:your port ==> if other then 80 and 443

http(s)://name.dyndns.org:port ==> if other then 80 and 443

or you have problem with double NAT, DHCP or UpnP

[mellowfish]

So, upon further investigation, I found that I *can* reach my router's admin page externally, I just have to *be* external. That was my bad for testing that while at home... I wasn't expecting the router to be smart enough to deny me access to the external port. Go D-Link!  

Any further thoughts on why external pings/port forwards are (still) failing before I reset to factory and hope for the best?

Thanks for all of our suggestions up to now.

[smlunatick]

Which ports?

Also, most DIR routers have a setting to turn off Ping response.

[mellowfish]

I have several virtual server style port forwarding rules set up which are all broken (haven't touched that setup for a month before they broke). The ports are things like 80, 443, 23, 22 etc for ssh and web serving, plus some arbitrary offset versions of these ports for connecting to a secondary server on my network and my PC's remote desktop port (just so it wasn't the standard one).

Also: I am an idiot on missing that ping setting. D:

[smlunatick]

I do believe that port 80 and 443 should not, or can not, be forwarded.  These are "resevered" for the router.

[mellowfish]

"The Virtual Server option allows you to define a single public port on your router for redirection to an internal LAN IP Address and Private LAN port if required. This feature is useful for hosting online services such as FTP or Web Servers."

Is this not the right place to forward port 80?

Also, mostly I care about why they broke *now* when I haven't touched those settings in a month.

[kthaddock]

I do believe that port 80 and 443 should not, or can not, be forwarded.  These are "resevered" for the router.

Offcause can they be forwarded. Just plan your port using