Quote:
Originally Posted by jb66
Because techs have no tools to detect what is causing t3 timeouts or why it occurs, they also can't pass it to networks as the tech can't prove it's a network issue
|
Trouble is, as you might know, various departments jump on the fact that it IS an upstream network issue and immediately blame the local area network but as you state there is no immediate way of knowing where or how it is occurring so very difficult to diagnose.