ext_293242 (
asbrand.livejournal.com) wrote in
techrecovery2010-07-18 12:03 am
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png)
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
So...where do you turn to?
I've been wondering... Where do you, my fellow tech support folks, turn to when you are stumped on an issue?
I'm certainly not going to post the problem here. *grin*
I will say it is networking related on mostly Windows machines.
Where would you go to look for answers to bizarre issues?
-Az
I'm certainly not going to post the problem here. *grin*
I will say it is networking related on mostly Windows machines.
Where would you go to look for answers to bizarre issues?
-Az
no subject
(no subject)
(no subject)
(no subject)
no subject
(no subject)
no subject
no subject
(no subject)
(no subject)
(no subject)
no subject
NOW, for the non-googlable answers, I turn to IT Toolbox. But be warned; they look unkindly on googlable answers.
After that, just experience. No one remembers the old "debug" DOS commands (fcs:200 400 0 FTW!).
(no subject)
(no subject)
(no subject)
no subject
everything: serverfault.com
realtime: freeNode IRC #(insert relevant channel here)
no subject
If you access the big file locally from the fileserver, does everything keep ticking along? If something's broken in your file I/O, then it could just be that opening the file in read mode (which would happen every time the file was requested, regardless of the protocol/server daemon.) then the disk buffer trying to pre-read the entire thing could be fucking everything up. Or what about a resident scan-on-access virus scanner? If it isn't something like that, associated with big disk accesses or something, then I can't explain why it would happen the same with both SMB and FTP.
(no subject)
no subject
(no subject)
(no subject)
no subject
*cough* Outside of my advocacy...
Failing Google, I usually turn to the guys that I work with, we operate a pretty large scale datacenter that runs pretty much everything (win2k to Hackint0sh to slackware to freeBSD and so on) and they know some pretty off the wall solutions to just about any zaney problem out there. And most of them work.
(no subject)
no subject
no subject
no subject
no subject