Personal tools
You are here: Home → support → WiKID Documentation Center → Troubleshooting FAQ → What ports are needed for WiKID? How do I know if the listener running on the server?

What ports are needed for WiKID? How do I know if the listener running on the server?

Up to Table of Contents

This FAQ applies to: WiKID Strong Authentication Server Enterprise Edition, WiKID Strong Authentication Server Community Edition

The token client uses port 80. Because we use asymmetric encryption, there is no need for SSL. If you are behind a proxy, your token client won't connect to the WiKID server. Proxy support is coming in version 3.0. The WiKIDAdmin web interface uses port 443.

Network clients use a variety of ports. Radius is typically 1812, LDAP 389, wAuth is 8388 and TACACS+ is 49. To see if the listener is running on the WiKID server, enter the following command at the WiKID server terminal:

# netstat -anp | grep 8388
Just change the port to the service you are looking to check. The output for wAuth looks like this: 
netstat -anp | grep 8388
tcp        0      0 0.0.0.0:8388            0.0.0.0:*               LISTEN      11955/java          
tcp        0      0 127.0.0.1:8388          127.0.0.1:34817         ESTABLISHED 11955/java          
tcp        0      0 127.0.0.1:8388          127.0.0.1:34826         ESTABLISHED 11955/java          
tcp        0      0 127.0.0.1:34826         127.0.0.1:8388          ESTABLISHED 12044/java          
tcp        0      0 127.0.0.1:34817         127.0.0.1:8388          ESTABLISHED 12066/java