We have a 24-port 100T switch, and we have a 4 port GigE router. Hardware was another issue that I thought about. :) This server has never had problems with large file transfers before it stores and transfers ISO images over the network all the time. I'd love to hear some thoughts on what could be causing this. The binary data contains the first 32 bytes of the request. Or if a malicious code is trying to probe for available services. This can happen if the provider failed to initialize but was not marked as critical The Following Client failed TFTP Download:Ī request was received by the RPC server on Įndpoint. I have a LOT of Server Manager info messagesįrom WDS (as many as 30 in one minute) but very few errors, and they're all either like this: I am not sure how to post any sort of log files or check what's "under the hood," so to speak, so I guess if someone tells me where I can find them and post them here, that's probably a good place to start. We're on a 100T network so the gigabit connection on the server never goes over 12% utilization.
These working/not working sections each appear to be no longer than 4 minutes for working, and 3 minutes for non-working periods.ĬPU usage on the quad core Proliant M元50 is only at 25%.
Tracking the network connection of the server shows that the server will randomly just completely drop the connection, leaving the client machines either patiently waiting (if they've made it into the "expanding windows files" section) or crashĪnd hang (if they were in the loading boot image section). I've tried this with a minimum of one computer and a maximum of 5 computers at once with the same results. It's using the same win7 boot image to get started. I am trying to deploy a windows 7 custom image to a school.
I'm quite new to the the world of WDS, just started using it yesterday, but I believe I've got a fairly good grasp of what should be happening.
0 kommentar(er)
