Like we need a new thread on HTTP port 80

I am in the situation that my ftp is working but http is not working. All works inside my network but non-local computers can only get my ftp and not http. I am running a linksys router and have port 80 open and directed to the static ip address on my LAN in the server. (OS Windows 2000 server) I am using both TCP and UDP on port 80.

Racked my brain and looking for someone's input.

Thank you kindly

ok bro make sure that the ftp is set to anything above 1025 but by defalt it should be port 21 if they are both 80 you will have a conflict. now by defalt port 80 is http and both 21 and 80 are open. now if you want to use say 1075 then you must open this is the router with lynksys type in 192.168.1.1 in internet explorer and log in by defalt it is user name admin password admin then click advanced/fowarding then in there under exp port make first box 1075 and second say 1090 then check tcp and add your routers ip for that machine then check enable then goto bottom and click apply now those ports are open and you can use them for ftp sites



kwick

I don't know where port 1075 came from, but my best guess is you either a) didn't forward port 80 properly, or b) you have some other firewall in the way, or c) your isp blocks port 80 to keep you from running a web server.

Doug,
I have not heard that kind of advice (port 1075) as though there would be a port conflict but I did it anyway. I won't be using anonymous access to ftp. Port 80 forwarding: a) I use the linksys befsr41 dsl router and it has HTTP port 80 enabled for my static IP on my LAN. I am using just TCP as a protocol. Do you think I should use both TCP and UDP? b) The router might have an internal firewall that I dont know how to turn off. Would that jeapordize my security? I called my ISP (Verizon) and they said that they dont block any ports.
Thank you

I have a number of befsr41's here and Verizon DSL. I've never had any problems with port forwarding, I've always clicked both TCP and UDP but I don't think UDP is needed.

You can sometimes use telnet to track down problems, telnet to port 80 and see what the response from your HTTP server looks like.

[QUOTE=Doug G]I have a number of befsr41's here and Verizon DSL. I've never had any problems with port forwarding, I've always clicked both TCP and UDP but I don't think UDP is needed.

You can sometimes use telnet to track down problems, telnet to port 80 and see what the response from your HTTP server looks like.[/QUOTE

Doug, Do you have static IPs from Verizon or you purchased them from another company or do you use a DNS service like no-ip, DynD, or TZO?

I have fixed ip's. But as long as your dynamic DNS service gets visitors to the current IP address, I don't think there is anything in your router or network that would act differently.

Doesn't dynamic dns require a program to run on your computer? Maybe that program needs to listen on some other port to work right?

If outside users can reach your ftp server OK but not your http server, and your router port forwarding is set up properly, it should work for you!