Re: Wanting to place my hosted web on my server

In news:FD7BC45F-BD5D-4742-8C2A-924FD4374C82@xxxxxxxxxxxxx,
Mark <Mark@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post, which I then commented
about below:
> http://192.168.x.xx:80 does not work from outside or inside the
> server. ftp://192.168.x.xx:80 does not work from outside (from my
> pc)or in the server.(when logged in)
>
> ****Do I need the anonymopus box unchecked in all placesunder web. on
> IIS or leave the default username ans PW in. I didn't think I needed
> any forwarding stuff done.
>
> I guess I am doing something wrong or do not have it set up right
> yet. I hate to give up, I feel I'm so close. I'm sure I am confusing
> you,. Remember. One server. I connect remote. Or My son is on that
> network where the server is . One pc connected on the same workgroup.
> I log in via MSTSC and a 63.xx number.
>
> I think I read that I needed the :80.
> "Mark" wrote:

What is the exact error you get in the webpage when you connect by
http://192.168.x.xx:80 ?

Port 80 is the default port for web services, meaning it automatically uses
that for 80 when you type in a URL, unless you want to use a different port
to keep it private, but the web site properties must match the port used in
the browser.

Keep the anonymous box checked, unless you want to keep it private and must
log in to the site everytime you visit it. Leave the password for the
anonymous account alone for now.

As far as FTP, the default FTP port is 21, not 80. Since you stipulated 80
for FTP, then the FTP service default port 21 will need to be changed to 80,
but that will conflict with the HTTP service listening for requests for the
website on port 80, and it will tell you so warning you not to do it when
you attempt to set it. If you say yes, the service will not start because of
the conflict. Each service needs a unique port number to identify itself.
Does that make sense?

Another method for unique website identification is the hostheader. That is
the name you type in for the URL. It can be configured in the website
properties, general tab, click on the Advanced button next to the IP address
dropdown box. You can type in the name, such as www.domain.com, domain.com,
and/or the IP address. If it's the only website machine, it will use the IP
set on the machine, and the default port, but no hostheader. Hostheaders are
a great method to host multiple websites with one IP address on the machine,
and using only the default HTTP port. It identifies each website on the
machine by it's hostheader. All webhosting companies do it this way, unless
you want SSL, on the website, which requires a certificate and a unique IP,
in addition to the hostheader.

Here's a little about hostheaders:
IIS TIPS - Host Header - What is it:
http://msmvps.com/bernard/archive/2004/07/29/10855.aspx

IIS Answers - How to create multiple websites with one IP address:
http://www.iisanswers.com/Top10FAQ/t10-hostheaders.htm

Using Host Headers to Allow for One I.P Address to Host Multiple Domains:
http://www.4guysfromrolla.com/ASPscripts/PrintPage.asp?REF=/webtech/080200-1.shtml

HOW TO Use Host Header Names to Configure Multiple Web Sites in Internet
Information Services 5.0 (308163):
http://support.microsoft.com/?id=308163



In your case, it sounds like something is misconfigured assuming you didn't
change the default ports. You mentioned earlier you installed DNS but wasn't
sure what to do with it. Simply, under your zone name (like domain.com),
make sure the machine name has either self registered or manually entered.

For the resource records (www, etc), rt-click domain.com, choose new Host
record. Type in www, and provide the same IP address. You can also create a
blank record by rt-clicking, new host, keep the name box blank, and just put
the same IP in. This allows you to connect by http://www.domain.com and
http://domain.com (without the www). Both of these must match the website
properties hostheader names. But this will only work on the private internal
network, and not from the Internet. From the internet you would point to the
router's outside IP address. To make the outside requests work bringing them
to the webserver, yes, you must make a port remap rule allowing inbound port
80 requests coming in on the outside interface (the 63.x.x.x number you
mentioned), to go to the private 192.168.x.x or whatever IP it is of the
machine. If you want to host if for all to see from the Internet, you must
change the www address for your domain name to point to the outside IP of
your router. This way you can connect by name, and not needing the IP. But
if just for private use, then connect by IP.

Or you can create an alias for the real machine name. If the machine name is
'ralph' under domain.com, and ralph is already a host record created under
the zone set with it;s own IP, then rt-click, new Alias (or CNAME), type in
www for the name, and point it to ralph.domain.com.

315982 - HOW TO Configure DNS Records for Your Web Site in Windows 2000:
http://support.microsoft.com/?id=315982

But more imporantly about DNS, in order for your own internal machine to use
your own DNS server, and get to the website by name internally (only), you
must ONLY set itself as the DNS address in it's IP properties, and no other
DNS, or it may or may not use it if you mix numbers. If you have your ISP's
DNS set in your IP properties, or getting it from DHCP somewhere (such as
your router?), then it will never use itself. You have to set it to be a
client of itself. As for DHCP, the machine should really have a static IP
configuration.

Read a little on how DNS works on the Internet in regards to domain names
and their websites.

IIS Answers - DNS basics for IIS Administrators:
http://www.iisanswers.com/articles/dns_for_iis.htm

I hope that sets you in the right direction.

Ace


.