To get anything more than guesses, you'll have to tell us what "won't work"
and "can't/won't use port 80" mean. Details like whether you are accessing
from the external interface or the internal one, and whether you are talking
about port forwarding to an internal server or running the weblet (or some
other httpd server) on the router itself.

As for the guesses ... some ISPs block incoming traffic to port 80 (to
enforce "no server" policies for home accounts, or for security reasons ...
or maybe just to keep the traffic up on troubleshooting lists), requiring
off-LAN Web servers to use a non-standard port. 

At 02:12 AM 3/11/02 +0800, Vic Berdin wrote:
>Hello everyone,
>
>I can't figure out why httpd won't work on it's native port 80. I've
>managed to make it work on port 81 and on any other available port as
>long as it's not 80.
>I find it a bit odd to to include the port number along with the address
>when accessing web pages on my DS box. And I also do not wish to change
>my browser's default port settings juts to make this work.
>
>Upon viewing the /etc/services file, it clearly indicates that port 80
>is indeed accounted for WWW http:
>www            80/tcp            http            #World Wide Web HTTP
>www            80/udp                             #Hypertext transfer
>protocol
>
>I just can't figure out why httpd can't/won't use port 80. Any hints to
>those who may have encountered the same problem is greately appreciated.



--
------------------------------------"Never tell me the odds!"---
Ray Olszewski                                        -- Han Solo
Palo Alto, CA                                    [EMAIL PROTECTED]        
----------------------------------------------------------------


_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user

Reply via email to