Subject:
|
Re: New Web Site Launch
|
Newsgroups:
|
lugnet.off-topic.geek
|
Date:
|
Tue, 1 Jul 2003 14:10:06 GMT
|
Viewed:
|
412 times
|
| |
|
|
In lugnet.technic, Matthew Miller wrote:
> Your router is what is confusing you. It's probably not merely a router, but
> one of those fancy little internet gateway boxes from Linksys or Dlink or
> someone. Not only do they act as routers, but they also do something called
> Network Address Translation. Your ISP probably gives you only one IP
> address, which will be valid on the internet. Based on the header of your
> post, this is probably "24.217.75.125". However, your gateway box will
> probably let you have multiple computers attached. Each of these is assigned
> a non-public address in the 192.168.x.x range, and the gateway box takes
> care of translating these to your public address as requests come in and
> out. I can give more details on this if you're curious, but the important
> thing is: you need to use the gateway box's configuration interface to
> forward incoming port 80 requests to the local IP where your server lives --
> 192.168.1.102, in this case. Then, you set the DNS to point to your public
> address.
Also, if connectivity is provided by, for example, a cable company broadband or
phone DSL provider, there is a chance that the external IP (probably
"24.217.75.125") won't stay that way forever but will periodically (weekly?
Monthly?) change. You may want to check your terms of use to see if you are
allowed to do webservice, and if you are, you may want to look into a
redirection solution like www.dns2go.com (which I have heard about but not used
myself)
Hope that helps.
|
|
1 Message in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
