RSA Access Manger 6.1
Operating system supports IPV6
IPV6 must be disabled, as AxM does not currently support ipv6.
To disable ipv6, do the following:
1) Uncheck IPv6 in the the network interface setting
2) Add DisabledComponents setting in the
registry at HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters
3) comment out or alternately remove the ::1 localhost entry in the c:\windows\system32\drivers\etc\hosts file
In the event you continue to have issues running the aserver (or any of the AxM components) in debug mode and are recieving this error, the following workaround may be used:
1) In aserver/dispatcher/eserver.bats under the "init" section, include on the JVM_OSARGS line the following directive, -Djava.net.preferIPv4Stack=true.
Example:
:init
set JAVA_HOME=%AXM_HOME%\jre
set JVM_OSARGS=-server -Djava.net.preferIPv4Stack=true
set JVM_64=0
2) in hosts file, in addition to removing the v6 loopback, add the IPV4 ip address and fqdn of the host (it is not there by default), insuring it matches the primary hostname
Related Articles
Measuring RSA AA Web Services performance 27Number of Views RSA Software token application does not work on Android 10 26Number of Views Using PING to backup RSA Authentication Manager 8.2 and receiving error CIFS VFS: Error -32 sending data on socket to server 56Number of Views Missing sdconf.rec file causes SecurID to fail on Raptor Firewall 77Number of Views Error message "NIC Server is currently not available" displayed for RSA enVision 272Number of Views
Trending Articles
RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Upgrade Internal SHA-1 Certificates to SHA-256 in Authentication Manager Using rsautil RSA Authentication Manager 8.9 Setup and Configuration Guide RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows