| Remember, the proxy is not used when accessing internal pages. This is
not a proxy problem and logging a call to the IMC (which maintains the
production external proxy servers at CXO, ALF and DAS) isn't going to
do a bit of good. The client talks directly to the internal host.
As the previous note mentioned, the no proxy settings should be set...
as they have been since the beginning to time. ".dec.com" for Netscape
Navigator and "*.dec.com" for Internet Explorer. This is not new. ##
By the way... the proxy settings for access should be:
www-proxy.{your-site-code}.dec.com (in most cases)
(Ping it to see if it works for you; it's not everywhere.) An
attempt was made to point www-proxy at each site DNS domain to the
closest/fastest proxy server on our corporate WAN. (People still point
to PA or CRL even though there are closer servers that would minimize
WAN traffic.)
This, of course, only applies to people not using AltaVista Tunnel for
access to the network. In that case, you never use a proxy and do not set
a "no proxy" setting at all. (You're on the external and internal
Internet at the same time.)
--Ron
## In some sites, there might be special caching proxy servers that
are intended to reduce WAN usage. In these cases, "no proxy" might
not be set -- all data is funneled through the cache. This is
mostly overseas.
|