Re: Intranet Issue
From: Dan (anonymous_at_discussions.microsoft.com)
Date: 12/02/04
- Next message: Ron Weldy: "Re: Trouble with ASP.NET"
- Previous message: Robert Bird: "RPC over HTTP Proxy Not Making RPC Virtual Directory in IIS"
- In reply to: Phillip Windell: "Re: Intranet Issue"
- Next in thread: Phillip Windell: "Re: Intranet Issue"
- Reply: Phillip Windell: "Re: Intranet Issue"
- Reply: Phillip Windell: "Re: Intranet Issue"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 2 Dec 2004 15:12:07 -0600
I dont have a proxy server. I just have a Watchguard firewall. Yes now i
remember the settings i was talking about was the proxy setup where you can
bypass certain sites in the exception list. Since i dont use a proxy then i
think im ok.
"Phillip Windell" <@.> wrote in message
news:%23gEWpDL2EHA.3236@TK2MSFTNGP15.phx.gbl...
> "Dan" <anonymous@discussions.microsoft.com> wrote in message
> news:%23gplp2K2EHA.3064@TK2MSFTNGP10.phx.gbl...
> > I created an intranet website. I created a dns record called intranet so
> > when users type in http://intranet it goes to my site. I remember with
> older
> > software i think NT4 or 98 you would have to add this to a setting so
when
> > users type this in their browser it will stay in the internal LAN rather
> > than trying to resolve it or access it on the outside. How do you
> configure
> > this in windows 2000. Also I get an active x security warning on some
> > computers when they view the site how can i setup a GPO to allow this
site
> > to low securty.
>
> The exception list is part of the browser. It doesn't matter if it was 98,
> NT, 2000, XP, or 2003. It is all the same. You never needed that in 98 or
> NT either,...what it really depended on what what kind of device was being
> used to "provide" the Internet (proxy, nat firewall, etc) and how that
> device is built, configured, and how its "behavor logic" is designed.
>
> For example a CERN Compliant Web Proxy would resolve the URL on behalf of
> the client (client doesn't resolve it itself typically in such cases). The
> DNS used by the proxy must be the one setup to resolve to the IP# you
> desire. It then compared the discovered IP# to the Local Address Table
(LAT)
> and if it was in the table the proxy "dropped out" and let the client
acess
> the site directly, but it the address was not in the LAT it would pass the
> request to the outbound Internet router. A NAT-based Firewall device
would
> be a little different, the client would resolve the URL itself, so
whatever
> DNS it used had to be the right one so it would resolve to the right
> address. Once it had the address it would drop the request on to the
"wire"
> if it was the same subnet or pass it to the Layer3 routing scheme (default
> gateway or static specified gateway). If the request then reached the
> Firewall Device it would compare it to it LAT and process accrdingly.
>
> I have used each of those variations here at our location and run Win95,
> Win98, NT4.0, Win2000, XP, and Server 2000 & 2003. I have never had to
> include an exception in the Browsr's exception list.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
- Next message: Ron Weldy: "Re: Trouble with ASP.NET"
- Previous message: Robert Bird: "RPC over HTTP Proxy Not Making RPC Virtual Directory in IIS"
- In reply to: Phillip Windell: "Re: Intranet Issue"
- Next in thread: Phillip Windell: "Re: Intranet Issue"
- Reply: Phillip Windell: "Re: Intranet Issue"
- Reply: Phillip Windell: "Re: Intranet Issue"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
