Logon takes very long when connected to foreign network using Domain login

Yanıt Logon takes very long when connected to foreign network using Domain login

  • 26 Nisan 2012 Perşembe 11:05
     
     

    Hello Technet,

    I have a question regarding the logon to a domain integrated computer when connected to a foreign network (for example: public wifi at a airport).
    It takes pretty long till the desktop appears, like 2 - 3 minutes. Is this behaviour by design or can you do something about it?

    Client OS is Windows 7 x64 Bit, no cached profiles are  being used.

    Thanks for reading!
    regards

    Martin

Tüm Yanıtlar

  • 27 Nisan 2012 Cuma 02:37
     
     

    Hi Martin,

    is the logon performance better when you are not connected to the internet? and is it faster if you are in your office connected directly to the domain network?

    Logon performance for a domain joined PC can be hampered by multiple factors such as group policy processing, logon scripts and other security settings or software management policies. You will need to troubleshoot this issue with your domain administrators.

    Regards, Richard

  • 27 Nisan 2012 Cuma 07:58
     
     Yanıt

    Hi,

    Since the public Wi-Fi network transmission speed is not as fast as LAN, and other factors such as domain group policy and logon scripts may cause this issue.

    Authenticate, download policy, both need to communicate with DC. So I suggest you to enable log on with local cache. Another suggestion is to disable some application which you don’t need to start when login.

    Taking 2-3 minutes on domain login is a little longer but it is acceptable in view of your network environment and domain login.


    Ivan-Liu

    TechNet Community Support


  • 27 Nisan 2012 Cuma 09:50
     
     

    Logon performance is always slow when I am trying to authenticate as a domain user while I am connected to a network that has no domain access (public wifi or other foreign networks)

    No logon scripts are running (because they are on the net). No special security settings and software deployment management settings are applied. Group policy setting is also not an option, because the client has no access to the net.


  • 27 Nisan 2012 Cuma 11:17
     
     

    Okay, if you are not using vpn or direct access then the issue is a default timeout after waiting to discover something. The best tool to use is xperf, you can also try USERENV logging, or search for a blog post by Chad Duffy regarding netsh logging

  • 30 Nisan 2012 Pazartesi 01:43
     
     

    Hi,

    It takes more time when domian users try connectting to the network which has no domain access, public Wi-Fi needs time to build the network link additional.


    Ivan-Liu

    TechNet Community Support