Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Crashplan and Firewall

Hello all,

We have an ongoing issue with Crashplan PROe and, we believe, our RV220W.  Basically we believe Crashplan is triggering the firewall to block the Crashplan server from the network. I have searched the interwebs and have found some similar descriptions but no resolution. It may seem like a Crashplan support question but reading below you will see why we believe it is something to do with the RV220. Details are:


Cable Modem -> RV220W -> Internal network. 

On the network we have a Mac Mini which runs a Crashplan PROe server. Staff have the Crashplan client on their machines and connect to the server by it's fixed IP and port. The Crashplan clients contact the server for config settings and then proceed to backup to the Crashplan PROe server's storage.

This works fine for roughly one minute after which the Mac Mini disappears from the network. At this point Crashplan cannot backup to it, and we cannot explore the Mac Mini or screen share it over the network. We have a monitor physically plugged into the Mac Mini and the machine is fine but we can see the network activity drops to nothing on the Mac Mini.  Rebooting the Mac Mini fixes the problem but only for roughly a minute at which point it drops off the network again. 

- The behaviour is the same regardless of what IP we assign the Mac Mini or if we switch to DHCP. 

- If we connect the Mac Mini to our second network (2nd cable modem -> Netgear WNDR5400 - > Internal users) then the Mac Mini / Crashplan PROe server is stable and remains accessible to users on this network. 


So, given the only difference is the firewall/DHCP being the Cisco vs the Netgear we are thinking it is most likely a config issue with the RV220W. Perhaps the Cisco unit sees the traffic as naughty and shuts down the Mac Mini's access to the rest of the network?


Any advice would be greatly appreciated. 


Everyone's tags (2)
CreatePlease to create content