Re: Problem with IIS on LAN
From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 12/31/04
- Next message: mmcgowan: "Default website and OWA"
- Previous message: Jeff Cochran: "Re: Setup of IIS on Windows XP sp1"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 31 Dec 2004 12:27:59 -0800
Jeff is pretty much correct. You do not have an IIS issue. You have a
network/routing configuration issue, and no generic installation
guide/newsgroup posts will help you -- you just havve to know what you are
doing. All the behaviors that you observe are expected -- you just need
someone to explain them to you.
In any case, if you do not fix your issue, I believe you can abandon IIS,
use another web server, and still see the exact same behavior. Here is why:
> The problem is I cannot view any web pages on my main PC. I can
> run them (asp + htm) fine on the web server but not the main PC.
This means IIS is fine. You have a networking issue of some sort (i.e. your
machines are not configured properly to see IIS on the LAN)
> From the main PC I can read files on the webserver and can see a
> web page when I enter the direct path to the file such as
> \\webserver-b\WebSites\testsite\Index.htm into my browser
This means that main PC can see "webserver-b" and its UNC share (no HTTP
involved, so says nothing about web serving)
> but I get 'The page cannot be displayed' msg when I type
> http://localhost/testsite/Index.htm.
This is by-design, since "localhost" refers to "the machine you're running
the browser from" -- main PC -- and you said that IIS is *not* running on
this machine. Thus, you will only get "The page cannot be displayed" from
this machine and it is expected.
> When I type http://webserver-b/testsite/Index.htm or
> when I type http://159.254.210.101/testsite/Index.htm
> IE wants to connect to the internet.
Sounds like a browser configuration issue. You have network connection
between main-PC and webserver-b using UNC (one type of protocol), yet
network connection over HTTP (another type of network protocol) causes IE to
pop up that Internet connection dialog.
> When I try to view an ASP file in IE it starts up MS Frontpage.
This is really unrelated and does not indicate anything wrong -- just that
you do not understand why it happens. An ASP file has many defined actions
for Windows to perform, depending on the order/type of programs installed,
and not all of which are comparable, so it really depends on what action you
chose. For example, given an ASP file, notepad could OPEN or EDIT it in raw
HTML form, FrontPage could OPEN or EDIT it in rich HTML form, and IE could
open it in dynamic interpreted form. Etc. I'm pretty certain that FrontPage
was configured by you to view an ASP file in IE -- even if you do not
remember nor know why. It is of course all configurable as an option so you
can change the behavior, but it really has no relation to your current issue
at all. It is a client-side behavior unrelated to networking.
What sort of configuration changes did you make on main-PC when you failed
to get IIS working on it? I suspect you've already got some bad settings on
main-PC that is causing your current problems.
How are the two PCs connected to each other (networking-wise)? Please trace
and describe every network adapter and device starting from main-PC to
webserver-b . How are the PCs connected to the Internet (why do you think
the external IP will work?).
Finally, it seems that getting networking configured is just a bit too much
for you -- why is IIS not working on main-PC ? Seems like you'd avoid all
the networking stuff that you do not need (yet) to be able to use VB.Net.
Also, you are running W2KSP2, so your IIS/OS will be vulnerable to all sorts
of virus/worm on the Internet from the past 4 years and will likely get
infected within minutes if you are not careful with networking setup. With
your current SW patches, you will be safer either developing on a single W2K
PC that is not connected to the Internet in any way, or run XPSP2 with its
firewall enabled.
Good Luck.
-- //David IIS http://blogs.msdn.com/David.Wang This posting is provided "AS IS" with no warranties, and confers no rights. // "SJM" <akronym_takeout_@ozemail.com.au> wrote in message news:eFHMLwI7EHA.3368@TK2MSFTNGP10.phx.gbl... I am hoping someone can help me with this before I abandon IIS. I have looked at a number of prior posts on www but they have not really helped, neither did step by step installation guides. I have a 2 PC network at home both running Win2000 sp2. One PC is the dedicated webserver (IIS 5), the other is my main PC on which I will do all my work. This PC also has IIS 5 but not running, and it also has VB.NET installed. The problem is I cannot view any web pages on my main PC. I can run them (asp + htm) fine on the web server but not the main PC. >From the main PC I can read files on the webserver and can see a web page when I enter the direct path to the file such as \\webserver-b\WebSites\testsite\Index.htm into my browser but I get 'The page cannot be displayed' msg when I type http://localhost/testsite/Index.htm. When I type http://webserver-b/testsite/Index.htm or when I type http://159.254.210.101/testsite/Index.htm IE wants to connect to the internet. When I try to view an ASP file in IE it starts up MS Frontpage. I was originally unable to get IIS 5 to work on the main PC which is why I used the 2nd PC as a webserver, but I need to be able to view my test websites on the main PC. To get around the problem of the Dial Up connection msgbox popping up, I have ticked 'Bypass proxy server for local addresses' even though I don't use a proxy server for my internet connection, so I don't know if this is really working. I thought I had set up my firewall appropriately, but just in case shut it down, and it made no difference. Any advice is very much appreciated.
- Next message: mmcgowan: "Default website and OWA"
- Previous message: Jeff Cochran: "Re: Setup of IIS on Windows XP sp1"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
