Hi zawarski,
Let me sumarize what do we get from this issue, in case other users come cross the similar.
From the log file, it shows nrservice works well and it's running under the "Default user", hence the ACL rules for the "Default user" gets applied, since no user logged in from nrclientcmd at the moment. With the ACL rules for "Default user" you defined, no one is allowed to ping from the Linux box to the target machine, though the connection has been created.
The basic idea is nrclientcmd works with nrservice to apply the ACL rules. Before sign in from nrclientcmd, nrservice is running as "Default user"; when you signed in (stay in the nrclientcmd and do not quit), nrservice is running as the the NR user you sign in; when you quit from nrclientcmd, nrservice changes back to "Default user".
If you want the nrservice running under a NR user when the box started, you may want to put the command line nrclientcmd -u username -p password -d domain in a script file and run it automatically.
Thanks, KevinZ - NeoRouter team
|