Client Management Suite

 View Only
  • 1.  RAAD: Not able to connect to 'computername'. Initialization error

    Posted Jul 18, 2014 10:52 AM

    Hello, 
    I'm having trouble connecting RAAD (v2.1.24.0) with four desktop PC, that have XP SP3 installed. 

    The Message error is, "Not able to connect to 'computername'. Error de inicialización" (Initialization error).
    I've tried several things locally (Firewall, MS Updates, Running Services, .NetFramework, Uninstalling & Deleting Agent from DB, IP/DNS).

    This error also ocurres on Altiris Administrator machine, when trying to connect RAAD to this workstations.

    Any ideas or suggestions will be appreciated.

     

    Thanks,
    Ezequiel.-

     



  • 2.  RE: RAAD: Not able to connect to 'computername'. Initialization error

    Posted Jul 22, 2014 01:42 AM

    If you are login with admin id then may be try to create the new profile. This error may be occur because of corrupted profile.



  • 3.  RE: RAAD: Not able to connect to 'computername'. Initialization error

    Posted Jul 25, 2014 11:14 AM

    Thanks for the reply.

    The thing is, that we are in a domain, and every PC has Workstations -domain- Admins (me) and Local Administrator (also administrated by us) and all the workstations have that. I also checked permissions on that WKS, and there was no admin user that it wasn't allowed.

    Thanks a lot!

    Ezequiel



  • 4.  RE: RAAD: Not able to connect to 'computername'. Initialization error

    Posted Jul 31, 2014 08:16 AM

    If your is still persist then i suggest you to rename your profile and configure it again either try with other login id.



  • 5.  RE: RAAD: Not able to connect to 'computername'. Initialization error

    Posted Jul 31, 2014 09:07 AM

    Hi, thanks for the reply.

    Two different users and different PCs and the same behavior. It´s not a profile issue.-

    Regards!



  • 6.  RE: RAAD: Not able to connect to 'computername'. Initialization error

    Broadcom Employee
    Posted Aug 02, 2014 02:44 AM

    Maybe you can try this way to check logs and other things on managed endpoint