Server Lockup Copying File to Network

I ran into a very interesting problem with a standard Windows 2003 server
and several files. I have an installation area that I share out on my small
network. With just 1 user connected, I noticed that the server would lock
up (no blue screen, just keyboard/mouse lockup and no ping response).

I traced it to when I was trying to do an install of various utilities from
the a network share on this machine. So, I copied the small share, and it
locked up. Tracing it further, I noticed that it would ALWAYS lock up when
copying this single file (189K in size). It didn't matter what machine I
copied to, or who initiated the copy, the machine would always lock up.

Fearing a hard drive problem, I tried copying the file (and then the
directory) to another drive on this machine - and it worked fine! No lock
up.

Lastly, I compressed the directory into a compressed folder and did a copy
to a remote machine, and it worked fine.

It seems as though a specific bit pattern sent out over the network driver
causes the machine to lock up. Question is ... how do I fix it? I'm
running TCP/IP only on this machine over a generic Intel 10/100 NIC (using
the Microsoft drivers supplied with the OS).

Any ideas on how to get this fixed? There are other files/directories that
exhibit this problem, which makes it hard for me to use this machine as a
file share on my small network.

--
Doug Thews
Director, Customer Solutions
D&D Consulting Services
----------------
Visit my Tech Blog at:
http://www.ddconsult.com/blogs/illuminati/

Windows 2003 requires smb signing which can cause problems depending on the
client operating system. I would disable it at least temporally via Local
Security Policy going to security settings/local policies/security options
and for the option Microsoft network server:digitally sign
communications(always) set it to DISABLED. If that does not help after a
reboot I would install the latest drivers from Intel for your network card
and if that does not help try another network card. Also if the network
adapter properties is set to auto for network speed it is worth a try to set
it to 100. --- Steve


"Doug Thews" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I ran into a very interesting problem with a standard Windows 2003 server
>and several files. I have an installation area that I share out on my
>small network. With just 1 user connected, I noticed that the server would
>lock up (no blue screen, just keyboard/mouse lockup and no ping response).
>
> I traced it to when I was trying to do an install of various utilities
> from the a network share on this machine. So, I copied the small share,
> and it locked up. Tracing it further, I noticed that it would ALWAYS lock
> up when copying this single file (189K in size). It didn't matter what
> machine I copied to, or who initiated the copy, the machine would always
> lock up.
>
> Fearing a hard drive problem, I tried copying the file (and then the
> directory) to another drive on this machine - and it worked fine! No lock
> up.
>
> Lastly, I compressed the directory into a compressed folder and did a copy
> to a remote machine, and it worked fine.
>
> It seems as though a specific bit pattern sent out over the network driver
> causes the machine to lock up. Question is ... how do I fix it? I'm
> running TCP/IP only on this machine over a generic Intel 10/100 NIC (using
> the Microsoft drivers supplied with the OS).
>
> Any ideas on how to get this fixed? There are other files/directories
> that exhibit this problem, which makes it hard for me to use this machine
> as a file share on my small network.
>
> --
> Doug Thews
> Director, Customer Solutions
> D&D Consulting Services
> ----------------
> Visit my Tech Blog at:
> http://www.ddconsult.com/blogs/illuminati/
>
>
>
>

What if the client operating system is the server itself copying to another
WinXP machine? I don't see SMB getting in the way of that.

--
Doug Thews
Director, Customer Solutions
D&D Consulting Services
----------------
Visit my Tech Blog at:
http://www.ddconsult.com/blogs/illuminati/



"Steven L Umbach" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Windows 2003 requires smb signing which can cause problems depending on
> the client operating system. I would disable it at least temporally via
> Local Security Policy going to security settings/local policies/security
> options and for the option Microsoft network server:digitally sign
> communications(always) set it to DISABLED. If that does not help after a
> reboot I would install the latest drivers from Intel for your network card
> and if that does not help try another network card. Also if the network
> adapter properties is set to auto for network speed it is worth a try to
> set it to 100. --- Steve
>
>
> "Doug Thews" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>I ran into a very interesting problem with a standard Windows 2003 server
>>and several files. I have an installation area that I share out on my
>>small network. With just 1 user connected, I noticed that the server
>>would lock up (no blue screen, just keyboard/mouse lockup and no ping
>>response).
>>
>> I traced it to when I was trying to do an install of various utilities
>> from the a network share on this machine. So, I copied the small share,
>> and it locked up. Tracing it further, I noticed that it would ALWAYS
>> lock up when copying this single file (189K in size). It didn't matter
>> what machine I copied to, or who initiated the copy, the machine would
>> always lock up.
>>
>> Fearing a hard drive problem, I tried copying the file (and then the
>> directory) to another drive on this machine - and it worked fine! No
>> lock up.
>>
>> Lastly, I compressed the directory into a compressed folder and did a
>> copy to a remote machine, and it worked fine.
>>
>> It seems as though a specific bit pattern sent out over the network
>> driver causes the machine to lock up. Question is ... how do I fix it?
>> I'm running TCP/IP only on this machine over a generic Intel 10/100 NIC
>> (using the Microsoft drivers supplied with the OS).
>>
>> Any ideas on how to get this fixed? There are other files/directories
>> that exhibit this problem, which makes it hard for me to use this machine
>> as a file share on my small network.
>>
>> --
>> Doug Thews
>> Director, Customer Solutions
>> D&D Consulting Services
>> ----------------
>> Visit my Tech Blog at:
>> http://www.ddconsult.com/blogs/illuminati/
>>
>>
>>
>>
>
>

I don't believe that smb is required when W2003 is the client - just when it
is the server. I don't know for sure that smb signing is related to your
problem but I mention it because many times it does cause networking
problems with XP, particularly SP1 when in a Windows 2003 domain or trying
to connect to a Windows 2003 Server in a workgroup. I have experienced a
similar problem to yours before and the problem went away when I replaced
the network adapter. It was a weird problem in that I could copy files to
the computer fine but any time I tried to copy file from the computer it
would lock up. Up to that time with no change in configuration it worked
fine for a long period of time.--- Steve


"Doug Thews" <(E-Mail Removed)> wrote in message
news:OsKT$(E-Mail Removed)...
> What if the client operating system is the server itself copying to
> another WinXP machine? I don't see SMB getting in the way of that.
>
> --
> Doug Thews
> Director, Customer Solutions
> D&D Consulting Services
> ----------------
> Visit my Tech Blog at:
> http://www.ddconsult.com/blogs/illuminati/
>
>
>
> "Steven L Umbach" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Windows 2003 requires smb signing which can cause problems depending on
>> the client operating system. I would disable it at least temporally via
>> Local Security Policy going to security settings/local policies/security
>> options and for the option Microsoft network server:digitally sign
>> communications(always) set it to DISABLED. If that does not help after a
>> reboot I would install the latest drivers from Intel for your network
>> card and if that does not help try another network card. Also if the
>> network adapter properties is set to auto for network speed it is worth a
>> try to set it to 100. --- Steve
>>
>>
>> "Doug Thews" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>>I ran into a very interesting problem with a standard Windows 2003 server
>>>and several files. I have an installation area that I share out on my
>>>small network. With just 1 user connected, I noticed that the server
>>>would lock up (no blue screen, just keyboard/mouse lockup and no ping
>>>response).
>>>
>>> I traced it to when I was trying to do an install of various utilities
>>> from the a network share on this machine. So, I copied the small share,
>>> and it locked up. Tracing it further, I noticed that it would ALWAYS
>>> lock up when copying this single file (189K in size). It didn't matter
>>> what machine I copied to, or who initiated the copy, the machine would
>>> always lock up.
>>>
>>> Fearing a hard drive problem, I tried copying the file (and then the
>>> directory) to another drive on this machine - and it worked fine! No
>>> lock up.
>>>
>>> Lastly, I compressed the directory into a compressed folder and did a
>>> copy to a remote machine, and it worked fine.
>>>
>>> It seems as though a specific bit pattern sent out over the network
>>> driver causes the machine to lock up. Question is ... how do I fix it?
>>> I'm running TCP/IP only on this machine over a generic Intel 10/100 NIC
>>> (using the Microsoft drivers supplied with the OS).
>>>
>>> Any ideas on how to get this fixed? There are other files/directories
>>> that exhibit this problem, which makes it hard for me to use this
>>> machine as a file share on my small network.
>>>
>>> --
>>> Doug Thews
>>> Director, Customer Solutions
>>> D&D Consulting Services
>>> ----------------
>>> Visit my Tech Blog at:
>>> http://www.ddconsult.com/blogs/illuminati/
>>>
>>>
>>>
>>>
>>
>>
>
>

