Domain login very slow 10+ minutes

Question

Is there a way to include the credential required by AWS S3 in Cocoapods specification?

currently my Podfile looks like this: 'pod 'mylibrary', :git => 'https://s3.amazonaws.com/myBucketThatHostsGitRepo' and it works if the bucket has public access. However, once the repo is made private (i.e. requires authentication), mylibrary cannot be downloaded.

I've come across this post: Cocoapods Private Spec Repo over HTTP/S3 But a bit of detail would help as I poke around with .gitconfig and it does not help.

Solution 1

We had a similar issue where workstations were taking about 10 minutes to log in. However, if the network cable was unplugged and the PC rebooted then they logged in right away.

We found that the slow logons were caused by a printer driver that was being installed but which required user input, which obviously couldn't be provided because the user was not logged in yet.

Try turning on Verbose Welcome Screen in GPO. This might show you where the PC is getting stuck.

Solution 2

You may want to test the "BufferPolicyReads" registry setting. This setting is enabled by default in Windows 7, but needs to be specified for Windows XP.

http://support.microsoft.com/kb/319440

Key: HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

Value: BufferPolicyReads
Type: DWORD
Value: 1

Solution 3

To add to what others have posted, I've seen this sometimes when the client machines DNS are set to something other than an AD server (or internal DNS server), this is especially true if your local domain is using a .com or .net or something that is in the Public DNS domain.

Comments

[Harrys Kavan]

Do you guys have an ntp server, and sync all your clocks with this ntp-server? I nearly lost my mind because we didn't have an ntp Server and all our AD Maschines where slightly out of sync and this causes insane network traffic and really long authentification times.

[Striker_84]

although you've mentioned DNS, please verify that your clients are pointing to your Windows server’s DNS and WINS services. You could also try to configure DNS entries on a local system. see link for details.

[jscott]

Mark Russinovich has some great links for troubleshooting slow logons. You may consider starting there to gather some more information about your specific problem.

[Str82DHeaD]

I have two questions about the problem : Are you sure that you don't download the entire user directory at login (files, documents, music, etc.) from the domain controller, and not just the configuration files? Is the logout slow too?

[TomTom]

CHeck Network traffic. Roaming porifle + Gigabytes of data = slow logon.

[Daryl Liney]

Str82DHeaD in answer to you question, no. None of our users are on roaming profiles so all files are stored on the local machine, log out is not slow at all, takes around 30 secs

[OrganizedChaos]

@MDMarra so.... I went to lookup your answer to prove you wrong, because in the past this was widly considered best practice. I see that now, it's recommended to go with a public DNS name and use the subdomain like you mentioned because it's unique. If your company were to merge, you wont have any issues with merging two AD's with the same name etc...

[I say Reinstate Monica]

As a slight variation to this solution, I solved the same problem the OP had by removing a GP Preference item that was attempting to install a printer that no longer existed (rather than requiring user input).

[John K. N.]

Would help if you supplied a reason as to why he should run your script.

[Vitas]

but run these commands on the server or client?

[Vitas]

this does not seem to do anything! I enabled this in gpedit.msc but logout and login screen look the same on server w2k16!