Forum Home
Press F1
 
Thread ID: 37894 2003-09-21 09:35:00 Setting a virtual server on a Dynalink ADSL Router andrew_mercer (3328) Press F1
Post ID Timestamp Content User
176819 2003-09-21 09:35:00 I have Apache installed on my Linux box, and am experimenting with a dynamic IP service (www.dynu.com) so that I can use my Linux box as a webserver on my ASDL account.

I've set the up the virtual server on the router so that any coming through on Port 80 (and 8080) gets forwarded straight thru to my Linux box (and my apache webserver). However, PCs connecting to my address (www.colibri.dynu.com) still get the router's configuration pages.

Are there other settings that I need to be aware of, or is there some further step required to enable the virtual server? Any info greatly appreciated.

Cheers
andrew_mercer (3328)
176820 2003-09-21 09:56:00 Have you got the firewall on, maybe open up some ports on that?

Have you got the Virtual Server set to to forward anything on the same port of external packet to the same port on internal packet? Maybe give us a screenshot of how you've got it set up:

sal.neoburn.net

I would think its more liekly to be something configured wrong in the linux box.
kiki (762)
176821 2003-09-21 10:34:00 > I've set the up the virtual server on the router so
> that any coming through on Port 80 (and 8080) gets
> forwarded straight thru to my Linux box (and my
> apache webserver). However, PCs connecting to my
> address (www.colibri.dynu.com) still get the router's
> configuration pages.

It sound like you forgot to change a setting on the router

What typed of router do you have???

Also give us a screen shot of your router configuration pages as well.
stu140103 (137)
176822 2003-09-22 00:45:00 Andrew,

I assume Apache is using port 80 for webserving. Does that computer have a static IP for the network card?

In your dynalink router config page, set up virtual server to use your apache server's network IP, and port 80, and that should be it.

You can't connect to colinbri.dynu.com from computers within that network or else the router config login will show, you have to connect IPAddress people not within the network, should be able to connect using colinbri.dynu.com
Kame (312)
176823 2003-09-22 12:34:00 Thanks for your comments.

The virtual server is set as per the Dynalink recommendations
dynalink.co.nz
Seems like it SHOULD work, but doesnt.

I have also tried accessing the site from my work (i.e. outside of my own network) but without success.

Will just keep trying and experimenting, I guess. Could be a combination of factors instead of just one.
andrew_mercer (3328)
176824 2003-09-22 12:35:00 PS: The webserver itself is running fine. I can access the site within my own local network by pointing at the IP. andrew_mercer (3328)
176825 2003-09-23 00:45:00 OT: I have just tried( at 11:44 am) www.colibri.dynu.com & I get this error message:

Forbidden
You were denied access because:
Access denied by access control list.

????? ?:|?:|
stu140103 (137)
176826 2003-09-23 00:51:00 > PS: The webserver itself is running fine. I can
> access the site within my own local network by
> pointing at the IP.

Have you tried accessing the server from the outside via its internet IP address e.g. 210.55.230.XX Not throw www.colibri.dynu.com ?????

If you do not know what your server Internet IP address is try this site & it will tell you http://www.whatismyip.com/

Also who is your ISP???? I hope it is not XTRA :D???
stu140103 (137)
176827 2003-09-23 00:56:00 > Have you tried accessing the server from the outside
> via its internet IP address e.g. 210.55.230.XX Not
> throw www.colibri.dynu.com ?????

I have just ping www.colibri.dynu.com & I got this IP address: 203.98.50.XX

Is this your Internet IP address????

Note: dynu.com IP address is: 198.144.7.XXX
stu140103 (137)
176828 2003-09-23 02:04:00 Andrew check your .htaccess file in your web documents root. It's probably not set up correctly and isn't allowing access.

Also have a look for your HOSTS file and check those settings are correct.

Have a look in your httpd.conf file and check there as well.

The problem seems to be Apache isn't set up correctly with permissions.
Kame (312)
1 2