Slow Gigabit performance from a Windows 2003 server to a MS-DOS cl

We have a Windows 2003 server with Gigabit NIC and swithes, where we have a
diskshare to store and load our ghostimages.
We boot our client computers on a ms-dos diskette with Gigabit NIC driver
for the client Broadcom Gigabit NIC, version on the Ndis2 driver is 7.65.
The Ghost version is 8.2.

The readtransfer we get with this setup is 450 Mb/min in Ghost, and the
writetransfer is 600 Mb/min. We have also tried to copy a file from the
server to the clients harddrive with the same transferrate.

We beleive this is a bit on the slow side, and we wonder what transferrates
is to be expected in a setup like this?

Do you have any tips and tricks to tweak the performance in this setup?

Regards,
Dan

Hi Dan (or anyone who may know the answer!)

We have recently migrated our server from Windows 2000 to Windows 2003
and having problems as our MS-DOS networking client tcp/ip disks are
not connecting to the new 2003 servers (or windows xp pro machines) -
using the net use command.

Does anyone know what security settings that need to be lowered on the
Windows XP / Windows 2003 Server machines to allow the old MS-DOS
networking client to connect ?

Any help would be greatly appricated,
Cheers
Winston


Dan <(E-Mail Removed)> wrote in message news:<BF6C8DC9-63B7-40FC-ADD1-(E-Mail Removed)>...
> We have a Windows 2003 server with Gigabit NIC and swithes, where we have a
> diskshare to store and load our ghostimages.
> We boot our client computers on a ms-dos diskette with Gigabit NIC driver
> for the client Broadcom Gigabit NIC, version on the Ndis2 driver is 7.65.
> The Ghost version is 8.2.
>
> The readtransfer we get with this setup is 450 Mb/min in Ghost, and the
> writetransfer is 600 Mb/min. We have also tried to copy a file from the
> server to the clients harddrive with the same transferrate.
>
> We beleive this is a bit on the slow side, and we wonder what transferrates
> is to be expected in a setup like this?
>
> Do you have any tips and tricks to tweak the performance in this setup?
>
> Regards,
> Dan

It is impossible for MS-DOS clients to negotiate SMB-signing. To resolve
this situation, either temporarily disable the SMB-signing requirement in
the default domain policy, or upgrade the MS-DOS clients. Regarding the
SMB-signing requirement, the GPO setting below needs to be set to disabled,
if that is the chosen resolution.

Server: Digitally Sign Communication.

DOS, Win9x, and NT4.0 (pre-SP3) cannot communicate with a Server 2003 system
without reducing that security level.

811497 - Error Message When Windows 95 or Windows NT 4.0 Client Logs On to
Windows Server 2003 Domain:
http://support.microsoft.com/default...b;en-us;811497

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights