Guest User!
You are not Sophos Staff.
Greetings!
I recently replaced a UTM 120 with an XG 125. Crashplan Pro (usually running on ports 443 and 4242) hasn't worked since. Taking the XG out of the loop allows communication, so it's definitely something with the new unit's config, but even if I allow all traffic out and disable HTTP/HTTPS scanning, it won't communicate. Any suggestions?
Thanks,
Peter
First verify that you have the correct network interface selected for Crashplan (in the app). I've had this change several times on my computer.. maybe because I've been playing around with VPN apps and stuff.. Right now it had shifted again and selected my tap interface, instead of eth6 which was my intel card with my local IP shown.
Next you should be able to get this to work following my post (answer #3 in this thread) to get it to work. It still works for me, and the app is now v4.7.0
Thanks.
Unfortunately that wasn't the problem, I also have a number of interfaces and all of them were checked. I couldn't get the FQDN group policy to resolve the blocking of Crashplan. But after some experimenting I fixed it by creating a policy allowing unrestricted HTTPS access for the server where Crashplan runs.
This method should be useful in other cases like this [:)]
... I couldn't get the FQDN group policy to resolve the blocking of Crashplan. But after some experimenting I fixed it by creating a policy allowing unrestricted HTTPS access for the server where Crashplan runs...
Seems I'm back with my old problems after upgrading XG to v16.0.x. I'm not able to connect to CrashPlan Central anymore (app v4.8.0).
Do you have any advanced settings in that 'CP' rule of yours?
