Tasklist Command and RPC Server Port

[anthonymeluso]

I really like the tasklist command in Win XP and Win 2003, however I can't get any of my client which has Windows Firewall turned on, to respond when I send this command to them. It tells me that the RPC server is unaviable. However, the tasklist command works fine on all my Win 2003 machines, probably due to the fact that the firewall is turned off.

So my question is what port does the RPC server run on so I can open and query my clients with the tasklist command?

Thanks in advance,

Anthony

 

[anthonymeluso]

I guess no one has run into this problem?



Anthony

 

[SMBgeek]

This one could be tricky. Most RPC based services on Windows servers register on random ports. When the service loads it registers its port number with the endpoint mapper service. The endpoint mapper service always runs on port 135 so that clients can query for the correct port for the desired service. For example, when I fire up Outlook on my workstation it first queries port 135 on the Exchange server to find out which ports the Exchange related RPC services are running on, then connects directly to those ports.

So, this obviously creates an issue for you since you won't know what ports to open and allow through the firewall (because they change). You may want see if there is a registry hack to fix the particular ports for that rpc based service. Then you know what to open!

Hope this helps

http://www.smbgeek.com

 

[anthonymeluso]

Thanks for the suggestions. I'll do some more research and search the MS knowledge base for any clues on what port this thing runs on.

Anthony

 

[anthonymeluso]

Strange, I did my weekly restart of the PCs and I tested it out and it works. I tried tracking down the port number and its dynamic so that would mean I would have to open a range of ports on the firewall, which is probably not safe.

It is also probably working since no one has logged on to their machines yet. I guess I will see come Tuesday.

Thanks

Anthony