Nevermind tunneling, DCOM over anything but 135?

I'm still fighting with this, and I can't seem to get the Nirvis.SlinkeClient to talk over anything but port 135, which is firewalled between my work and home.

Colby, I've read that the component itself can override the settings in the dcomcnfg program -- is there any chance that this is what's going on? I've tried using setting the default protocol to connection oriented TCP/IP only, on a high port, as well as specifying it directly in the Nirvis.SlinkeClient application's properties. No matter what, my client is trying to talk to the server on 135.