|
-
Mar 17th, 2004, 09:12 AM
#1
Thread Starter
Hyperactive Member
Slow log in in Windows XP
When I try to log in in Windows XP (in a domain), logging in will take about 5 (!!!) minutes. The problem doesn't appear when I pull out the network cable. It seems the problem occurs when connected to a network.
Does someone of you have the same problem? What could it be?
Thanx in advance
-
Mar 17th, 2004, 09:48 AM
#2
Hyperactive Member
Just a thought
Could your PC be trying to access something on the net on startup, e.g. mapping to a network drive?
"The wise man doesn't know all the answers, but he knows where to find them."
VBForums is one place, but for the really important stuff ... here's a clue 1Tim3:15
-
Mar 17th, 2004, 01:49 PM
#3
SQL Server, Norton Antivirus, etc. Stuff like this can slow the startup quite a lot.
Also, get a utility called bootvis.exe, analyze your startup. Someone on this forum would have it, most likely.
-
Mar 17th, 2004, 02:26 PM
#4
Frenzied Member
bootvis is free from microsoft
although i don't think it's really all that useful
-
Mar 17th, 2004, 02:34 PM
#5
Originally posted by dis1411
bootvis is free from microsoft
although i don't think it's really all that useful
Saved me a minute.
And it's not available on the MS site anymore. Someone will have to upload it here.
-
Mar 18th, 2004, 01:17 AM
#6
Thread Starter
Hyperactive Member
-
Mar 18th, 2004, 04:14 AM
#7
Retired VBF Adm1nistrator
Check your DNS settings in windows.
Microsoft MVP : Visual Developer - Visual Basic [2004-2005]
-
Mar 18th, 2004, 04:25 AM
#8
Thread Starter
Hyperactive Member
I also thought about that, but with Win2K I don't have the problem. Is MS fixing a bug, or frustrating the user?
-
Mar 18th, 2004, 04:38 AM
#9
Retired VBF Adm1nistrator
Well WindowsXP is different in some respects to Windows 2000.
I would try checking your TCP/IP settings.
Try making your Primary DNS server = the ip address of your Primary Domain Controller
Microsoft MVP : Visual Developer - Visual Basic [2004-2005]
-
Mar 18th, 2004, 04:50 AM
#10
Thread Starter
Hyperactive Member
Ok, I know that, but I don't have time for now to set up the DNS on my server. I already thought it was DNS, but I was wondering if other people did have the same 'problem'.
-
Mar 18th, 2004, 04:52 AM
#11
Retired VBF Adm1nistrator
If its a Win2k or Win2k3 server, chances are its already got DNS installed and configured (somewhat anyway).
I've had that problem with logging WinXP machines onto a Win2k3 domain.
After manually setting the dns settings it worked like a dream.
Also, do you have a roaming or mandatory user profile ?
Microsoft MVP : Visual Developer - Visual Basic [2004-2005]
-
Mar 18th, 2004, 05:03 AM
#12
Thread Starter
Hyperactive Member
Ah, is the clue in manually reconfiguring win2ksrv dns. I knew DNS was configured when I installed the server. But Win2k didn't have a problem with that. WinXP on the other hand does.
I'm using mandatory profiles. So my solution for now was putting out the network cable, log in, wait for WinXP to log in, and put my network cable back.
It worked about 20 times faster than let WinXP search for DNS.
-
Mar 19th, 2004, 01:11 AM
#13
Thread Starter
Hyperactive Member
My collegue also has it when hanging two computers in a workgroup (not connected to the internet). When pushing off the switch, all works like speedy gonzalez. When he put the switch back on and tries to log in, it works like hell...
-
Mar 19th, 2004, 02:31 PM
#14
Lot of frogs in this thread, btw...
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|