Hey Jungs, ich hab ein geiles Tutorial gefunden wie ihr den ärger mit Rpc bzw Dcom endlich los werdet.
ZitatAlles anzeigen
Make a copy of the file rpcss.dll, as a backup in case anything goes wrong.
Copy the file from \windows\system32\rpcss.dll into one of your own directories, using Windows Explorer.
From the Start menu select Run…
Enter "regedt32" and click on OK.
Expand the tree and select the key:
HKLM\System\CurrentControlSet\Services\RpcSs
Rename the value "ImagePath" to "xImagePath"
Exit regedt32 and re-boot the machine. The machine may take longer than normal to start up and some functionality will no longer be available. Don’t worry as this will be re-enabled later.
Run your hex editor and open the file “from \windows\system32\rpcss.dll”
Search for the byte sequence "31 00 33 00 35" or the Unicode text "135".
Over-write this byte sequence to "30 00 30 00 30".
This changes the port from 135 to 000, which DCOM will not be able to open.
Save the file in the hex editor.
From the Start menu select Run…
Enter "regedt32" and click on OK.
Expand the tree and select the key:
HKLM\System\CurrentControlSet\Services\ RpcSs
Rename the value "xImagePath" to "ImagePath"
Exit regedt32 and re-boot the machine.
The DCOM server should no longer bind to port 135 and KFSensor should be listening to this port.