wrote:
> My question was really directed towards IIS management on my Vista PC.
> Maybe
> I did not make that clear. URL http://192.168.0.100/ is meant to
> give
> access to the web server (that works with loopback http://127.0.0.1/
Yes it's working with the loop back IP or Localhost IP of .0.0.1 which
is internal to on the machine that IIS is running on or is Local to the
machine.
You are working with IIS locally if you give the 127.0.0.1 or Localhost
as part of the HTTP:\\127.0.0.1.appname.asp or aspx(.NET) or
HTTP:\\Localhost.appname.asp or aspx in a browser address line with the
browser running on the local machine.
> )
> through my local area network created by my router. My Vista PC is
> connected
> to a router which in turn is connected to a cable modem which in turn
> is
> connected to my ISP. IP 192.168.0.100 is simply the subnet IP address
> given
> (as a static IP address) by my router to my Vista PC.
Yes, it is the local IP that is given to the machine by the router when
the IIS Web server and application is being accessed from another
machine on the LAN (Local Area Network) behind the router. A browser
address from a machine on the LAN that is to access the Web server on
the LAN must give that HTTP:\\192.168.0.100\appname.asp or aspx to
access the Web server on the machine that is hosting IIS on the LAN and
the application.
And that I know of, routers don't give out static IP(s). Routers give
out DHCP IP(s) to a computer's NIC that is requesting a DHCP IP from the
DHCP server on the router. The computer's NIC must be configured to use
a static IP in the known static IP range of IP(s) that is done with a
manual setup of the NIC.
> I guess you are
> not
> familiar with routers. Port 80 is just the default port used by the
> hypertext transport protocol, HTTP. Specifying port 80 is never
> necessary
> because it is the default for the HTTP protocol.
But HTTP does not have to be on port 80 if IIS has been configured to
not use TCP port 80. It could be port 8080 that IIS is listening.
And HTTPS is on TCP 443 that never has to be specified for the HTTPS
protocol.
>
> Sorry to be critical of your answer. You have misunderstood my
> question and
> that is my fault.
>
> Under Computer Management there exists Internet Information Services
> (IIS)
> Management. To the best of my recollection, I have enabled access the
> same
> way I did first time around, but I guess my recall is faulty. IIS is
> installed and the service is running; that is why http://127.0.0.1/
> works.
Yes, because 127.0.0.1 or Localhost points back to the NIC on the machine.
>
> Under Authorization Rules it says Allow All Users. I presume that
> means all
> outside users from the Internet. I presume this because it worked this
> way,
> first time around, AFAIR. It is possible that I am confused and that
> the
> rules only allows other users on my Vista PC. But I need help to find
> a
> solution which evades me and I cannot see a better option.
In away you are correct, but what it really means I think that all users
can access the site and IIS anonymously and don't have to give login
credentials.
>
> As I said in my opening post, I apologize for inappropriate cross
> posting. I
> am looking for expertise in IIS management. Please direct me to the
> right
> place.
IIS has nothing to do with this and a WAN (Wide Area
Network)/IP/Internet user client that wants to make contact with the WEB
server, which is done by the client giving the IP that is assigned to
your network by your ISP.
That would be the IP assigned to the modem. From there, you would
configure the router to use port forwarding on port 80 (open the port on
the router and have all inbound traffic forwarded to the LAN/IP on the
router to the machine that is hosting IIS is using on the LAN.
http://www.homenethelp.com/web/expla...arding-dmz.asp
In this case, you would want to use a static IP on the router that never
changes or has a chance to change on the computer. I don't think
192.168.0.100 is a static IP. It looks to be a DHCP IP and possibly the
first one in the DHCP range controlled by the DHCP server on the router.
192.169.0.99 and down would be static IP(s) not under the control of the
DHCP server on the router.
>
> On Oct 1, 4:49 pm, "Cari \(MS-MVP\)" <newsgro...@coribright.com>
> wrote:
>> Providing 192.168.0.100 is the TCP/IP address provided to your PC by your
>> router, you need to forward Port 80 (unless you're not using a default
>> setting) from the Router to that IP address. If your router is giving your
>> PC another address, forward to that address. Or give the PC a static IP
>> address and tell the router to forward Port 80 to that static.
>> --
>> Cari (MS-MVP) Printing & Imagingwww.coribright.com/windows
>>
>> "Dan" <nicor...@hushmail.com> wrote in message
>>
>> news:...
>>
>>
>>
>>> Please accept my apologies if I have cross posted this question
>>> inappropriately. I had this problem solved first time around but the
>>> solution evades me second time around. I needed to reinstall Vista when I
>>> made a mistake constructing a RAID storage array. (It works great now.) I
>>> wish to make my web server page(s) available to the Internet. At this
>>> point, I can access the webpage with URLhttp://127.0.0.1/but with
>>> http://192.168.0.100/I get a Gateway Timeout error. First time around I
>>> set up virtual web server on my router so I'm sure that still works. I've
>>> done every thing I thought I did first time around. Thanks in advance for
>>> help.- Hide quoted text -
>> - Show quoted text -
>
Similar Threads
Linear Mode
