RPC used port 135 - how to change?

[MankeyM0nkey]

Hi guys, my ISP has recently blocked any outgoing TCP/UDP packets on port

135, this has caused me a bit of a headache but I got a partial solution in

place...what I would prefer to do is to change svchost.exe which is running

on this port. It's not a virus, I've checked many times to be sure...as far

as I can tell it's RPC endpoint mapping, the 2003 srv being used by my

client has DHCP and Remote Access & Routing installed.

I've trawled the net trying to find a way to do this, the closest I got was

to adding an DWORD to NTDS parameter section to specific a TCP/IP port but I

still get svchost running on port 135.

Any suggestions for changing the port number?

[John Veteran]

svchost is the process that is used for your system services. if your ISP is blocking port 135, you'll have to get them to unblock it. i really don't suggest you try and change the port yourself because it will just turn out to be more work than it's worth.

[DreamweaverN]

If you are using this for say your local network then even if it blocked 135 it shouldn't cause any problems. Sounds more like a virus if it really really requires it.

[Japlabot]

you can set ICF to have the Internal Port as 135 and an External Port as Something else, and then on the other end, set that external port to that something else, and have the internet port as 135

would that work?

[Aaron P]

For what reason do you need to make RPC requests across the Internet? Add some more detail and we might be able to give something more concrete.

[John Veteran]

  Quick Reply said:

you can set ICF to have the Internal Port as 135 and an External Port as Something else, and then on the other end, set that external port to that something else, and have the internet port as 135

would that work?

no. ICF doesn't remap ports.