It must be Comms

I've worked in IT now for 3 decades which doesn't necessarily give me a good insight into the behemoth that it is and there are still many, many things about it I don't understand; like SAP.

But the one thing I really don't understand is why everything is always the "fault of comms" and why we, in comms, have to prove it isn't before the other sections of IT will even consider looking at an issue. The other aspects that go with this thinking fall into vague areas, such as ...

• can I ping it
• can't I ping it
• don't know what else to do so will dump the call on comms
• it must be a network fault
  

Whatever, the call is coming our way irrespective of the answer. Only yesterday I had a call passed into the "comms queue" with the words - I was able to term serve to it and ping it and all applications appear to be ok - perhaps comms can shed some light on it - or maybe it is just me?

Perhaps someone can shed some light on this. After all, I'm happy to accept there may be a comms fault and that I or one of my team need to investigate it, but surely to God folks should do their own homework first and if the call comes to them prove all is ok.

Here's another one from yesterday's queue .....

Our website has the following message on:
You are seeing this page because we are experiencing difficulties at present and normal service will be resumed as soon as possible.

Yup, you guessed it, this ended up getting logged as a fault and sent to the comms queue with the immortal words of - are there any comms issues? Let me see, how do I explain this one .... NO you numb nut!