Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Slow boot when disconnected from network
- Thread starter MSR63
- Start date
- Thread starter
- #3
My apologies but it is that simple.
When user is in the office and connect to network via hardwire or wireless - system boots up quick.
User goes home or to a remote location, boots up the system and it is slow to boot.
Uses same login/password/default domain - no errors reported.
When user is in the office and connect to network via hardwire or wireless - system boots up quick.
User goes home or to a remote location, boots up the system and it is slow to boot.
Uses same login/password/default domain - no errors reported.
If you are on a domain at the office network, and then try logging onto that domain when NOT on the office network, you are using cached credentials, and if there are network resources the laptop is trying to connect to, bootup will be slow. That's why I suggested logging on locally. Have you tried this?
Are you sure there are NO errors or warnings in the Event log (System or Application log)?
Are you sure there are NO errors or warnings in the Event log (System or Application log)?
drjohnbullas
Programmer
do thse laptops typically syncronise with network drives as a matter of course or download email into outlook from a network outlook server.... if these processes are run on bootup they will be tried and tried again until they timeout / fall over .... then allow other things to carry on...
Dr B
Dr B
guitarzan,
You are actually suggesting that a local account be created for the user, and to use that one instead. You should clarify that. You cannot simply switch the "Log on to:" from the domain to the local computer name using the same domain ID. I've tested this and it does not work.
MSR63,
There are a number of possibilities as to what's causing that. I would suggest that you create a separate local account as a test to see if the user is satisfied with that option. Since they are offline, there shouldn't be any real need to log in under the same domain user ID. You can tailor a local ID to the same preferences.
~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Einstein
[tab][navy]For posting policies, click [/navy]here.
You are actually suggesting that a local account be created for the user, and to use that one instead. You should clarify that. You cannot simply switch the "Log on to:" from the domain to the local computer name using the same domain ID. I've tested this and it does not work.
MSR63,
There are a number of possibilities as to what's causing that. I would suggest that you create a separate local account as a test to see if the user is satisfied with that option. Since they are offline, there shouldn't be any real need to log in under the same domain user ID. You can tailor a local ID to the same preferences.
~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Einstein
[tab][navy]For posting policies, click [/navy]here.
MSR63,
The reason your laptop boots so slowly off the network is it's trying to connect to mapped drives.
As cdogg suggested, try using a local user account without any domain credentials or mapped drives. It'll boot much faster.
As a test, if you have another computer available on your domain, try this:
1) Disconnect all mapped drives on the laptop (maybe do a print screen of each, or put the paths in a text file so you have them for later)
2) Start both computers.
3) On the laptop, map a drive to the second drive. Make sure you can open a folder and view files on the share.
4) Now shutdown both computers. Leave the second computer off, turn the laptop back on. Does it boot slowly?
5) After the laptop boots, turn on the second computer.
6) Shut down and restart the laptop. Notice any boot time differences?
The slowdown comes because a comoputer is trying to re-connect to drivrs that are mapped. If your not connected to your domain, or the drive is from a pc that isn't powered on, for example, then the booting pc will take time until it reaches a timeout period. This is why you should log onto the laptop locally when you don't/can't log into your work domain.
The reason your laptop boots so slowly off the network is it's trying to connect to mapped drives.
As cdogg suggested, try using a local user account without any domain credentials or mapped drives. It'll boot much faster.
As a test, if you have another computer available on your domain, try this:
1) Disconnect all mapped drives on the laptop (maybe do a print screen of each, or put the paths in a text file so you have them for later)
2) Start both computers.
3) On the laptop, map a drive to the second drive. Make sure you can open a folder and view files on the share.
4) Now shutdown both computers. Leave the second computer off, turn the laptop back on. Does it boot slowly?
5) After the laptop boots, turn on the second computer.
6) Shut down and restart the laptop. Notice any boot time differences?
The slowdown comes because a comoputer is trying to re-connect to drivrs that are mapped. If your not connected to your domain, or the drive is from a pc that isn't powered on, for example, then the booting pc will take time until it reaches a timeout period. This is why you should log onto the laptop locally when you don't/can't log into your work domain.
- Thread starter
- #8
Thanks everyone for your input
Having the user login as local user really isn't ideal.
I prefer users to log into their systems under the domain even if it is cached. These executives save too much work on their desktops already that if the system crashed we wouldn't be able to retrieve the data.
However - mapping may very well be the culprit. We have a nightmare infrastructor. This exec came from one domain ans still needs mapping to a drive there. Then he has our domain and is mapped to his home drive and share drive. And also has Citrix so he can access an application and yet another drive on a third domain.
The only thing is - that I have the same mappings and my laptop boots up at home much quicker than this execs does.
My system however is newer than his.
Having the user login as local user really isn't ideal.
I prefer users to log into their systems under the domain even if it is cached. These executives save too much work on their desktops already that if the system crashed we wouldn't be able to retrieve the data.
However - mapping may very well be the culprit. We have a nightmare infrastructor. This exec came from one domain ans still needs mapping to a drive there. Then he has our domain and is mapped to his home drive and share drive. And also has Citrix so he can access an application and yet another drive on a third domain.
The only thing is - that I have the same mappings and my laptop boots up at home much quicker than this execs does.
My system however is newer than his.
- Thread starter
- #10
That right there tells me the laptop has quite a history. Not only is your laptop newer, but it probably hasn't endured all that much in comparison. It's no surprise that yours boots much faster as a result.
Like I said before, there are likely a number of factors involved here such as a clogged registry, mapped drives (as others have mentioned), possible malware infections, etc. If Lawnboy's suggestion doesn't yield much, the next thing to try would be to reload Windows from scratch getting rid of excess baggage at bootup. Also while you're at it, see if you can upgrade the memory to at least 1GB. The combination of doing both can have very favorable results in overall performance.
~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Einstein
[tab][navy]For posting policies, click [/navy]here.
- Thread starter
- #12
I would love to reload it - but it took me over a year to get this bean counter to let me migrate to the new domain...
I know he wil not give it up for a reload unless it's really giving him problems. Like I said - when he is connected to the LAN hard wire and wireless - the laptop boots up just fine. We did upgrade the RAM to 1 GB months back.
I'll check with the user today to see if Lawnboy's suggestion helped any.
Thank you al for your assistance.
I know he wil not give it up for a reload unless it's really giving him problems. Like I said - when he is connected to the LAN hard wire and wireless - the laptop boots up just fine. We did upgrade the RAM to 1 GB months back.
I'll check with the user today to see if Lawnboy's suggestion helped any.
Thank you al for your assistance.
- Status
Similar threads