Re: URL for Internal Web Sites not working
- From: "Jim Harrison \(ISA SE\)" <jmharr@xxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 15 Feb 2007 13:21:35 -0800
Use the IIS host header feature available on any virtual web server.
This way, you can operate them all on port 80 and they won't conflict.
The IIS help discusses this in detail.
--
Jim Harrison (ISA SE)
This posting implies no warranty and confers no rights.
"news.eclipse.net.uk" <nick@xxxxxxxxxxxxxxx> wrote in message
news:O-SdnURGrNPLJknYnZ2dnUVZ8qqlnZ2d@xxxxxxxxxxxxxxxxx
This is probably really simple - for someone that understands networking!!
I am running SBS 2003 R2 / ISA 2004 in a configuration with 2 network cards.
I have successfully published several web sites from a server in the network
(not the SBS server itself) using Web Publishing Rules.
Because I am serving a number of sites, for simplicity I have used different
port numbers on IIS. So, the request coming in on Port 80 is bridged by ISA
to, say, port 82. For example, an external user can request
http://sub.domain.com and ends up being served a page from port 82 on my
internal server "fred".
Internally, I can reach http://fred:82. However, I want to be able to use
http://sub.domain.com internally. At the moment, it just dies with a DNS
error.
Where do I start to look?
Thanks,
Nick
.
- Follow-Ups:
- Re: URL for Internal Web Sites not working
- From: Nick Locke
- Re: URL for Internal Web Sites not working
- References:
- URL for Internal Web Sites not working
- From: news.eclipse.net.uk
- URL for Internal Web Sites not working
- Prev by Date: URL for Internal Web Sites not working
- Next by Date: about isa2006
- Previous by thread: URL for Internal Web Sites not working
- Next by thread: Re: URL for Internal Web Sites not working
- Index(es):
Relevant Pages
|