There could be numeorus reasons why your computer isn't starting as expected.
This issue goes back a long time, i have even had it once or twice. In most
cases it has to do with the network contacting a host or certain hosts, or
servers which do not exist anymore. More specifically, Network Neihborhood
(network browsing). If you previously had mapped network drives, which the
host of those drives do not exisit anymore, then windows will have delay
while trying to reconnect to those drives. If you have shares set to cache
data for offline browsing, then windows may also try to reconnect to those
shares to update the information.
Another problem could possibly be the DHCP service. If your network adapter
is set up obtain an ip address, that can also delay your startup sequence as
it tries to obtain an address from a remote host.
To resolve these issues, do it step by step. Change a setting, then reboot.
It's a lengthy process, but believe me, it pays off in the end. There's
nothing like disabling services or changing settings all at once to save the
problem solving time, than doing such a thing and creating more problems from
services you turned off, applications you've disabled/deleted, that ultimatly
had nothing to do with the first issue you were having; and not remembering
which services/programs you've modified, in order to resolve the post
problems.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
*******************************************************
Please note ALL the changes you are doing, as you just may HAVE to use these
changes to solve other problems you may encounter in the future. You may also
have to revert some or all changes in order to access computers on your local
network.
*******************************************************
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
That being said, first go into my computer click on tools in the top bar,
and click "disconnect network drive". If you don't have any network drives it
will come up with a message saying so. You don't have to reboot during this
time.
Next, go into your network connections in control panel. Right click the
adapters you use and select properties. In the general tab, under the
statement "This computer uses the following items" UNCHECK Client for
Microsoft Networks and File and printer Sharing for Microsoft Networks.
Reboot your computer and see if the problem persists. if so, read on leaving
the above settings changed for now.
Open up your network connections once again, click on your adapter and
choose properties. Scroll down to tcp/ip and click properties or double click
on it to bring up the property dialogue. Under the general tab, note if you
have it set to obtain settings automatically. This includes the DNS server
settings. If they are set to such, set the settings manually if your ISP
allows it. If you are directly connected to your modem, then you may not have
the option to do so. Usually you must pay extra money to have a static ip
address. If you are within a LAN, than you should be able to assign yourself
an ipaddress without much incident.
Reboot your computer and note the time it takes to get to your desktop.
By this time, I can almost guarantee that your problem is gone, if not the
boot process has dropped conciderably. However, there are always problems
which still may affect it. So if the problem STILL persists, read on.
Click on start, and then run. In the run dialogue, type in services.msc. You
will be presented with the services snapin. Find the Computer Browser entry,
double click on it to bring up it's properties and in the startup type,
choose "disabled".
reboot your computer and note the time it takes to get to the desktop.
If your problem still persists, open up the serivces.msc snap-in once more,
find the Server entry, open it's properties and in the startup options,
choose disabled.
Note that disabling this service will also cause the "Workstation" service
not to start as it is dependent on the Server service. Other dependencies
that will fail to start are the Alerter, Computer Browser, Messenger (not MSN
messenger or windows messenger), Net Logon (doesn't affect actually webpage
logins), and Remote Procedure Call Locator (which is disabled by default
anyways).
This is fine for the time being. After the Server service has been disabled,
you may as well disable it's dependencies, as they will try to start whether
or not it's parent service has been disabled. Doing so may shorten your boot
or logon process as well.
Now reboot your computer and note the time it takes to get to your desktop.
If your problem still persists, well that will require further inspection.
This post is long enough. So if you feel the need to contact me you may do so
by using my passport address.
