Name resolution errors in RSA Federated Identity Manager (FIM) 2.5
Originally Published: 2005-01-12
Last Modified: 2023-10-06
Article Number
Applies To
Microsoft Windows 2000 Server SP4
Issue
The administration server could not be contacted
Cause
Resolution
:localServer
set ADMIN_SERVER_HOST=fimserver.rsa.net
set PRIMARY_SERVER_HOST="fimserver.rsa.net"
set PRIMARY_SERVER_PORT="7001"
set PRIMARY_SERVER_SSL_PORT="7002"
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
set ADMIN_SERVER_PORT=7081
set ADMIN_SERVER_SSL_PORT=7082
set RSA_CSF_ADMIN_SERVER_OPTIONS=-Drsa.admin.server.host=fimserver.rsa.net
set RSA_CSF_ADMIN_SERVER_OPTIONS=%RSA_CSF_ADMIN_SERVER_OPTIONS% -Drsa.admin.server.port=%ADMIN_SERVER_PORT%
set RSA_CSF_ADMIN_SERVER_OPTIONS=%RSA_CSF_ADMIN_SERVER_OPTIONS% -Drsa.admin.server.ssl.port=%ADMIN_SERVER_SSL_PORT%
set RSA_CSF_PRIMARY_SERVER_OPTIONS=-Drsa.primary.server.host=fimserver.rsa.net
set RSA_CSF_PRIMARY_SERVER_OPTIONS=%RSA_CSF_PRIMARY_SERVER_OPTIONS% -Drsa.primary.server.host.port=7001
set RSA_CSF_PRIMARY_SERVER_OPTIONS=%RSA_CSF_PRIMARY_SERVER_OPTIONS% -Drsa.primary.server.host.ssl.port=7002
Might become:
:localServer
set ADMIN_SERVER_HOST=192.168.0.5
set PRIMARY_SERVER_HOST="192.168.0.5"
set PRIMARY_SERVER_PORT="7001"
set PRIMARY_SERVER_SSL_PORT="7002"
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
set ADMIN_SERVER_PORT=7081
set ADMIN_SERVER_SSL_PORT=7082
set RSA_CSF_ADMIN_SERVER_OPTIONS=-Drsa.admin.server.host=192.168.0.5
set RSA_CSF_ADMIN_SERVER_OPTIONS=%RSA_CSF_ADMIN_SERVER_OPTIONS% -Drsa.admin.server.port=%ADMIN_SERVER_PORT%
set RSA_CSF_ADMIN_SERVER_OPTIONS=%RSA_CSF_ADMIN_SERVER_OPTIONS% -Drsa.admin.server.ssl.port=%ADMIN_SERVER_SSL_PORT%
set RSA_CSF_PRIMARY_SERVER_OPTIONS=-Drsa.primary.server.host=192.168.0.5
set RSA_CSF_PRIMARY_SERVER_OPTIONS=%RSA_CSF_PRIMARY_SERVER_OPTIONS% -Drsa.primary.server.host.port=7001
set RSA_CSF_PRIMARY_SERVER_OPTIONS=%RSA_CSF_PRIMARY_SERVER_OPTIONS% -Drsa.primary.server.host.ssl.port=7002
NOTE: Make a backup copy of the file before editing it - if the modification allows the command to run successfully, then perform the following 2 steps:
1. Put the file back to using FQDNs
2. Identify the limitation/error in your name resolution
NOTE: RSA Security cannot assist with this task - contact your operating system or network vendor for assistance
Related Articles
Embedded identity router loses name resolution capability for RSA Authentication Manager Number of Views Error: 'The server has not found anything matching the Request-URI' in RSA Federated Identity Manager (FIM) Number of Views Checking name resolution and port connectivity for Web Tier instance on a supported Red Hat platform - RSA Authentication … Number of Views Error message "failed to preload on startup in Web application" in RSA Federated Identity Manager (FIM) 2.5 Number of Views Error: Error 'Socket Closed exception in RSA Federated Identity Manager (FIM) 2.5' Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?
