Hi, I was able to create a DCOM client/server app. However, on the DCOM server side, I was able to invoke the methods on it from a remote DCOM client on a Windows 2000 machine which has yet to be patched with the recent DCOM RPC security patches from Microsoft. Machines that have been fully patched are cannot be reached, with the exception when I tried on a fully patched Windows 2000 Advanced Server machine. This means that I tried unsuccessfully on patched Win2K Pro and WinXP Pro machines

After doing some reading up on antivirus and security sites, it seems that these patches which are designed to block the DCOM RPC vulnerabilities exploited by the Blaster worm blocks the very same ports that are used by DCOM applications, eg 135 etc.

Is there a way to code my DCOM client/server application to utilize alternative ports? My organisation's Security Team insists that all machines are patched and requires any DCOM apps to use alternative ports. Does anyone know how do I go about doing this? Or if this is not possible, what are the best reasons to overcome the Security Team's concerns? ;)

Thanks & regards,
Kelvin