This is due to nsrauth and key. Chances are that either you must remove key from the server for NMC (not likely if this is new server) or from NMC. If you check daemon.raw on NMC host, you will most likely find there are messages indicating key mismatch.
Incase you had any server use the same hostname earlier chances are that you might have a old peer information. Try deleting the peer information and try again.
ble1
4 Operator
•
14.4K Posts
0
January 19th, 2016 04:00
This is due to nsrauth and key. Chances are that either you must remove key from the server for NMC (not likely if this is new server) or from NMC. If you check daemon.raw on NMC host, you will most likely find there are messages indicating key mismatch.
crazyrov
4 Operator
•
1.3K Posts
2
January 19th, 2016 07:00
Incase you had any server use the same hostname earlier chances are that you might have a old peer information. Try deleting the peer information and try again.
tsamuel0905
2 Intern
•
136 Posts
1
January 20th, 2016 06:00
In my case, after deleting the peer info in both server (Specific host name) and client and restarted the services. It worked fine..
ttobey
32 Posts
0
January 25th, 2016 11:00
Agree with the two above sounds like bad peer information.