Have BatchPatch working Internally, but…

[AdvanSuper]

I have BatchPatch working internally within our Domain network, but I was testing with a laptop connected over VPN and I was getting the RPC unavailable error. This laptop works fine with BP when joined to the network without a VPN. Where should I begin to look to see what is causing the issue? I’m currently tasked with finding a way to remotely install/push out updates for end users who will eventually be working from home at some point.

I appreciate any help on the matter, thank you.

[doug]

“RPC unavailable” is almost definitely due to a firewall problem or some kind of similar access issue. Many VPN clients have firewall software built-in, which could cause this. But it could also be caused by your VPN infrastructure. In either case, the issue is that BatchPatch cannot communicate with the RPC server on the target host because it appears to not be available. Since you’ve already established that things work normally within your network, you know that the RPC server on the target is enabled. The issue is only when you’re trying to work across the VPN. That said, you need to examine your VPN setup and figure out how to allow RPC communication (and full PC to PC communication) across the VPN.

-Doug

[AdvanSuper]

Thanks for the info. It turned out to be a routing issue. What I did as a test was connect myself via VPN and I was able to push out an install to the machine. We just need to add the VPN network block to our routing tables and we’ll be good to go.

[doug]

Excellent. Glad you got it working. Thanks for letting me know.

-Doug

[Author]

Posts