we see very different connection speeds with logging in via ActiveDirectory vs User/pwd. For some reason ActiveDirectory ( conn.UseADLogon = true;) establishes a connection to the server in 2 seconds in Client.Connect() however it is taking 7 seconds for a VisualCron user/password combination to be established.
This seems like it should be even faster in the User/Pwd method than AD.

Version 9.9.8 Pro

we see very different connection speeds with logging in via ActiveDirectory vs User/pwd. For some reason ActiveDirectory ( conn.UseADLogon = true;) establishes a connection to the server in 2 seconds in Client.Connect() however it is taking 7 seconds for a VisualCron user/password combination to be established.
This seems like it should be even faster in the User/Pwd method than AD.

Version 9.9.8 Pro

Hi,

Can you reproduce this every time? And also, is this when logging in from a remote client to the server, or the client on the local server?

This is consistent over several months and from several different machines and remote client to server. These are all connections on the same LAN in the same building with ping speeds between the client and server of 15-30ms.

This is consistent over several months and from several different machines and remote client to server. These are all connections on the same LAN in the same building with ping speeds between the client and server of 15-30ms.

I'm having issues reproducing this myself. Can you create a small test environment in VM's or two unused machines where you install visualcron fresh on both, latest version, and see if you re able to reproduce it with fresh installations?

Yes repeatable and this is on a new laptop. Just got virtually identical results on a different server that is several hundred miles away. It could be AV or security related. Can you advise what speeds you see on your end for each authentication method over a local network?

Can you advise what speeds you see?
We have broadened this to more machines and it is 5 seconds or so on a LAN in same office and extending to 18 seconds to get to hosted machine.

conn.UseADLogon = true;
conn.EndpointIdentityType = EndpointIdentityT.UpnIdentity;
conn.PrincipalName = "first.last@company.com";

the connect method has been tried passing either true or false with same results
s = c.Connect(conn, true);