Good luck! In Clean Boot, the unnecessary services and startup items are disabled by msconfig. If it also works in Clean Boot, you may refer to the following link for how to narrow down and find out the root cause. Office Office Exchange Server. Not an IT pro? Windows Client. Sign in. United States English. Ask a question. Quick access.
Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows 7 Performance. Sign in to vote. Why is the peformance with mapped drives and libraries so poor in Windows 7? My laptop Intel dual core 2. Another drive letter takes at least 5 minutes to show up. Always the same drives behaving the same way. Sorry Alerts, I can't remember if this was resolved via troubleshooting, or if we just finally did a format and re-install of the problem system in order to get the system fully compliant with our ELITE-level Managed Service Best Practices baseline.
To continue this discussion, please ask a new question. Laplink Software, Inc. Neil Laplink. Get answers from your peers along with millions of IT pros who visit Spiceworks. Best Answer. Doug This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. View this "Best Answer" in the replies below ». Popular Topics in Windows 7. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need.
Learn More ». Ghost Chili. I do not have a roaming profile but we do use gpo login scripts. This happens whether network drives are mapped or not.
I've performed some boot tracing below which shows the long delay but now what? If your machine is joined to the domain it will always try to authenticate to the domain, read GPs, scripts, etc..
As your domain is not reachable, you have to wait till the search for the domain times out several times, till Windows falls back to local authentication via cached credentials. Depending on the structure of the non-domain network, it can take quite a while, till this occurs. I therefore never join laptops, which are used without domain connection frequently, to the domain - instead I put a "logon" script equivalent onto the desktop of the laptop, which can be run if connected to the domain, to connect to the domain and get drives mapped and settings applied, which you need to work in the domain.
That way you are much quicker up outside of the domain - and can use the domain resources if connected with one fingertip. We have experienced the same behavior in our environment.
Like WolfP stated, the machine is attempting to authenticate by reaching a domain controller. The timeout appears to be a long time and can be annoying.
We have noticed that if the machine doesn't have an active network connection, it will skip the check completely and immediately use cached credentials if there are any. We tell our laptop users that if they are performing a cold boot off-site to slide the switch to the off position before booting. As soon as they get to their desktop, they slide it back over and go about their merry way. Of course, they can't have an ethernet cable plugged in either for this to work.
The other solution, which is probably the best, is to setup Direct Access. Not only would that alleviate the slow offsite domain login times, but users would have access to their network resources! Unfortunately the problem presents itself even if i dont have any active network connections no ethernet cable and wifi switch disabled.
The machine still sits at the wait screen for the 50 seconds before the local credentials are used. It's a very perplexing problem.. The client is clearly looking for something from the DC for a long time Any help would be appreciated. Hi disk2 Unfortunately the problem presents itself even if i dont have any active network connections no ethernet cable and wifi switch disabled. And you don't have any other internal network adapters like e.
There is a virtual machine running XP on this client but it is not running at login or boot time. Yes but you have a virtual network adapter, to which this virtual machine can connect. That counts as a connected network adapter for the Domain logon.
If I were in your situation I'd create a local user with administrative rights otherwise it is complicated to access resources of the Domain user and logon as that user, if I were offsite.
Even Direct Access will not help you if you have no Internet Access from a particular location. I'm still trying to fix this problem and there are no real helpfull hints posted here. If you have a virtual network adapter try to set the NDISdevicetype to an endpoint device look e. None of these responses addresses the problem at all, english almost seems like a second language to some of theses commenters.
The firewall and other remote connections have nothing to do with it. The client is searching for a connection to the domain controller and it goes thru a full cycle of attempts before it brings up the login screen. I read that the GPO "Slow link detection" can be added to the logon policy which bypasses the normal login routine if the domain controller cannot be reached at a minimum speed.
If this policy is effective it should also detect if there is no connection to the domain controller and continue to local credentials with a nominal wait. Similar story here. One of my satellite office employees experiences the same thing when logging to his laptop from home. Sonicwall here too.
0コメント