Re: Problems setting up a web server with Win XP and IIS 5.1...???



tw55447 <tw55447@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I'm having a problem with setting up my home web server, I'm hoping
that someone can shed some light, or point me in the right direction.
I'm running Win XP Pro with IIS 5.1. I'm trying to set my computer
up in order to make viewable from the web, basic html's.

This sort of thing does make me a bit nervous from a security standpoint.
I'd hope this isn't the same box you use as a workstation...

My
equipment is as follows:

Win XP SP2
IIS 5.1
Windows firewall
Linksys Router (model BEFSR41)
Cable modem (dynamic IP)

When you do get this up and running, go to www.dyndns.com or similar, and
set up a dynamic DNS service - and download the update client to run as a
service on this PC (or use your Linksys, which may have an update client
built in). Then you'll be able to use
http://myhostname.dynamicdnscompany.com and not worry about IP address
changes. But that's not relevant yet, of course.

What I've done is install IIS via the Win XP CD and set my settings
up for my default website (ie...ip = "all unassigned", port = 80,
enabled default content, mostly the default settings). Once that was
set up, I placed my html document in the web directory that IIS
points to. The html page displays when using the LAN ip or the
http://localhost...etc.

Next, I assigned a static local LAN ip to my web server (not in the
range of assigned ip's that my router gives out). I then, in the
router config page, forward all port 80 traffic to the server via the
static local LAN ip. I then check it via the local LAN ip,
http://localhost, as well as the ISP ip that is assigned...everything
works.


I then configured the windows firewall by adding port 80 as an
"Exception"...

But is it an exception for * or only the local subnet?

keeping the rest of the settings default.

So by this point, I'm thinking... IIS set up (check), router
configured (check), firewall allowing port 80 traffic (check).

Can you successfully telnet to your public IP address on port 80, from
outside?

So I
check the site via the local LAN ip as well as
http://localhost...etc. Everything works.

What about testing http://lanIP from another computer on your LAN, just to
make sure you can access it from something other than the box itself? That's
the interim thing I'd try....

Now this is where the problem starts. I try to access my site from
outside my network...nothing. I try to ping my server from outside my
network...nothing.

Unless you'd opened up inbound ICMP, that doesn't mean much.

I tried changing setting in IIS, the router, and
with windows firewall and re ping'ing...nothing (doing this for about
two weeks now by trying different settings and getting nowhere).

Pinging isn't a useful test. You can't ping www.citibank.com but I do think
their servers are operational :)

So yesterday, trying to isolate the problem, I hooked my server up
directly to the modem, got all my settings set back to the way I
think that they should be (with the new dynamic ip that my ISP gave
me), thus taking the router out of the equation. Well...I can still
see the site via the ip of the server as well as
http://localhost...etc. However when I ping the server from outside
the network, I get nothing. So, I get to thinking (which normally
gets me in trouble), I'll disable the firewall and see if that gets
me any different results. Well after turning window's firewall off,
I was able to ping my server from outside my network.

Ouch - don't connect without a firewall, even for a nanosecond. Put your
router back in place asap.

However, when
I try to view my site from outside my network (http://xxx.xxx.xxx.xxx
and http://xxx.xxx.xxx.xxx/index.html), I don't get anything, just a
"Cannot Find Server" error.


So as it stands right now...I'm thinking that something that I have
set up in IIS is not letting the site be viewable to the outside
world. I took the firewall and router out of the equation and the
problem still persists. I'm not sure if my router and firewall are
set up exactly the way they should be, but with those turned off, I
should be able to see my IIS site from the outside world...right?

I've been searching for instructions for setting up a web server with
IIS and Win XP, and have come across some websites that give you step
1-10, but they don't seem to be working for "outside my network"
access. I read somewhere that you might have to have asp.net
installed for IIS to work...is this true?

Nah. I'm not much of an IIS expert, but it sounds like you've got that part
right.

Nothing else that I've
read mentioned that. I'm still reading anything that I can in order
to get this thing running, but keep hitting dead end after dead end.

Any help would be GREATLY appreciated...suggestions, comments, links,
references...etc?

Thanks,
Thomas

The telnet would be a useful test....as would knowing whether you can access
the site from another machine on the same network.


.



Relevant Pages

  • Re: loss of SOME connectivity
    ... I "think" it is DNS. ... Yes, I can ping the router, AND the ISP DNS. ... I cannot connect the inet cable directly to the server because the inet is ... MS firewall not started. ...
    (microsoft.public.windows.server.sbs)
  • Re: IP Addressing
    ... Address of the ISA server? ... firewall and router). ... On the firewall create a static NAT entry as I wrote ...
    (comp.dcom.sys.cisco)
  • Re: Being hacked...
    ... Are you offering a webserver and ftp server to users on the internet as per having ... FTP and HTTP open? ... For internet attacks what I would look for is patterns in the firewall ... I am not an expert on IIS by any means but I do know if you are using FTP and IIS you ...
    (microsoft.public.win2000.security)
  • Re: Still cant connect to RWW or OWA remotely
    ... Re-running the CEICW, disabling the firewall, then re-running CEICW again, ... "Cannot find server or DNS Error". ... the DSL router 4-port switch. ... of the two NICs by clicking the Advanced tabs, ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN suggestions requested
    ... > connecting to the Internet through a cheap basic broadband router. ... necessarily mean you have to pop in a firewall, ... also mean only to secure the W2K server. ...
    (comp.security.firewalls)