Re: Annoying Crashes on SBS
- From: "Cliff Galiher" <cgaliher@xxxxxxxxx>
- Date: Sat, 24 Jan 2009 16:11:38 -0700
First, let me be *very* clear on this. SMB, as a protocol, knows when things are getting dropped. A good RAID card with appropriate drivers (you are running RAID on your server, right?) knows when there is a hard disk error. If your system is in decent running order, SBS *WILL NOT* confuse missing data from a copy as a bad hard drive.
If the event logs are actually showing you hard drive related errors then you *have* hard drive related errors and should address them.
But for us to help you, we'd need to know a few things:
First and foremost, what do you mean SBS shuts down the domain!? That simply doesn't make sense. If the SBS server is shutting down and it is the only DC then sure, you have no domain access...but it is the SERVER that shut down. "The Domain" is a nebulous things that doesn't just shut down. If SBS is staying up, but Active Directory is somehow becoming unavailable then you have *OTHER* problems. Again, as above, you need to find out why and address them. But you need to be VERY CLEAR about what is happening. "shutting down the domain" unfortunately is just not detailed enough, and I don't want to guess what you meant by that.
Secondly, what event logs have you seen that make you think SBS is deciding it is a hard drive issue. Post the actual errors and events you are seeing. We will be able to better help you interpret those errors and events than we can guess what is happening based on the interpretation you've already decided to make. You very well may have interpreted the errors correctly...I'm not second guessing that, just saying that the conclusion you drew may be off. But I'd rather not guess...and see the evidence for myself.
Good luck,
-Cliff
"thejamie" <thejamie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:841863AB-807A-48CF-A69E-4C2900AA7647@xxxxxxxxxxxxxxxx
I connect to the domain via a wireless access point - one job is to develop
databases and frequently I move a large backup file from a laptop to the
domain. Unfortunately, the connection is not always what it should or could
be and the SBS DC interprets the missing packets as a bad sector on the hard
disk, shuts down the domain... wow, so annoying! The simple solution is to
never try to move a large file from the access point into the domain but that
is not a practical solution for this infrastructure.
Which is this. There is a WAP just over 50 feet away from my desk. It is
authenticated through IAS and SBS sees it like a machine on the network. The
IAS keeps just anyone from using it - anyone can login if they know the WAP
password, but it won't get them authenticated. That part is fine.
Since moving files conventionally seems to fail frequently I try to use the
ESE.DLL in conjunction with the ESEUTIL.EXE that comes with Exchange and then
pipe it:
eseutil /y "G:\BIGFILE" /d "\\dcserver\Users\myspace\BIGFILE.bak"
Neither this nor the file transfer method works. The minute the WAP gets
fuzzy and some packets are lost, SBS says - aha, I lost the file - must be my
hard disk so I am going to shut down and kaboom, down comes the domain.
What can I do to fix the server so that it doesn't interpret the file
transfers as a bad disk?
Yep, I have been doing this for about a year - I go back, run the chkdsk for
bad sectors on the mirror - nothing - the disks are fine. It is essentially
something in the makeup of the way SBS is interpreting the file as it comes
across from the WAP.
If I didn't think it would raise hackles all over the place, I would call it
a bug. Think of a disgruntled employee on a WAP and you'll get the picture.
--
Regards,
Jamie
.
- References:
- Annoying Crashes on SBS
- From: thejamie
- Annoying Crashes on SBS
- Prev by Date: Re: Virtualized SBS / WS /TS
- Next by Date: Re: A case for windows firewall
- Previous by thread: Re: Annoying Crashes on SBS
- Next by thread: CHild domain under sbs 2003 server standard
- Index(es):
Relevant Pages
|
