Re: SBS NIC Cards give Code 1

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



How you replaced the NIC's, the physical card(s) may have been zapped.

Dan
"William Paris" <williamparis@xxxxxxxxxxxxxx> wrote in message
news:OYFV5P$jHHA.568@xxxxxxxxxxxxxxxxxxxxxxx
Merv, thanks for your answer. Yes, I've removed the offending nics from
the dev mgr and used updated drivers from the man. It failed with the
same errors "Cannot install device" "Cannot find file". I suspected
driver corruption so I used recovery mode to copy clean versions of the
drivers as well. Unfortunately, this had no results.

Regards,
William
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:%23ujC24%23jHHA.5048@xxxxxxxxxxxxxxxxxxxxxxx
Have you tried removing the device (NICs) in Device Manager; then run the
Add New Hardware wizard and reinstall the NIC(s) using drivers downloaded
from the manaufacturers web site (or from a recovery disk)?

--
Merv Porter [SBS-MVP]
============================

"William Paris" <williamparis@xxxxxxxxxxxxxx> wrote in message
news:eT%23eQl%23jHHA.5048@xxxxxxxxxxxxxxxxxxxxxxx
Hi everyone, long time SBS user but this is the first post I've done on
the
newsgroups.

I run an SBS 2003 server at home with a number of Non-Profit websites
for
free for charities that couldn't otherwise afford webspace. I provide
them
with mail, remote webwork place etc.

Here's my problem.

I've got workmen at my house converting my garage into an office.

They were messing with the electrics and powered up/down about 14-15
times
throughout the course of the day. By the end my UPS had no more juice
left
and my SBS server went down hard a number of time.

After one of the times it didn't come back up. It gave a boot error and
I
went into recovery console and performed a FIXBOOT. The server then
booted
fine.

However here were the following behaviours of the server:

1) I only had external connectivity
2) The internal (LAN) side card showed in the dev mgr but gave a Code 31
3) The only thing that showed in either card's properties was the
Windows
Client. Each time I tried to add tcp/ip the error msg given was "Cannot
find file"

I contacted MS Support who brilliantly called my back the next day - the
bummer is that I was out of the office the whole week this week and
wasn't
able to contact them back. I did via email ask if an "In-Place upgrade"
would sort my issue. The MS engineer responded with a 'most likely' so
Friday night after doing a full backup using NTbackup I did that.

Now my server's behaviour is much worse:

1) I have no connectivity at all
2) The NICs all give a Code 1 in the Dev Mgr and won't uninstall giving
an
error msg of "This device is required for boot"
3) Each time I reboot I get a "New hardware found" and then the cards
don't
install giving a "file not found"
4) A full restore with file over write did NOT get me back to the
previous
behaviour. I'm now stuck.

I'd really like some help getting this back without having to rebuild
the
server. I've got screenshots of all the above mentioned if this will
help.

Here's some actions I've performed:

1) Added devmgr_show_nonpresent_devices 1 into the environment to see if
the
nic cards had hidden devs that were preventing them from being
uninstalled
2) Manually uninstalled the devices via the registry and
system32\drivers
(they reappeared and gave the above error msg!)
3) Backed up my system state, my exchange, my www and iis config.

Can someone please help me!

Regards,
William Paris
williamparis@btinternet<REMOVEME>.com









.



Relevant Pages

  • Re: SBS NIC Cards give Code 1
    ... dev mgr and used updated drivers from the man. ... and my SBS server went down hard a number of time. ... The internal side card showed in the dev mgr but gave a Code 31 ... The NICs all give a Code 1 in the Dev Mgr and won't uninstall giving ...
    (microsoft.public.windows.server.sbs)
  • Re: BSoD on 2003 TS - varying error codes
    ... Another option is to completely wipe the server and reinstall from a known good image or from scratch. ... If the problem comes back then it is most likely faulty hardware. ... Possible Faulty Device Drivers ...
    (microsoft.public.windows.terminal_services)
  • Re: After manually undoing a recent MS Update, my server is a mess
    ... Keep in mind that I have seen OEM drivers up there so given that you've blown that image away, I can't say for certain that the 'critical' was 100% pushed by Microsoft. ... External USB is no replacement for local drives. ... LOL I show my naivety here when I say that I showed great diligence in my blind application of any MS suggested resolution to "Critical Errors" on my Small Business Server Monitor Report. ... When I got the first BSOD, I booted from the orginal CD and chose to only restore the System files. ...
    (microsoft.public.windows.server.sbs)
  • SUMMARY - Re: Jumpstart x86 - not accepting -B insall_media=
    ... from drivers not being included in the Solaris install media. ... Jumpstart environment is to modify the miniroot that is used during the ... Locate this directory on your jumpstart server and backup your ...
    (comp.unix.solaris)
  • [2.6.30.1] Significant latency playing video file from NFS4 share
    ... No significant other processes running on either the client or the ... latencytop on the server does not show any significant latencies. ... # CPUFreq processor drivers ... # Core Netfilter Configuration ...
    (Linux-Kernel)