Hi all.
i'm kinda new here, so bear with me
I have a problem, that i'm hoping someone can help me with.
i have a windows Vista x64 SP2 machine, which I use both at work and at home.
At work there is no problem, the laptop boots, logs in, and is active very fast (or at least fast enough
), but wwhen I get home, the logon process takes approx 2 mins.
My logic tells me, that since it more or less freezes at the "welcome" screen, the 2 mins is some sort of timeout, before it finds out that the DC cannot be found.
or maybe it is the time it takes to find out that the network drives I have mapped cannot be located. (I have tried turning of the Wifi before booting, but it didn't help)
I'm very use to only setting the machine to hibernate, which works fine, but once in a while I like to turn it off completely.
my question is simply put, this:
1) Is there some way I can set the timeout to a lower value so that It doesn't look for 2 full minutes?
2) can I tamper with the cached logins, and will this help?
3) can I create a logon script that simply checks if the DC can be contacted, and if not, then simply remove the mapped drives, so it doesn't try to remap them at logon?
I know the last question is not really placed in the right forum, but any help would be very appreciated.
i'm kinda new here, so bear with me

I have a problem, that i'm hoping someone can help me with.
i have a windows Vista x64 SP2 machine, which I use both at work and at home.
At work there is no problem, the laptop boots, logs in, and is active very fast (or at least fast enough

My logic tells me, that since it more or less freezes at the "welcome" screen, the 2 mins is some sort of timeout, before it finds out that the DC cannot be found.
or maybe it is the time it takes to find out that the network drives I have mapped cannot be located. (I have tried turning of the Wifi before booting, but it didn't help)
I'm very use to only setting the machine to hibernate, which works fine, but once in a while I like to turn it off completely.
my question is simply put, this:
1) Is there some way I can set the timeout to a lower value so that It doesn't look for 2 full minutes?
2) can I tamper with the cached logins, and will this help?
3) can I create a logon script that simply checks if the DC can be contacted, and if not, then simply remove the mapped drives, so it doesn't try to remap them at logon?
I know the last question is not really placed in the right forum, but any help would be very appreciated.