@CCRDude wrote:
The distinct server port 3689 may not be as much a problem as the multicasting used to announce where the server is.
Wasn’t there some kind of daap proxy thing for exactly this kind of setup? I quick googling showed me Rendezvous Proxy, not sure though if that is the best solution 😉
Yeah… that’s the problem. VPNs generally don’t pass multicast, so you’ll need to have a rendezvous announcer on the remote side. Rendezvous Proxy is the only one I know for windows.
You’d have to add an entry for _daap._tcp on 3689 (and _rsp._tcp, if you wanted the soundbridge to work remotely).