Re: URL for Internal Web Sites not working

Tech-Archive recommends: Fix windows errors by optimizing your registry

Your AD DNS needs to be a split DNS. Create a new zone using your
external domain, manually add the relevant entries (www, etc) pointing to
the /internal/ IP.

"Nick Locke" <nick@xxxxxxxxxxxxxxx> wrote in
news:5Z-dnXPK0r4K7UjYnZ2dnUVZ8saonZ2d@xxxxxxxxxxxxxx:

Jim,

Thanks - that would solve me needing to use different ports (I had
actually recently discovered that and already have it on my list of
things to do).

However, unless I'm missing something, that won't help with the issue
- I can't use the "extenal" URL from an "internal" PC and get to the
right pages. It doesn't get as far as trying to find the server - the
DNS lookup fails.

"Jim Harrison (ISA SE)" <jmharr@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:43A3621F-60FD-4B09-A625-1167E6EC9C20@xxxxxxxxxxxxxxxx
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






.

Relevant Pages

  • Re: Cant access web on local network server
    ... Yes my Windows 2003 R2 Standard Server is a DC domain controller. ... How do I open DNS for the outside? ... What port should I give access to? ...
    (microsoft.public.windows.server.general)
  • Virtual host "lite"?
    ... redirect an incoming we request based on DNS name, ... "http://webmail.domain.com " will automatically be redirected to port ... fall over and the Boss works out what a "server" is.. ...
    (comp.os.linux.networking)
  • Re: Please help confused iptables user
    ... >> system talk to a remote 22. ... First rule says allow IN anything destined for your IP port 22. ... >> about DNS, asking remote servers if they'll accept your OUTBOUND mail), ... the "remote" DNS server is on the same network, ...
    (comp.security.firewalls)
  • Re: Setting up website on my DSL
    ... Well when I telnet to www.geewhizbang.com on port 80 I get something listening there. ... I assume you are doing a port forward on your router for port 80 to your web server. ... Just go into the andanved TCP/IP properties of the NIC on the DNS tab and untick the "Register this connection in DNS" This will make the errors go away. ...
    (microsoft.public.windows.server.dns)
  • Re: SRV RRs support in Internet Explorer?
    ... It had a remaining dynamic port bias, which it shouldn't have had, and was ... and MS DNS Server could then be as follows: ... > web access from a client to web server and, to keep things simple, also ...
    (microsoft.public.win2000.dns)