Avocent DSR8020 KVM/IP - Network Connect Error - Solution - rtt.com

This error is commonly due to Java security or TLS settings but there is a second issue with forwarded ports that also causes it.

1. Java Security/TLS Settings issue:

This article has the solution to change them all in Linux automatically

2. Port Forwarding Issue if your Avocent DSR is behind NAT/private IP

One would assume if you can get to the interface successfully via port 80/443 that all would be well but it's not enough.

Actually a port scan shows the following ports are open on the DSR:

PORT     STATE SERVICE
80/tcp   open  http
443/tcp  open  https
2068/tcp open  advocentkvm
3211/tcp open  avsecuremgmt
3871/tcp open  avocent-adsap
8192/tcp open  sophos

You could forward all above ports but for normal functionality they are not required unless you are using the Avocent software I believe.

Forward these ports to your private IP of the Avocent DSR:

80,443,2068,8192

An example in iptables of how to forward the ports:

-s 192.168.5.4/32 #this is the only public IP that can access it (you can do away with this line if you want any remote IP to have access but for security this is recommended. I find the unit itself tends to crash from attacks/hacking attempts when left wide open to the public.

iptables -A PREROUTING -t nat -s 192.16.5.4/32 -d 103.2.5.2/32 -p tcp -m multiport --dports 80,443,2068,8192,3871,3211 -j DNAT --to 192.168.10.5

The same portforwarding can also be achieved with OpenSSH like this:

*Replace 192.168.10.5 with the NAT IP of your Avocent DSR unit

ssh -L 80:192.168.10.5:80 -L 443:192.168.10.5:443 -L 2068:192.168.10.5:2068 -L 8192:192.168.10.5:8192 user@remotehost.com

#bash script

remoteip=publicip