michaelmurfy: @r2d2CookingBacon with how many end user problems they have to diagnose issues that appear to be an end user problem often just get filtered out from the network team.

To be fair - when I first saw your issue I thought the same hence why I requested more information. It is only when you get a few people with a similar issue where it potentially turns from a potential end user issue to a wider issue.

Can’t blame 2degrees support on this. They’re not network techs and can only go as far as their scripts and knowledge allow them to go. I’ve worked in this sort of environment too where about 95% of end user incidents get closed before they reach me due to the fact it is highly likely to be an end user problem aka “not our issue”. The remaining 5% that ended up in my incident queue mainly got filtered / closed too.

Support is hard. Just be happy and thankful we’ve got some network techs who read and often help out on Geekzone in their own time.

Sure I used to work at Orcon doing the same thing 15 years or so ago.. I understand that the helpdesk don't have the knowledge or time for the problem I had, however they should not promise call backs etc when they never intend to do that, and 2d obviously needs to hire more staff. 

"Just be happy and thankful we’ve got some network techs who read and often help out on Geekzone in their own time" I am very grateful for this, and thank you very much of consolidating the issues into one ticket, I don't think this would have ever been resolved without it.