Well I’m on the opposite end and youdon’t know how many times I hear we didn’t change anything over and over. And then magically everything starts working again once they actually check stuff.
Literally 50% of my job is communicating with IT to turn of SIP ALG on consumer and enterprise networks. I’m sure the meme is valid but this industry has a huge “not my problem” problem too. I don’t think I’ve worked in a field with less mutual respect among technicians. It’s a real bummer.
I was just coming in to say exactly this. I cannot tell you the number of times IT has told me “there’s nothing wrong with the network” or “no one else is complaining”, yet when I whip out the old trusty packet capture showing missed packets, firewalls sending a TCP RST, etc., then their tune changes. It’s like Confucius always said, “the packets don’t lie”.
Same. I work for a vendor of a certain device that needs an ethernet connection. The amount of times I've remotely checked it out and determined it must be an issue with the connection only to be told it's not by IT and then gone on site to find a connection issue is rediculous.
Either the cable's fucked up somewhere in the roof, or not plugged into the switch on the other end, or the switch is overheating making an intermittent connection, or....it's literally not plugged in.
Honestly, if I’m calling IT it because I’m pretty damn sure that its not an issue on our end and I’m hoping they can help me determine if there is an issue on the client’s network. I’m not trying to point the finger, I’m trying to collaborate towards a resolution for the client, which is both good for us as a service provider and them as their technical support. WE’RE ON THE SAME SIDE! LOL
Same. If I'm contacting the customers IT I've already put at minimum 1hr into it. In one case I drove a 4hr round trip twice over something stupid like this. First trip where I said "Yeah there's gotta be a dying switch somewhere" but the individual that was there didn't know where the network closet was. IT said everything was fine and it must be a problem with our stuff. I go out there again and get the business owner to show me the network closet and in like 2 seconds find the little 8 port switch that was too hot to touch. Moved the connection I needed to another port and it worked. After pulling the power from that switch I told the customer it was a fire hazard and that they would need to have their IT replace it.
It pisses me off though that the guy didn't even check but he's well known for that kind of thing.
When I get the finger point from vendors, the problem I have is: show me what part of the software is getting screwed up. What is it expecting that it’s not getting. Is it a port/network issue? A server spec issue? Drivers? OS patch? Latency? Just saying “it’s not us, it’s something on your side that’s the issue” is no better than kicking the can down the road for someone else to deal with.
Best part is when you ask what the software needs open they can’t tell you because it works on an open test network with no security at all in place. These software companies need to start understanding enterprise networks better.
Add comment