Network Files & KB826502

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a Win2K Pro machine that is up to date on service packs and hot fixes
that is crashing when serving data to another Win2K Pro machine. The network
is 1Gb/sec and research has pointed me to KB Article 826502.
The symptoms match and looking at the data in the Resolution section,
specifically the "File Information", I have found that the files listed are
older than the KB article calls for.
I figured that having SP4 and the latest hotfixes would give me the latest
files, but it is not so, and I'd like to know how I can get them, easily and
quickly The following chart details the file information:

Filename Date on Systems Date in KB Article
Afd.sys 19-Jun-2003 21-Sep-2003
Msafd.dll 19-Jun-2003 27-Sep-2003
Tcpip.sys 19-Jun-2003 21-Sep-2003
Tdi.sys 19-Jun-2003 21-Sep-2003
Wshtcpip.dll 19-Jun-2003 27-Sep-2003

AdvThanksance,
John
 
John D. said:
I have a Win2K Pro machine that is up to date on service packs and hot fixes
that is crashing when serving data to another Win2K Pro machine. The
Click to expand...
network

Define "crashing". Blue Screen? Spontaneous reboot? Lockup with keyboard,
mouse still moves? Lockup with keyboard and mouse does not move? Lockup
that still allows Task Manager to come up with a Ctrl-Alt-Del? Lockup
where Crtl-Alt-Del gets no response?

That last time I had trouble with this was caused by a bad slot in the
motherboard. It wasn't even the slot the Nic was in, but was the one the
sound card was in. It would spontaneously reboot as soon as traffic hit the
Nic when the file copy began. I have seen bad memory chips cause the same
thing.
 
Crashing in this case was a spontaneous reBOOT. This has happened twice in
one day. Conditions are:
- Transferring image, as in photographic, data to a disk on another
machine
on the network.
- Tranferring this same data to a local disk works fine, meaning no
crash.
Thanks,
John
 
John D. said:
Crashing in this case was a spontaneous reBOOT. This has happened twice in
one day. Conditions are:
- Transferring image, as in photographic, data to a disk on another
machine on the network.
Click to expand...

Ok, well there is no such thing as photographic data. The NICs and the BUS
only see "ones and zeros", doesn't matter if it is an image, a text file, a
binary, or an executable, it all the same. Anyway, like I said, the two
causes I have experienced were a bad slot in the Motherboard and/or bad
memory chips. They caused the exact spontaneous reboot that you describe.
 
Back
Top