D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: MrGST on June 01, 2010, 09:34:28 AM
-
Ok...2nd question:
I have a NAS device with a built-in web server on my home network which I can access from all machines on the private side at 192.168.0.119.
I want to be able to get to this web server from the internet so I have set a virtual server rule to direct port 80/HTTP traffic to 192.168.0.119.
I'm using dyndns to point to my dir-655 which responds to a ping request from the internet side.
As far as I can tell, the router is NOT directing http requests to the NAS.
What am I missing?
(http://www.tokuhara.net/misc/vserv.jpg)
-
http(s)://192.168.0.119 that it is.
http(s)://Yourname.dyndns.com
Setings in dlink : public and private 80, 443 at the same row.
Reserv that ip and (macfilter)
Try that
kthaddock
-
If I'm understanding your post correctly, I've done all that.
Is there another setting some place in the router that would prevent this from working?
-
Oh, not sure if it matters but the NAS gets it's ip via a DHCP reservation.
-
Oh, not sure if it matters but the NAS gets it's ip via a DHCP reservation.
Yep but you have to reserve to know you get same ip every time othervise your can't connect your NAS
-
Any other ideas why I can't access the web server from the internet?
-
Any other ideas why I can't access the web server from the internet?
Check your firewall that is an issue to get trouble.
Try to turn it off for testing. maby you need firewall rule to reach your NAS
-
Might try to put the NAS into the router's DMZ....
Does a NAS device have enough built-in intelligence to act as a server ? Such that it can, on its own, respond to requests from the internet ?
-
I tried the DMZ yesterday, didn't work.
Yes, the NAS has an apache server built-in. From the LAN side, it serves pages fine.
I'm wondering if there is something wrong with my router??? Otoh, remote admin to the router works fine, it just doesn't seem to want to forward requests to the the LAN side hosts.
-
Hi,
Well, as a temporary thing, turn off the router's firewall and test for access....
-
Well, as a temporary thing, turn off the router's firewall and test for access....
-GASP-
-
oops...guess I missed that other post.... my bad
-
I just tried the DMZ again, with both the NAS and a printer...can't access either of them. I did very briefly turn off the SPI firewall, no change. I'm starting to believe there is something wrong with the router. Either that or I'm missing a key point to make this work.
-
OP, just a minor thing, but you don't mention about saving your changes and rebooting the router with each change you test with.... I am sorta assuming you are doing that anyhow...but as you are seeking possible things you may have missed....thought I'd mention it...
-
Yes, I have been rebooting it after each change. :)
-
Hi,
Just another thought (tho I have so few each day I have to ration them), but can you, or rather should you set up a public server using port 80 ?
Your image shows private port 443 with the HTTPS item unchecked.... Maybe try some other random port to forward/redirect thru like 48990....
You image also shows only TCP is allowed....can you be sure that outside users wont hit you up using a UDP port as well ?
-
Right now I'm just trying to get it working. Once I can connect, I'll secure it. :-)
-
Could your ISP be filtering your attempts to get at your NAS server ?
I recall hearing that some ISPs do not allow private servers to be run unless the user has some level of service....
-
Possibly but I am able to remote admin the router. I'll check into it.
-
Here is a recent thread that might possibly help out...its not exactly what you are seeking, but it may be close enough to try something to resolve your situation:
http://forums.dlink.com/index.php?topic=13056.0 (http://forums.dlink.com/index.php?topic=13056.0)
-
Were you able to resolve this? I am having the same issue.
-
No, never solved it. One of these days I will try again but for now, it's a low priority.