Help with personal Web Server

[milky]

I want to host my own web site, just for the hell of it, so I installed Abyss Web Server X1 2.0.6.
I used Macromedia Flash 8 to create a simple flash page (.swf)
I got a free domain name from dyndns.org (milkytech.homeftp.net)
I think I configured the server properly as far as ports, and directory locations.

I cannot log on to the website from a computer outside my LAN, but works fine with computers within LAN

Windows Firewall is configured correctly (port 80 is open by default anyway)
I even tried configuring the server to use port 1024 internally and port 80 externally...same thing...works locally, but not remotely.
I've opened the ports on my router as well.
Seems to me that if it works within my LAN it should work from outside it as well since my domain name in resolved to my public ip address.

Remote Desktop works fine using that same domain name both with RDP Client and TSWeb. I have no problem accessing my ftp server (running on the same pc) with that domain name [However: I cannot seem to access my ftp server through a web browser, only with ftp client software (LeapFTP)]

What am I doing wrong? I don't know too much about websites, just some basic html. Does the homepage have to be an index.html or index.htm file?
the only file I have in the root folder is "Untitled-2.swf" (Flash).

I know that file itself is good because if I go to another computer on my LAN and open internet explorer and type http://milkytech.homeftp.net it works!

 

[Nodsu]

Did you forward the correct port to the right computer on the router? Your ISP may be blocking port 80 - try using something >1024.

 

[milky]

I once had a friend tell me that my ISP [Optimum Online (Cablevision)] does in fact block port 80, but when I mentioned that to my Network+ instructor, he laughed and said that if port 80 was blocked I wouldn't be able to use the internet and that ISPs do not block port 80.

Anyway, like I said previously, I tried setting the server's public port to 80 (isn't that a must for people outside my LAN to be able to see the website without specifying a port?) and the private port to 1024. still the same thing...works locally only. I will now try setting both public and private ports to 1024 but I have a feeling that I will have to specify the port in the web address (ie- http://milkytech.homeftp.net:1024)

 

[Mictlantecuhtli]

I will now try setting both public and private ports to 1024 but I have a feeling that I will have to specify the port in the web address (ie- http://milkytech.homeftp.net:1024)

Is that too annoying then?

Port 8080 is the alternative http port, by the way. Maybe that isn't blocked?

when I mentioned that to my Network+ instructor, he laughed and said that if port 80 was blocked I wouldn't be able to use the internet and that ISPs do not block port 80.

There's a difference between incoming and outgoing traffic. Does your instructor know it?

 

[milky]

Yes, that is way too annoying. I just tried it and it does work remotely on port 1024 as long as the port is specified.

Now I will try 8080. hopefully It works without specifying the port.

 

[Mictlantecuhtli]

It won't

 

[Samstoned]

you must diffently add the :8080 or what ever extension for others outside your lan to see your server
my old address was

www.m7l.com:8080/

when I ran my own apache web server

 

[milky]

well that didn't do me much good. 8080 doesn't work even if I specify. I guess my ISP blocks that one also.
So I guess my question now is: Why is 8080 considered an alternate web port if it is really no different than the thousands of other alternate ports?

 

[gary_hendricks]

Hi milky,

Hey I've always wanted to do the same thing. I've tried setting up my own web server to no success. You see, I've been subscribing to a online cable service and it does not allow me to set up an FTP server that I can access from the office.

Here's an interesting article that inspired me to set up my own web server.

http://philip.greenspun.com/panda/server.html?

You guys should check it out!

 

[Nodsu]

1080, 3128, 8080 are so-called "well known ports" used by proxy software.

You could set up your web server as secure (HTTPS) and have people access it using https:// links. That is if your ISP allows connections to port 443.

 

[milky]

now that you bring that up, I have a few questions about the HTTPS protocol:

To use https, the only thing I need to do is set my server up on port 443 (if my isp doesn't block it)??
What makes https secure? Is the transmission encrypted?
If so, which device is performing the encryption/decryption?
How does the device know to encrypt/decrypt a transmission? Simply because it is using port 443?