The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: [OT] BlueTooth Headset - for SE T610


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [OT] IIS, domains, routers and host headers


  • To: <ukha_d@xxxxxxx>
  • Subject: RE: [OT] IIS, domains, routers and host headers
  • From: "Paul Gale" <groups@xxxxxxx>
  • Date: Fri, 29 Aug 2003 16:34:03 +0100
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

Mmm  - that would solve the router bit but I'm using Dreamweaver to
create/test pages - I'm not sure it will cope with different ports? If
possible I'd prefer to keep ports to 80. How do host headers work?

Paul.



-----Original Message-----
From: Pedro de Oliveira [mailto:p.oliveira@xxxxxxx]
Sent: 29 August 2003 15:47
To: ukha_d@xxxxxxx
Subject: RE: [ukha_d] [OT] IIS, domains, routers and host headers



Hi Paul

How about running it on a different port which is not accessible from
outside?

Pedro

-----Original Message-----
From: Paul Gale [mailto:groups@xxxxxxx]
Sent: 29 August 2003 15:14
To: ukha_d@xxxxxxx
Subject: [ukha_d] [OT] IIS, domains, routers and host headers


I think that only covers a small area ;)

I need some help with my home/office network setup or some pointers to
good resources where I can research the answers:

I currently have a W2K server running on my network using a 192.168.0.x
address. My ADSL router is setup to route one of my public IP addresses
and associated domain names through to the server (but only allows port
80 through). The website does not have anonymous access and file
security on all files is set to Administrator and one internal domain
user. AD is running. I have several HA and alarm pages and OWA setup on
this web server so want to keep it as secure as possible. I currently
only have one default web site setup on port 80. My internal domain is
set to home.local and the server and other servers on the network appear
as homeserver.home.local, cameraserver.home.local etc. I have a DNS
server running on this server too and all clients point to this before
my ISP DNS servers.

I'd also like to use this server as a testing server for developing web
pages and applications. I don't want this site to be accessible from the
Internet at all (or at the very least, protected). What's the best way
of doing this? Would host headers help??? (I don't know anything about
them).

My IIS knowledge is reasonably basic.

Ta,

Paul.





** UKHA2004 BE THERE! ** - start planning now.

http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe:  ukha_d-subscribe@xxxxxxx
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
List owner:  ukha_d-owner@xxxxxxx

Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/








Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.