Reset Search
 

 

Article

KB13069 - 'Failed to connect or authenticate to remote server...' error is generated when trying to Push Config to a target PCS / PPS device

« Go Back

Information

 
Last Modified Date8/1/2015 9:54 PM
Synopsis
This article describes the issue of the Failed to connect or authenticate to remote server... error message being generated, when trying to Push Config to a target
Problem or Goal
After configuring certain target servers in the Push Config feature of the Infranet Controller,  the following error message is generated when attempting to push config:
Failed to connect or authenticate to remote server: https://<server name or IP address>/admin
Cause
Solution
Various issues can trigger this specific error message. However, the most common reason for this error message is a configuration issue with the Target's authentication realm name. The realm name is case-sensitive. To re-create the issue, perform the following procedure:
 
  1. Go to Maintenance > Push Config > Targets:
     
 
  • Add a new target (to add a new target, you need to follow the procedure provided in the PPS 2.2 Admin Guide). Notice the highlighted field:



    With the new target configured:

 
  • Execute a Push Config by going to Maintenance > Push Config > Push Configuration.
 
  • Click the Job <Job's date and time> results link to go to the Push Config Results page:



    Notice how the Push Config option failed:



    From the Admin Access log:


To resolve this issue, perform the following procedure:
 
  1. Modify the Target's Realm to use the correct case:



    This is how Auth. Realm looks like on the actual target Infranet Controller:

 
  • Push Config again and view the Results page:



    This time the Push Config should be successful:
     


    From the Admin Access Log:

Related Links
Attachment 1 
Created ByData Deployment

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255