Results 11 to 15 of 15
You could try without the router perhaps? I am not having such issues. Permissions on your web pages are ok?...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 03-30-2006 #11
I am not having such issues.
Permissions on your web pages are ok?"To express yourself in freedom, you must die to everything of yesterday. From the 'old', you derive security; from the 'new', you gain the flow."
- 04-05-2006 #12
Have you configured port forwarding for port 80 on your router? On your router status page it might be called "Virtual Servers" or something similar. What happens if you visit your router's IP from the Internet, instead of the DynDNS name? Your router status page will tell your your external IP address.
- 04-06-2006 #13
Ye, it was an issue with port forwarding. I thought I did it right the first time, but apparently my settings didn't stick. I am up and running!"If you are out to describe the truth leave elegance to the tailor."
- 10-17-2006 #14
Originally Posted by ThoughtVelocity
- Join Date
- Oct 2006
Could you please explain exactly what have you done for solve this issue ?
I get same message (401 the web site is blocked.....) when I try connect remotely to my Dlink. *.dyndns.com:8080
Thank you in advance.
- 10-18-2006 #15
If you're trying to connect to yourname.dyndns.com:8080 in a browser, you need to do either of these 2 things:
1. Set up your Apache server to listen on port 8080, and configure your router to forward port 8080 to the IP address of your Linux computer
2. Set up your router to forward port 8080 to port 80 on your Linux computer, as this is what Apache will listen on by default. Some routers do not allow port forwarding in this manner.
If you log into your routers admin interface you should find these options under 'firewall rules' or 'virtual servers', or maybe even 'port forwarding'. I own a netgear rather than a dlink router but they are all pretty similar.
You might find this link helpful: http://www.portforward.com/routers.htm