Actually, you don't need a static IP to run a webserver, but it does help. You can use a dynamic DNS service that will update your IP if it changes, so your domain will (almost) always resolve to your public IP.
FYI: 192.168. is a non-routable network address, not an IP address. 192.168.0.1 is an IP address :)
I think he's talking about getting a static internal IP, instead of being assigned one via DHCP. In this case, it is very preferable to be static ;-). Also 192.168. is his abbreviation for a 192.168.x.x IP, so don't pick on him :confused: .
Tekmaven
Software Architect
1,274 posts since Feb 2002
Reputation Points: 322
Solved Threads: 28
Could someone help me with the same problem as the original poster? I'm trying to reach my site (hosted on my home machine) from work. The firewall at work blocks all ports except 80. So I have to go out port 80 at work, but I know that OptOnline blocks 80. So I set up a WebHop with DynDns that redirects to a port on my home machine. I tried a variety of different ports figuring OptOnline blocks some of them, but nothing seems to work. Any help would be greatly appreciated.
a little more info would be helpful, in particular, the internal (from "modem") network layout, and your protocol config; along w/anything else that you believe would be pertinent
aeinstein
Team Member - aka kaynine
645 posts since May 2002
Reputation Points: 186
Solved Threads: 8
i'm a network guy so that's what i was looking for to help resolve, but since u dont have one... ...btw, do u have an "index.htm" or "home.htm" page for the site in the "Cabinet" directory?
...it redirects to http://69.115.43.20:5906/Cabinet/ on my machine...
aeinstein
Team Member - aka kaynine
645 posts since May 2002
Reputation Points: 186
Solved Threads: 8