Brainware

Internet Solutions

Home  >  Knowledgebase

Columbus does not work after you install MS Windows XP Service Pack 2

Article ID:
BW840912340
Last Review:
30. 03. 2007

Find on this page


Symptoms

After you install Microsoft Windows XP Service Pack 2 (SP2), the Columbus Client is not allowed to connect to the server anymore and a Windows Firewall security alert occurs.

Cause

This problem occurs because with Windows XP Service Pack 2 (SP2), Windows Firewall is turned on by default. Because firewalls restrict communication between your computer and the Internet, Windows Firewall may block the ports that are used for file and printer sharing or applications that prefer an open connection. When these ports are blocked, Columbus clients cannot connect to a server and no connection can be established from the console to the Columbus clients.

Resolution

You will need to create an exception in the Firewall settings that allows Columbus to communicate through the Windows Firewall.

To add Columbus to the authorized applications, a user with local administrative rights can unblock Columbus, when the security alert window appears.

This can also be done by writing the following entries into the registry to remove the blocking of Columbus by the Firewall:

 

If the computer logs on to the domain, you have to add the entry in the Domain Profile

 

Register32 'HKey_Local_Machine' 'SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\AuthorizedApplications\List' '%_Windows%\COLUMBUS.EXE' '%_Windows%\COLUMBUS.EXE:*:Enabled:Columbus User and Service part' 'REG_SZ'

 

If the user does not log on to the domain, you have to add the entry in the Standard Profile

 

Register32 'HKey_Local_Machine' 'SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\AuthorizedApplications\List' '%_Windows%\COLUMBUS.EXE' '%_Windows%\COLUMBUS.EXE:*:Enabled:Columbus User and Service part' 'REG_SZ'

More Information

We recommend to enter both entries, regardless. These commands must be included in

  • An OSDeploy job, used when you stage your PC with Windows XP SP2
  • A Columbus package, which is installed on existing Windows PCs before SP2 is installed!

Beginning with Columbus 6.5 the default Columbus OSDeployment job and update package contain these commands already.

 

Applies to

Productgroups:

  • Enterprise

Operating Systems:

  • XP

Related Articles

Keywords:

SP2, XP