ISP blocking port 135

[dhobson]

We lost the ability to logon to terminal services (NT4.0) and Exchange (5.5). I have a vpn site-to-site tunnel between the two offices (Hong Kong) and both servers can still be pinged. I'm being told from my tech in HK that the ISP has blocked port 135. Is there any workaround from the router/vpn standpoint? Port mapping? Any ideas would be helpful.

[rlcarr]

Who manages the tunnel?

All your provider should ever see is IP protocol 50 (IPSec) and UDP 500 (ISAKMP key exchange).

Your ISP would not have the ability to look into your tunnel to block traffic, it is already encrypted data.

[chris.burton]

If you are using a VPN tunnel then the fact that the ISP blocked port 135 should not affect you, since all of you traffic is tunneled through the ISP's network to the other end of the site-to-site VPN.

Chris