Discussion Locked

CacheFlow Proxy

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

When trying to access a web site my customer gets an "Access Denied:Unathorized point of entry" error message. If accessed outside the proxy there is no error message and you gain access. I can find nothing in the owners manual that covers this.
Dan Tipton
dtipton489@yahoo.com
Any assistance rendered is greatly appreciated.

7 replies

by ntoz

Since you dont mention what version your using of the appliance, I will provide the answer for the 2000 model.

36 CacheFlow Inc.
Client HTML Requests Fail
When a request for a Web document fails, it indicates one of the
following:
? the Web browser is not properly configured for the
CacheFlow 2000
? the CacheFlow 2000 cannot access the requested document
? the CacheFlow 2000 is not properly configured
? the CacheFlow 2000 is not functioning
To try and locate the problem, follow thesteps outlined below:
1. If the CacheFlow 2000 is used to access the Internet, and the
CacheFlow 2000 has been working properly, the most likely
cause of failed requests may be the route between the
CacheFlow 2000 and the Internet or intranet. Before you spend
time troubleshooting the CacheFlow 2000, verify your
connection to the Internet using the ping and traceroute
commands from the command line interface. If you are able to
ping the destination from the CacheFlow 2000, use the testcommand to verify the device can get the object. For
information on the ping, traceroute, and test commands, see the
CacheOS Management and Configuration Guide. If the request
fails, try other HTML requests to verify all requests fail.
2. The CacheFlow 2000 can be configured to deny access to
address groups. If the CacheFlow 2000 is configured for
forwarding or filtering, verify the requested address does not
match a denied subnet and mask. To configure deny settings in
the Web interface, from the home page select Management, then
ICP/Forwarding.

by ntoz

3. If your network is not configured for transparency, check the
Web browser to see if it is using a PAC file for autoconfiguration.
If the Web browser is configured to use a PAC
Troubleshooting
file, verify the address of the PAC file is correct, and the file is
accessible. See the CacheOS Management and Configuration
Guide for additional information. If auto-configuration is not
being used, check the Web browser?s proxy configuration. If you
are not using transparency, the Web browsermust be configured
for the CacheFlow 2000?s IP address and port. See the CacheOS
Management and Configuration Guide for information on
configuring the clients.
.4. If the correct IP address and port for the proxy server is
specified in the Web browser, try pinging the IP address to
verify the CacheFlow 2000 is accessible from the workstation. If
it does not respond to the ping, verify it is operational as
described on page 30. Also verify you can ping other nodes on
the network. If youcan ping the CacheFlow 2000, try pinging
the workstation from CacheFlow 2000 command line interface.
5. If the CacheFlow 2000 responds to the ping, verify the
CacheFlow 2000?s configuration. If it is configured to forward
requests, verify the server to which the CacheFlow 2000 is
forwarding requests. If the CacheFlow 2000 is not forwarding
requests, check the default gateway address and DNS address.
6. If the CacheFlow 2000?s default gateway address and DNS
address are correct, try pinging each address from the command
line interface to verify the servers are running. Be sure to ping
the gateway and DNS server from the same network segment
where the CacheFlow 2000 is connected.

by ntoz

7. If the default gateway is accessible, the problem most likely lies
outside the local network. To verify the problem is not
associated with the CacheFlow 2000, you must configure your
workstation for the same gateway address as the
CacheFlow 2000, and configure the Web browser not to use a
proxy server for HTTP requests

by dtipton489

Actually we have CacheFlow 625. We finally fixed the problem by allowing access to the site through the deny.txt list. After the address was cached once access was allowed from that point on. Even though we removed the line from the "allow access" list. Thanks for the response. Also we are not using PAC, we configure each individual machine.

This discussion is closed to new replies.