Prev: Initialize Disk
Next: ntvdm hardware error running 16 bits DOS app on 2003 server
From: v-jasont on 29 Dec 2005 02:09
Hi Scott,

If possible, I suggest you uninstall the SP1 to identify the effect. In
addition, you may review the following article to troubleshoot the startup
issue.

325375 How to troubleshoot startup problems in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;325375

Hope the information helps.

Happy New Year!

Best Regards,

Jason Tan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.




--------------------
| From: "Scott Micale" <hrm_admin(a)news.postalias>
| References: <#adwjY7CGHA.2040(a)TK2MSFTNGP14.phx.gbl>
<33388D60-1190-44B6-AC25-899C6133D8AD(a)microsoft.com>
<evJ#eN8CGHA.2956(a)TK2MSFTNGP14.phx.gbl>
<3F2918F2-E695-4497-89F8-B6758D703381(a)microsoft.com>
| Subject: Re: Windows 2003 boot issue "Preparing Network Connection"
| Date: Wed, 28 Dec 2005 12:38:51 -0500
| Lines: 91
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
| X-RFC2646: Format=Flowed; Original
| Message-ID: <#36XcY9CGHA.2320(a)TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.windows.server.general
| NNTP-Posting-Host: wireless.speedynet.net 216.29.29.21
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.general:84666
| X-Tomcat-NG: microsoft.public.windows.server.general
|
| Ok, I will have to try shutting down and rebooting tonight before I
leave.
| I can't take this down now during production time.
|
| I will post a reply later tonight or first thing in the morning.
|
| Thanks again!
|
|
| "Transam388" <Transam388(a)discussions.microsoft.com> wrote in message
| news:3F2918F2-E695-4497-89F8-B6758D703381(a)microsoft.com...
| > Just for grins, try disabling the NIC on one of the systems and then
| > rebooting. See if the system then comes up quickly. See if we can
narrow
| > your search. Do the servers have drives mapped to other systems? One
| > other
| > thing I have seen that if you go to control panel, system, Computer
Name,
| > Change, More, make sure your AD domain is correctly input in the
Primary
| > DNS
| > suffix of this computer. I have seen this cause delays if it is empty
and
| > or
| > wrong.
| >
| > "Scott Micale" wrote:
| >
| >> I am pretty sure it booted fine before the SP update. They systems
are
| >> all
| >> different, but setup similar. I don't think it is a DNS or WINS issue.
| >>
| >>
| >> "Transam388" <Transam388(a)discussions.microsoft.com> wrote in message
| >> news:33388D60-1190-44B6-AC25-899C6133D8AD(a)microsoft.com...
| >> > Did it boot quickly before the SP was installed? Are all the
systems
| >> > the
| >> > same type? What may have occured is if they are the same type of
| >> > systems
| >> > a
| >> > driver update occured to one of your network components and is
making
| >> > this
| >> > issue. I have had one server in the past that had a delay at the
| >> > "Preparing
| >> > Network Connections" but it was not 10 minutes. You may want to un
| >> > install
| >> > the SP on one of the systems and see if the time gets better. If so
| >> > then
| >> > you
| >> > might want to do the Customized version of Windows update and select
| >> > single
| >> > updates and reboot after each one. When you find the one that
causes
| >> > the
| >> > slow reboot then on the others just deselect that patch. Long
process
| >> > but
| >> > it
| >> > might find the one.? You may also want to see if all the systems
have
| >> > any
| >> > drives mapped to a system that either no longer exists or has had
it's
| >> > IP
| >> > changed and DNS / WINS still has the old IP.
| >> >
| >> > "Scott Micale" wrote:
| >> >
| >> >> I have 7 Windows 2003 servers and I am noticing on all of them when
I
| >> >> go
| >> >> to
| >> >> reboot them that theytake an extremely long time to reboot. They
are
| >> >> all
| >> >> running the latest Service Packs and updates and I am wondering if a
| >> >> certain
| >> >> update of late has caused this problem. Basically what I am seeing
is
| >> >> when
| >> >> the system reboots when it gets to the screen saying "Preparing
| >> >> Network"
| >> >> or
| >> >> "Preparing Network Connection", I forget exactly what it says they
| >> >> systems
| >> >> sit there for about 10-15 minutes before anyone can log into them
or
| >> >> get
| >> >> to
| >> >> their shares on the network. Once it then gets to the Press
| >> >> Ctrl+Alt+Del
| >> >> screen I am fine. Is anyone else seeing this problem?
| >> >>
| >> >> Thanks
| >> >>
| >> >> -Scott Micale
| >> >>
| >> >>
| >> >>
| >>
| >>
| >>
|
|
|

From: Preetam on 29 Dec 2005 08:01
I doubt but I would start with , if there is APC service

If yes please refer this KB:905716

First  |  Prev  | 
Pages: 1 2
Prev: Initialize Disk
Next: ntvdm hardware error running 16 bits DOS app on 2003 server