Search  
Thursday, November 20, 2008 ..:: Blog ::.. Register  Login
Location: BlogsSreejumon's Industrial World    
Posted by: Sreejumon Wednesday, June 06, 2007

If you are trying to connect to a remote OPC server from Windows XP SP2 and you are getting the message “DCOM was unable to communicate with the computer using any of the configured protocols”, then think about the additional security features and firewall configuration provided by Windows XP Service Pack 2.

Let’s consider the following points while configuring XP SP2 for OPC communication.

  • “Turn Off” firewall only for testing purpose (OPC client should work if firewall is “Off” and DCOM settings are correct). 
  • If firewall is “On”, proceed with the following steps.   
    • Goto “Exceptions” tab and select “Add Program”. Add all OPC Clients & Servers and OPCEnum.exe to the list.
    • Select “Add Port” and add TCP port 135 (which is required for DCOM)
  • Start DComcnfg.exe and select “COM Security” Tab.
  • Edit the limits for “Access Permission” and provide Local and Remote access for Anonymous Login.
  • Edit the limits for “Launch Permission” and provide full access to “Every one”

Hope this info will help to solve your OPC issues from Windows XP SP2 clients.

Permalink |  Trackback

Comments (2)  
Re: Windows XP SP2 and OPC via DCOM    By shijuprakasan on Friday, July 13, 2007
If its very usefull to programmers if you including basic code part.
Q. Can Firewall security change by on/off stage while running DCOM?

Re: Windows XP SP2 and OPC via DCOM    By Sreejumon on Friday, July 13, 2007
Hello Shiju, Most of the DCOM applications check the security aspects during initialization and try to function with available info. Hence you might have to restart the DCOM apps, after changing the firewall settings. Sometimes, windows restart itself might be required.

Copyright 2006-07 by Industrial-Automation-Software.com   Terms Of Use  Privacy Statement