Can't access router's "Remote Management" page from inside network. . .?

[gberz3]

Quote:

Originally Posted by Keymaker

Did you try a dns name resolution.

Define "dns name resolution". Do you mean using something like DYNDNS? If so, then yes, I have used it, but the router still knows that the requesting traffic initiated from inside itself.

If that's not what you mean, pleas elaborate. Thanks.

[Keymaker]

No, that's what I mean. Figured it wouldn't work, but heck worth a shot. As you already have found out.

Name resolution to you IP address....


Defined:

Quote:

Conventional name resolution transforms a DNS name into an IP address.

The TCP/IP Guide - DNS Basic Name Resolution Techniques: Iterative and Recursive Resolution



I have no other tricks that I'm aware of...yet..

[Keymaker]

Have you tried an entry in the host file?

192.168.1.1 (Router IP) : DNS name of external IP address.

[gberz3]

Quote:

Originally Posted by Keymaker

Have you tried an entry in the host file?

192.168.1.1 (Router IP) : DNS name of external IP address.

On the SOURCE machine or the DESTINATION machine? I'm not sure that would work toward accomplishing what I'm trying to accomplish.

[Keymaker]

It might from the PC accessing the remote interface to the router.

[gberz3]

Quote:

Originally Posted by Keymaker

It might from the PC accessing the remote interface to the router.

I see what you're saying, but that's not the issue. The PC is finding "home" just fine. The issue appears to be that the traffic is simply getting blocked because of some type of "encapsulation/tagging", and the router is aware that the traffic initiated inside itself (for lack of a more appropriate phrase) and disallows reentry.

[Mickwish]

I will again try to explain what I understand of this. The router apparently uses a NAT firewall that doesn't allow the external WAN IP to be used internally. Unless you can change this firewall rule you will never be able to access any internal server via WAN IP from within the LAN.

If you really want to access the internal server via WAN IP form within the LAN, you will need a new router, or new firmware which allows you to change the firewall rule on that router.

No amount of other stuff will help, I'm afraid.

Cheers
Mick

Oh, how I miss DNT1!

[gberz3]

It seems that this is becoming the case more and more as of late. I've worked with several different brands of routers (even some combo DSL/Cable routers) and more and more they seem to be blocking access. Has anyone found any articles/info regarding this trend and why it is becoming the norm? It's a very frustrating issue.

Oddly enough I can use my old DLink-624 and all is well. Only problem is its 802.11g (while my devices are 'Draft-N'...so I lose internal speed). Also, it is old and I believe it is failing...seems to want to restart randomly.

Anyway, if anyone has anymore info on the who/what/when/why of this situation, it would be most appreciated.

[Nude_Lewd_Man]

This is most likely due to the NAT rule/s. When you try to access (for example) 123.45.67.89 your machine knows that it isn't within the LAN, so it will go to your router, the router will (basically, and with my examples) know that it is itself, so will try to send it to the WAN inface.

If there are no rules that tell the router what to do with this, it will see it as an inbound (WAN --> LAN) packet and the default action for this would be for it to be dropped.

This is the same as if you have RemoteDesktop set up. Internally you would use (again, for example - I'll also demonstrate with a custom RD port) 192.168.1.2:1001 and the computer would respond to allow you to connect, presuming that it has been set up correctly in the registry and the firewall etc...
If you tried to connect using the 123.45.67.89:1001 port internally it wouldn't work, and the same is true if you tried using the 192.168.1.2:1001 externally...

However, if you tried the 123.45.67.89:1001 externally it would again be passed to the router at that location, which would send the traffic over the internet to your router, and as long as all the required settings are configured (and the machine is ready to accept the packets) it would allow you to establish the connection.....

[zeroluck]

The answer is "NAT loopback". The threndnet router doesn't support NAT loopback therefore you can't access the remote management from the inside using the external ip address.

Loop it in google. A lot of routers lack this feature:

Netgear
Linksys
Belkin
TrendNet

Almost anything in the SOHO level lack this feature.