|
|
 |
|
|
Pages: 1
Not sure where this goes.. Win 2000 Question.
(Click here to view the original thread with full colors/images)
Posted by: digitalfx
I just installed Windows 2000 pro. Everytime it boots up, it goes through all the boot up crap. Comes to the screen saying starting network connections and all that good stuff. Then that finally disappears, and it takes about 5 mins for the login screen to come up. This never did this before when I had it installed in the past. I just had to reinstall it because of problems. Is there kind of setting that could be making this do that?
Posted by: Canis Lupus
Hmmm, I assume you have a network card installed on that system? Most of the logon delays happen when the system is trying to communicate with/to the network card (this also happens in Win98).
Here are some things to check:- You don't have enough free RAM - you should have a minimum of 12 megabytes, but 32 is better (I am sure you have much more than this if you're running Win2K)
- Your hard disk is too slow - try optimizing it using Defrag. If you have some money burning a hole in your pocket, you might want to invest in a new, fast, huge hard disk.
- You don't have enough free disk space for a swapfile - you should have 20 to 40 megabytes of free disk space (including the size of the swapfile, Win386.swp)
- You may have too many fonts installed. If you can survive without all those fonts, try removing as much as you can to see if that makes a difference.
- Your network drivers (LAN, Dial-up Networking) take too long to load - try disabling them to see if it makes a difference.
Right after you boot up, try running START -> Windows Update and immediately download Service Pack 2, along with other critical and recommended updates for Win2K...
Post back on your progress ...
- Moving thread to Software forum
Posted by: Kdr Kane
Yeah. It's looking for other computers on the network. Mostly Microsoft stuff. It's looking for DNS, WINS and such. It takes 30 secs to 2 minutes to time out depending on the bindings.
This is how you get rid of it. Disable all of your network connections. You'll see the problem go away.
Now this is the correct way. Only use those protocols that you need. That means don't use Microsoft Networking, NetBEUI or IPX/SPX Netware connectivity unless you really need to.
Best bet is to get someone to fix it for you if you are not sure. Unfortunately, some software likes to enable these things when it's absolutely unnecessary.
The minimum configuration you will need is a dial-up (phone line) - or - a lan connection (if using cable). This connection will need to be configured for your ISP using TCP/IP.
Sorry to beat around the issue. But, you can really mess it up if you are not sure what you are doing.
Posted by: Rapmaster
if you have a cable modem or something and have your PC set to obtain an IP address automatically, it may take a while to communicate with the DHCP server (which are known to be slow with many cable providers). Best to set it up statically if possible,
|
|
|
|
|