I think it's the card itself, because now I'm getting the pop-up toaster
that says connected at 10.0MB, when I know it's a 100MB connection (I even
changed it to 100MB full duplex), but still no dice. Sounds like I need to
replace the card.

Very strange that it only locks up when certain byte patterns are sent.

--
Doug Thews
Director, Customer Solutions
D&D Consulting Services
----------------
Visit my Tech Blog at:
http://www.ddconsult.com/blogs/illuminati/



"Steven L Umbach" <(E-Mail Removed)> wrote in message
news:OJ%(E-Mail Removed)...
>I don't believe that smb is required when W2003 is the client - just when
>it is the server. I don't know for sure that smb signing is related to your
>problem but I mention it because many times it does cause networking
>problems with XP, particularly SP1 when in a Windows 2003 domain or trying
>to connect to a Windows 2003 Server in a workgroup. I have experienced a
>similar problem to yours before and the problem went away when I replaced
>the network adapter. It was a weird problem in that I could copy files to
>the computer fine but any time I tried to copy file from the computer it
>would lock up. Up to that time with no change in configuration it worked
>fine for a long period of time.--- Steve
>
>
> "Doug Thews" <(E-Mail Removed)> wrote in message
> news:OsKT$(E-Mail Removed)...
>> What if the client operating system is the server itself copying to
>> another WinXP machine? I don't see SMB getting in the way of that.
>>
>> --
>> Doug Thews
>> Director, Customer Solutions
>> D&D Consulting Services
>> ----------------
>> Visit my Tech Blog at:
>> http://www.ddconsult.com/blogs/illuminati/
>>
>>
>>
>> "Steven L Umbach" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Windows 2003 requires smb signing which can cause problems depending on
>>> the client operating system. I would disable it at least temporally via
>>> Local Security Policy going to security settings/local policies/security
>>> options and for the option Microsoft network server:digitally sign
>>> communications(always) set it to DISABLED. If that does not help after a
>>> reboot I would install the latest drivers from Intel for your network
>>> card and if that does not help try another network card. Also if the
>>> network adapter properties is set to auto for network speed it is worth
>>> a try to set it to 100. --- Steve
>>>
>>>
>>> "Doug Thews" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>>I ran into a very interesting problem with a standard Windows 2003
>>>>server and several files. I have an installation area that I share out
>>>>on my small network. With just 1 user connected, I noticed that the
>>>>server would lock up (no blue screen, just keyboard/mouse lockup and no
>>>>ping response).
>>>>
>>>> I traced it to when I was trying to do an install of various utilities
>>>> from the a network share on this machine. So, I copied the small
>>>> share, and it locked up. Tracing it further, I noticed that it would
>>>> ALWAYS lock up when copying this single file (189K in size). It didn't
>>>> matter what machine I copied to, or who initiated the copy, the machine
>>>> would always lock up.
>>>>
>>>> Fearing a hard drive problem, I tried copying the file (and then the
>>>> directory) to another drive on this machine - and it worked fine! No
>>>> lock up.
>>>>
>>>> Lastly, I compressed the directory into a compressed folder and did a
>>>> copy to a remote machine, and it worked fine.
>>>>
>>>> It seems as though a specific bit pattern sent out over the network
>>>> driver causes the machine to lock up. Question is ... how do I fix it?
>>>> I'm running TCP/IP only on this machine over a generic Intel 10/100 NIC
>>>> (using the Microsoft drivers supplied with the OS).
>>>>
>>>> Any ideas on how to get this fixed? There are other files/directories
>>>> that exhibit this problem, which makes it hard for me to use this
>>>> machine as a file share on my small network.
>>>>
>>>> --
>>>> Doug Thews
>>>> Director, Customer Solutions
>>>> D&D Consulting Services
>>>> ----------------
>>>> Visit my Tech Blog at:
>>>> http://www.ddconsult.com/blogs/illuminati/
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>