Help! - Internal Website (Win2003 Ent)

Hello everyone,

I'm new in server administration (currently with Win2003 Server Enterprise)
and I want to accomplish something. We have a server in our office (named,
say, ServerXYZ123) and it's available only from inside our office. I want to
be able to create internal "websites", so when we type http://production/ or
http://customers/ (etc.) in our browsers, it always points to the same
server (ServerXYZ123) because I don't want to use
http://ServerXYZ123/production/ or http://ServerXYZ123/customers/; and also,
the browser must know those "domains" are internal.

Can you help me with this?

Thanks in advance,
SB-R

Create two A records on your DNS server. Each name (customer & production)
should point to the same IP, which is ServerXYZ123. This will accomplish
using the URLs of http://production and http://customer. In your post you
show an example of this and of http://serverxyz123/production, which is
different and will not work with the above example.


"segis bata" <(E-Mail Removed)> wrote in message
news:u%(E-Mail Removed)...
> Hello everyone,
>
> I'm new in server administration (currently with Win2003 Server
> Enterprise) and I want to accomplish something. We have a server in our
> office (named, say, ServerXYZ123) and it's available only from inside our
> office. I want to be able to create internal "websites", so when we type
> http://production/ or http://customers/ (etc.) in our browsers, it always
> points to the same server (ServerXYZ123) because I don't want to use
> http://ServerXYZ123/production/ or http://ServerXYZ123/customers/; and
> also, the browser must know those "domains" are internal.
>
> Can you help me with this?
>
> Thanks in advance,
> SB-R
>

"NetEng" wrote:

> Create two A records on your DNS server. Each name (customer & production)
> should point to the same IP, which is ServerXYZ123. This will accomplish
> using the URLs of http://production and http://customer. In your post you
> show an example of this and of http://serverxyz123/production, which is
> different and will not work with the above example.

This will solve the first part of your request, but users going to
http://production and http://customer will be looking at the same page.

I'm not an HTML expert, but I believe you can create an index.html (or, a
..asp file -- I know even less about that) which will examine the
http-get-request and re-direct the user to appropriate subdirectory.

You may want to ask in one of the asp or webmaster groups.

You have already gotten an answer to the DNS part.

Once the client is able to find the server with the name you have
specified, you need to create multiple websites in IIS and assign a host
header value that matches the name you have choosen. That is, for the
"production" website, create a new website, and when asked to provide a
host header, write "production".

This will allow you to run multiple websites in IIS.

This will also help you to configure IIS:

"Using Host Headers to host multiple websites on IIS 6.0"
http://www.gafvert.info/iis/article/...e_websites.htm


Good luck!

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


segis bata wrote:

>Hello everyone,
>
>I'm new in server administration (currently with Win2003 Server
>Enterprise) and I want to accomplish something. We have a server in our
>office (named, say, ServerXYZ123) and it's available only from inside our
>office. I want to be able to create internal "websites", so when we type
>http://production/ or http://customers/ (etc.) in our browsers, it always
>points to the same server (ServerXYZ123) because I don't want to use
>http://ServerXYZ123/production/ or http://ServerXYZ123/customers/; and
>also, the browser must know those "domains" are internal.
>
>Can you help me with this?
>
>Thanks in advance,
>SB-R