Prev: SBS 2008 Migrate "a drive cannot be found"
Next: AllSBSUsers Group Policy - doesn't exist
From: thejamie on 24 Jan 2009 07:54
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
From: Joe on 24 Jan 2009 09:20
thejamie wrote:
> 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.

Have you tried a file transfer system, such as Filezilla, SCP or (ech)
FTP? It's going to take longer than CIFS/SMB, but fault tolerance always
comes at a price. A reliable protocol is just an unreliable one with
lots of patience.

--
Joe
From: thejamie on 24 Jan 2009 10:11
FTP... ok, but what is the SCP or (ech)?
I hadn't thought of FTP. I generally don't turn it on because I get so many
unsolicited attempts to break in.
--
Regards,
Jamie


"Joe" wrote:

> thejamie wrote:
> > 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.
>
> Have you tried a file transfer system, such as Filezilla, SCP or (ech)
> FTP? It's going to take longer than CIFS/SMB, but fault tolerance always
> comes at a price. A reliable protocol is just an unreliable one with
> lots of patience.
>
> --
> Joe
>
From: Russ (www.SBITS.Biz) on 24 Jan 2009 12:14
I move large files over my Wireless network often
Usually less than 2GB
But I've done 5GB with no issues.
But never seen this error before.
How big are these files? > 10GB?

I'd be thinking there is an issue with your SBS server.
is it a PC with SBS on it? or a Real Server with Plug in RAID cards?
(And RAID1 RAID5 or Other)

What kind of HD's do you have in the SBS server?
ATA? SATA? SCSI?
How Old is the Server?

You can use FileZilla, FTP Server
But if the SBS Server DIES because of I/O error I think the issue is The
server
and not the file transfer...

If you do think this is wifi related
when you use a 50' Cable do you get these errors?

If not, Is your Wifi a N type? or B or G?

Russ

--
Russell Grover - SBITS.Biz
Microsoft Gold Certified Partner
Microsoft Certified Small Business Specialist
World Wide 24hr SBS Remote Support - http://www.SBITS.Biz


"thejamie" <thejamie(a)discussions.microsoft.com> wrote in message
news:AD1ECEB8-39BC-4087-B5EF-B393C2EA4A8F(a)microsoft.com...
> FTP... ok, but what is the SCP or (ech)?
> I hadn't thought of FTP. I generally don't turn it on because I get so
> many
> unsolicited attempts to break in.
> --
> Regards,
> Jamie
>
>
> "Joe" wrote:
>
>> thejamie wrote:
>> > 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.
>>
>> Have you tried a file transfer system, such as Filezilla, SCP or (ech)
>> FTP? It's going to take longer than CIFS/SMB, but fault tolerance always
>> comes at a price. A reliable protocol is just an unreliable one with
>> lots of patience.
>>
>> --
>> Joe
>>


From: Les Connor [SBS MVP] on 24 Jan 2009 12:54
Event logs, client and server please?

--
-----------------------------------------------
Les Connor [SBS MVP]

"thejamie" <thejamie(a)discussions.microsoft.com> wrote in message
news:841863AB-807A-48CF-A69E-4C2900AA7647(a)microsoft.com...
> 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

 |  Next  |  Last
Pages: 1 2 3 4 5
Prev: SBS 2008 Migrate "a drive cannot be found"
Next: AllSBSUsers Group Policy - doesn't exist