• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3540
  • Last Modified:

MessageLabs Proxy

I am trying to configure out client proxy on out main server for Messagelabs - I can ping the proxy address given, I can go out on the port on the firewall, but cannot get it to proxy pages.

I get the following error - will be logging with Messagelabs when I can see how!!

2009/12/22 21:39:25| Accepting proxy HTTP connections at 0.0.0.0, port 3128, FD 169.
2009/12/22 21:39:25| Accepting ICP messages at 0.0.0.0, port 3130, FD 170.
2009/12/22 21:39:25| Accepting HTCP messages on port 4827, FD 172.
2009/12/22 21:39:25| Accepting SNMP messages on port 3401, FD 173.
2009/12/22 21:39:25| Ready to serve requests.
2009/12/22 21:39:25| Finished rebuilding storage from disk.
2009/12/22 21:39:25|         0 Entries scanned
2009/12/22 21:39:25|         0 Invalid entries.
2009/12/22 21:39:25|         0 With invalid flags.
2009/12/22 21:39:25|         0 Objects loaded.
2009/12/22 21:39:25|         0 Objects expired.
2009/12/22 21:39:25|         0 Objects cancelled.
2009/12/22 21:39:25|         0 Duplicate URLs purged.
2009/12/22 21:39:25|         0 Swapfile clashes avoided.
2009/12/22 21:39:25|   Took 0.0 seconds (   0.0 objects/sec).
2009/12/22 21:39:25| Beginning Validation Procedure
2009/12/22 21:39:25|   Completed Validation Procedure
2009/12/22 21:39:25|   Validated 0 Entries
2009/12/22 21:39:25|   store_swap_size = 0k
2009/12/22 21:39:25| Configuring proxy1.eu.webscanningservice.com Parent proxy1.eu.webscanningservice.com/3128/0
2009/12/22 21:39:26| storeLateRelease: released 0 objects
2009/12/22 21:40:23| TCP connection to proxy1.eu.webscanningservice.com (proxy1.eu.webscanningservice.com:3128) failed
2009/12/22 21:40:24| TCP connection to proxy1.eu.webscanningservice.com (proxy1.eu.webscanningservice.com:3128) failed
2009/12/22 21:40:26| TCP connection to proxy1.eu.webscanningservice.com (proxy1.eu.webscanningservice.com:3128) failed
2009/12/22 21:40:27| TCP connection to proxy1.eu.webscanningservice.com (proxy1.eu.webscanningservice.com:3128) failed
2009/12/22 21:40:28| TCP connection to proxy1.eu.webscanningservice.com (proxy1.eu.webscanningservice.com:3128) failed
2009/12/22 21:40:29| TCP connection to proxy1.eu.webscanningservice.com (proxy1.eu.webscanningservice.com:3128) failed
2009/12/22 21:40:30| TCP connection to proxy1.eu.webscanningservice.com (proxy1.eu.webscanningservice.com:3128) failed
2009/12/22 21:40:31| TCP connection to proxy1.eu.webscanningservice.com (proxy1.eu.webscanningservice.com:3128) failed
2009/12/22 21:40:32| TCP connection to proxy1.eu.webscanningservice.com (proxy1.eu.webscanningservice.com:3128) failed
2009/12/22 21:40:33| TCP connection to proxy1.eu.webscanningservice.com (proxy1.eu.webscanningservice.com:3128) failed
2009/12/22 21:40:33| Detected DEAD Parent: proxy1.eu.webscanningservice.com
0
CaringIT
Asked:
CaringIT
1 Solution
 
chukuCommented:
check the firewall, you might be blocking the response and therefore fail the connection
0
 
CaringITAuthor Commented:
A reboot of the server fixed the problem in the end so suspect it was a service not starting properly in the end.  Has been a DNS issue on the network which could also have been affecting it.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now