Problem description:

CallChange clients work without any problems when CallChange server is installed on Windows 2003 server with no service pack. After SP1 installation L1 client can not connect to the CallChange server; therefore clients of higher level also do not work.

Solution:

You must do these modifications to make CallChange to work again:

• run command prompt on CallChange server and type: dcomcnfg
• MMC console opens. Under Component Services - Computers rght click on My Computer and select Properties
• go to COM Security tab
• under Access Permissions press Edit limits, here should be set Allow for Local Access and Remote Access for ANONYMOUS LOGON, "Distributed COM Users" a Everyone users. If setting for ANONYMOUS LOGON is missing, add it.
• under Launch and Activation Permissions press Edit Defaults, here add "Distributed COM users" group and check Allow for all items (Local/Remote Launch, Local/Remote Activation).
• using "Active Directory Users and Computers" MMC add "Domain users" group into "Distributed COM users" group

Further information:

SP1 sets global security limits for DCOM clients accessing DCOM servers.

From CallChange version 4.6.03 DCOM will be replaced by XML RPC interface to avoid necesarity of security settings change.

Keywords:

CallChange, Windows 2003, SP1, L1 client

If there is something unclear, send us an email to development@datasys.cz.