If a session cannot start correctly, check the error messages to fix the problem. Some common problems:
- Make sure the netconfd-pro program is running.
- Make sure the netconf-subsystem-pro program is properly installed.
- Check if the SSH configuration contains the portion for NETCONF.
- If the SSH configuration looks correct, then try restarting the SSH server to make sure that configuration file is the one being used.
- If the SSH server seems to be running correctly, then check if any firewall or other security mechanism is blocking TCP port 830. If so, either enable TCP port 830, or enable port 22 on the NETCONF server (by restarting the server), and include 'port=22' in the 'connect' command parameters.
- If no firewall or other security measure is blocking TCP port 830, try to establish a normal SSH session with the server.
- If a normal SSH session works correctly, then check the log messages on the NETCONF server for more information.
Connecting with plain SSH to make sure the OpenSSH server and netconfd-pro server and working properly:
ssh -s user@ipaddress netconf
Same test but using port 830:
ssh -s -p 830 user@ipaddress netconf
If these connect tests are working correctly, the server will send its <hello> message and wait for the client to send a <hello> message.
- Check the server log for access-denied messages or protocol not enabled messages.
- Make sure the netconfd-pro parameters that control access are set correctly. Some common parameters to check:
- allowed-user (not set)
- with-netconf = true
- with-restconf = true