D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DGL-4500 => Topic started by: MrDoomMaster on June 11, 2008, 09:33:25 AM
-
Hi,
I setup Remote Management on my DGL-4500 Router and I cannot connect to it via my DNS. I enabled the HTTPS server, and also enabled remote management, and set my port to 1446. I then went to firefox and typed in:
https://my.domain.name:1446/
The web page hangs for a while and then eventually fails. Why isn't this working? My firmware is 1.03 beta.
-
I would appreciate a response on this matter. Thank you.
-
You're trying to loopback. You'll need to disable the SPI under advanced and firewall settings to loop back on the router.
-
i have the Same topic under the DIR 655.. Cant get to my remote admin part of the router..the disabling of the firewall didnt help for me?
DP ???
-
Also try changing the NAT ENDPOINT FILTERS to ENDPOINT INDEPENEDENT.
-
None of this is working.
Changing the firewall settings you mentioned shouldn't matter, since these requests aren't coming through the router to a client on the LAN. It's the router itself hosting the service, so the firewall shouldn't interfere IMHO. If it does, that seems broken. Can you issue a firmware fix for this ASAP? The system log on the router isn't even reporting any refused connections when I try to connect to my router remotely, this also seems broken & suspicious.
-
Hi,
I setup Remote Management on my DGL-4500 Router and I cannot connect to it via my DNS. I enabled the HTTPS server, and also enabled remote management, and set my port to 1446. I then went to firefox and typed in:
https://my.domain.name:1446/
The web page hangs for a while and then eventually fails. Why isn't this working? My firmware is 1.03 beta.
Can you connect via IP? https://WAN.IP.ADDRESS:1446/
-
Turns out, loop back for https was disabled. Don't ask me why, I'm still trying to figure out if it's intentional (I doubt it). I'll keep you guys posted.
-
When can we expect a fix for the loopback issue?
-
Like I said, we're not even sure if this is a actual mistake. In the past Dlink would block loop back on purpose.
So let me see first before I give dates on anything.
-
Like I said, we're not even sure if this is a actual mistake. In the past Dlink would block loop back on purpose.
So let me see first before I give dates on anything.
Okay, that's fine. But explain what you mean by loopback. What does this have to do with the remote management feature working? If loopback is required for the remote management feature to work, that seems like an obvious bug that it is disabled by default. Perhaps I'm missing something?
-
Loopback is when you try to hit the WAN interface from the LAN.
-
Loopback is when you try to hit the WAN interface from the LAN.
What does that have to do with the remote management feature working? When I access the router from *outside* the LAN, it still doesn't work...
-
Ok I misunderstood you then. What port are you using?
-
Ok I misunderstood you then. What port are you using?
The port I'm using is 1337. Why does it matter what port I choose?
-
I would appreciate a response.
-
Just looking to make sure the test is replicated accurately.
-
Just to let you know:
Remote Management has not been fixed in firmware v1.10. Not sure if it was supposed to be fixed or not, but I thought I'd mention it anyway.
-
Please review topic
http://forums.dlink.com/index.php?topic=2005.0
-
Please review topic
http://forums.dlink.com/index.php?topic=2005.0
I am running the botched v1.10 firmware and my remote management works. I do not use https I use http port 8080 and I filter the incoming IP addresses that are allowed to access the remote management functions.
I have other problems with this botched firmware, however not remote management at this time....
I really hope that v1.10 issues are fixed soon since this is holding up my productivity since I support my company from home and am having issues with my VoIP and other things. These things were never an issue using v1.02 . . .