Re: Extremely slow boot and periodic freeze

Tech-Archive recommends: Fix windows errors by optimizing your registry

What KB? I used device manager gui and then used the view tab and selected
show hidden devices..... Is there another way?
--
Sean


"Les Connor" wrote:

Hopefully, you followed the kb exactly, using the command prompt and leaving
the command prompt window open while in devman. Otherwise, you'll not get
the intended results and the non-present devices won't be seen.

--
Les Connor [SBS-MVP]


____________________________
"Sean" <Sean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CDD2EA5F-6490-4B7D-AB6C-610E066C315A@xxxxxxxxxxxxxxxx
Yes,
There did not appear to be any duplicated or disabled NICS, there wer
several variation adding miniport, etc...
--
Sean


"Larry Struckmeyer [SBS-MVP]" wrote:

Did you set Device Manager to "show hidden devices"?

Device Manager - View - Show Hidden Devices

--
Larry
Please post the resolution to your
issue so that others may benefit.


"Sean" <Sean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:56E3F224-3D48-490C-B7C0-93237B6E966E@xxxxxxxxxxxxxxxx
Only one entry for bind order and that is TCP/IP

No ghosted NICs there are a lot of variation (miniport, etc) but
nothing
greyed or duplicated

NIC DNS is pointing to itself only...

So far I've tried everything I could think of, so keep the suggestions
comming as I'm sure someone will get it.

Thanks
--
Sean


"Larry Struckmeyer [SBS-MVP]" wrote:

For bind order, rclick the connetor in network properties, advanced,
advanced binding order.

For ghosted nics - device manager.

Note that another possibility for long boot times can be DNS. The DNS
setting on your nic should be to the nic itself. This is set by the
CEICW,
which will ask you for the ISP's dns and place those in the forwarders
tab
of your DNS properties.

--
Larry
Please post the resolution to your
issue so that others may benefit.


"Sean" <Sean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A8516C82-B6FE-4D0B-8D83-1AEF53FFAEF4@xxxxxxxxxxxxxxxx
HP says there are no problems with the NIC and driver, even though
the
update
imediately preceeded the problem. I only have the 1 NIC.

SBS best practices analyzer shows too many NICS but I have Trend
Micro
installed too.

Where do I find the bind order and check for ghosted nics?
--
Sean


"Cris Hanna [SBS MVP]" wrote:

Sounds like a call to HP is needed

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672329573/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Sean" <Sean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D48A88F6-0BC3-44EE-AAAA-BBAC1EF5F6AC@xxxxxxxxxxxxxxxx
NIC is embedded on the server motherboard, the softpak from HP
did
update
the
drivers for the NIC.

The first two freezes I was able to ping, this last time,
nothing.
--
Sean


"Lanwench [MVP - Exchange]" wrote:

Sean <Sean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have two issues that I'm stumped on, both started shortly
after
applying a softpak from HP for my server and HP seems to think
it's
a
Microsoft thing.......

I am running SBS 2003 Standard patched up to SP2 on an HP
ML350
G5
with 4GB RAM and a single NIC.

1st Issue: Boot times have gone from pretty quick (<5 mins) to
15+
minutes. The logs do not show activity during the boot
process,
and
so I don't know what processes are having trouble or timing
out......

The system pauses at the Windows Server 2003 splash screen for
about
5-7 minutes, and then spends about the same amount applying
setting
until I get the login window. The system never had this issue
before
the HP update, and I've since applied SP2 and a MS KB about
reserving
ports for DNS. SP2 temporarily shortened the boot time about 5
mins
but it's back to taking a long time.... Anybody got any ideas?

2nd Issue - Just started and has occured on 11/18, 11/26, and
12/5
where the server just seems to freeze, logging stops and I
can't
access the system from the console. The first two times I was
able
to
remote to another server and send the shutdown command and it
worked,
this last time nothing was working. Again, no log activity
preceeding
the symptom.

Hopefully somebody has a suggestion, as I'm stumped......

I'm suspecting the NIC. Have you tried changing it?

While it's frozen, can you even ping the server?











.

Relevant Pages

  • Re: Extremely slow boot and periodic freeze
    ... Les Connor [SBS-MVP] ... There did not appear to be any duplicated or disabled NICS, ... Note that another possibility for long boot times can be DNS. ... Windows Small Business Server 2008 Unleashed ...
    (microsoft.public.windows.server.sbs)
  • Re: Changing NIC causes IP address warning
    ... even if the advice offered is generous in nature. ... When you run the batch file the Device Manager will open. ... It is possible but you should not configure it on a server. ... One of the NICs failed, so I decided to replace both NIC 1 and NIC 2 ...
    (microsoft.public.win2000.networking)
  • Re: Changing NIC causes IP address warning
    ... even if the advice offered is generous in nature. ... When you run the batch file the Device Manager will open. ... It is possible but you should not configure it on a server. ... One of the NICs failed, so I decided to replace both NIC 1 and NIC 2 ...
    (microsoft.public.win2000.networking)
  • Re: Changing NIC causes IP address warning
    ... This group is made up of peer users, volunteers who offer their knowledge and advice without renumeration or benefit from anyone. ... When you run the batch file the Device Manager will open. ... If the network adapater is no longer physically in the server (i.e. ... One of the NICs failed, so I decided to replace both NIC 1 and NIC 2 ...
    (microsoft.public.win2000.networking)
  • Re: No internet access
    ... > Connectin to www.yahoo.com....Could not open a connection to host on port ... drivers in Device Manager to get the NIC working. ... > adapter, when I press the Properties button, I get the following message: ... Broken NICs are uncommon but they do happen. ...
    (microsoft.public.win2000.networking)