I am wondering what exactly this means? Basically it happens hundreds of time and the clients get disconnected and so they have to reconnect. According to JTAC it is because also in the log at the end of all of these 2745's is "Got disconnect reason NC_CONFIG_CHANGED". Which according to them is because the Network Connect configuration changed so the client must disconnect and reconnect to pick up the changes.
There is two admins on the 6500's we have and neither of have made a change but yet it says there is a change? Any ideas?
I am also attaching the debug log.
6500's running 7.1R4
Are you getting one user drop at a time, or all NC users? Is it possible the end user's machine is changing it's network configuration? (DHCP, ect..??)
Is the client's IP address changing? If it is you can enable Roaming on the Role (Users > Roles > RoleName > General > Session Options) to allow the connection to continue across source IP changes.
@rswinter wrote:Are you getting one user drop at a time, or all NC users? Is it possible the end user's machine is changing it's network configuration? (DHCP, ect..??)
According to JTAC it is in the CORE with this error howver we haven't made core changes.
@MattS wrote:Is the client's IP address changing? If it is you can enable Roaming on the Role (Users > Roles > RoleName > General > Session Options) to allow the connection to continue across source IP changes.
Roaming is enabled however the users ip is not changing.