Good Day.
I have a 2x Windows 2022 Server that is running in Azure that is Joined to the same Domain that is allocate in the Client office.
Universe is loaded on each of the Windows Server 2022 in Azure. All my test is running of the 2 servers.

I have a Domain user as well as a Local user. 

I am using Dynamic Connect

First Test

Server 1. use the Domain user via Dynamic Connect
After you enter the password until it displays for you which Account you want to login .it take 23 second to pop up. See screenshot below

With the local User it takes 1 second to pop up.

Then, I move to the second server that is on the same domain, authenticate to the same Domain. Use the same Domain user, Same test via Dynamic Connect.

The login there are 2 second to pop up. 

Did anyone have this issue before? Is the Issue with the Domain or Universe. If you can just point me into the correct directions to resolve this issue

Thank you

Good Day.
I have a 2x Windows 2022 Server that is running in Azure that is Joined to the same Domain that is allocate in the Client office.
Universe is loaded on each of the Windows Server 2022 in Azure. All my test is running of the 2 servers.

I have a Domain user as well as a Local user. 

I am using Dynamic Connect

First Test

Server 1. use the Domain user via Dynamic Connect
After you enter the password until it displays for you which Account you want to login .it take 23 second to pop up. See screenshot below

With the local User it takes 1 second to pop up.

Then, I move to the second server that is on the same domain, authenticate to the same Domain. Use the same Domain user, Same test via Dynamic Connect.

The login there are 2 second to pop up. 

Did anyone have this issue before? Is the Issue with the Domain or Universe. If you can just point me into the correct directions to resolve this issue

Thank you

Armand,

UniVerse just uses a standard Windows API to retrieve users from the domain. I suspect an issue with the domain lookup. A few things you can try:

• Use runas at a  DOS command prompt on each system for the local and domain users in a UniVerse account to run a UniVerse shell (use the account XDEMO for ease of use).
• Try  using a fully-qualified domain name (FQDN)
• Turn on the Windows telnet service - changing from port 23 to another port for the test (or stop UniVerse for the test) and see how long it now takes to connect. Don't forget to disable Windows telnet afterwards and make sure UniVerse is back on port 23 if it was changed.

Let us know how the performance varies - there are many things that can slow down a Windows cross-domain lookup. You may also find this article useful https://learn.microsoft.com/en-us/answers/questions/1682492/how-to-fix-the-very-slow-user-login-to-the-domain

Regatds

JJ

------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------

Do you have the login cache for telnet connections enabled on both servers? 

Good Day.
I have a 2x Windows 2022 Server that is running in Azure that is Joined to the same Domain that is allocate in the Client office.
Universe is loaded on each of the Windows Server 2022 in Azure. All my test is running of the 2 servers.

I have a Domain user as well as a Local user. 

I am using Dynamic Connect

First Test

Server 1. use the Domain user via Dynamic Connect
After you enter the password until it displays for you which Account you want to login .it take 23 second to pop up. See screenshot below

With the local User it takes 1 second to pop up.

Then, I move to the second server that is on the same domain, authenticate to the same Domain. Use the same Domain user, Same test via Dynamic Connect.

The login there are 2 second to pop up. 

Did anyone have this issue before? Is the Issue with the Domain or Universe. If you can just point me into the correct directions to resolve this issue

Thank you