Print

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

[lordstyx]

Hello everyone,

Yesterday I've bought myself a D-Link router for the first time. It's a DIR-825 as you may have guessed   and all connections seem fine, however there is one thing. I have a webserver running here in my LAN, and I was wondering why I couldn't access it using our external IP (or domains pointig to it). Now, anyone outside my LAN (and thus having a different external IP address) CAN acces the website, which I found out by accident.

Does anyone know if this is related to any settings? And if yes, any solutions?

Thanks, lordstyx.

[vbobmac]

this is call a Loopback Connections error ....
look at this
http://forums.dlink.com/index.php?topic=14057.0

hope this will help....


Vbob

[lordstyx]

Hah I saw that thread and I was already wondering if it was the same problem.
Will people from outside the LAN still be able to connect like they can currently?
And since you can't enter port ranges at the Virtual Server page, is that list extendable? Because I have the server side of a server/client app running on the same machine, and it uses quite a few ports.

[vbobmac]

My english is limited. can someone from D-LINK help? can this be fix in futur firmware? or it's a dir-825 limitation?

??


Vbob

[lordstyx]

Hah I saw that thread and I was already wondering if it was the same problem.
Will people from outside the LAN still be able to connect like they can currently?
And since you can't enter port ranges at the Virtual Server page, is that list extendable? Because I have the server side of a server/client app running on the same machine, and it uses quite a few ports.

Can anyone answer me this?

[vbobmac]

YYYYYYYYYYYYYOOOOOOOOOOOOOOOOOOOOOOOO
WAT DO WE HAVE TO DO TO GET ANSWER......Y FAUS-TU CRIER?

Bon ... Now that i have your attention.... can someone answer those few questions? is there any D-Link tech here?


Vbob

[raytrace]

Hah I saw that thread and I was already wondering if it was the same problem.
Will people from outside the LAN still be able to connect like they can currently?
And since you can't enter port ranges at the Virtual Server page, is that list extendable? Because I have the server side of a server/client app running on the same machine, and it uses quite a few ports.

I'm not a D-Link employee but I can answer your questions for you.

First a question.  You mention using several ports but I'm assuming that you aren't requiring port redirection.  The virtual server is used to allow incoming ports to be redirected to both an IP address and a different port. 

Say you have a website called "http://mywebsite.com" but in order for your customers to access the site through your router they have to type "http://mywebsite.com:8888".  Your router recieves the incoming request at port 8888 and then it forwards the packets to your web server at port 80.

If you are requiring a lot of port redirects, then that is something more along the line of a commercial grade router.

Now, what I suspect is that you need port forwarding in which incoming ports get redirected to the same ports but to a certain IP address.  With port forwarding you can assign groups.  If that's what you need, then make sure that you assign a DHCP reservation to the server.

[lordstyx]

That's entirely off the question 
Port forwarding works fine, as long as people are outside my LAN. When I try to go to "http://mydomainpointingtomyIP.com:8888", or even "http://myIP:8888", the page doesn't load, I have to type the LAN IP address instead. Now this makes it way more difficult to check my own sites for bugs. What I was asking, is that if I use Virtual Server, will the same thing occur? Or will both people from inside as outside my LAN be able to use "http://mydomainpointingtomyIP.com:8888" to view the website?

Not only is the current situation difficult for checking the website(s) for bugs, I have to make myself a custom client, which uses the LAN IP of my server to connect to it.