Haha, this thread is making me LOL. Sorry kid but some of the posters on here are experts in there field (me excluded from that, I have a long way to go up the pyramid before getting to some of them though. You really have no idea about ISP network infrastructure. The chances that their equipment is "getting too hot and rebooting" is slim to none. Good ISP's have problems every now and then and typically know what they're doing as far as equipment temperature and things like that. Your 9 months going to college and reading a bunch of books about networking isn't going to teach you anything about actual networking until you have spent about 10 years at a job doing it. This is my 5th year in IT and 3rd year in networking and I still don't have half of it covered yet. How about you watch what you say on these boards and make sure you atleast know what you're talking about first, otherwise it just makes you look like a cocky, seems-to-know-it-all high school kid.
ViviTheMage
Lifer
that would be all of his posts in this thread.
I am in the same boat, I have worked IT for 2 years, schooled for 4 years, and I know shiet compared to a lot of people here on this board.
My IT Manager here has over 30 years of experience and a masters and he still has to call tech support for some things and jump through there hoops, why, because he know's he may have missed something, or maybe they were trained and know more then him about something
.I never said "I know it all", I am just saying I have most of the concepts of networking down to a point that I can tell if it is a problem on my side of if it is a problem on their side.
The systematic on and off gave me just a hint on what was going on, a loose connection, a FUBARd switch port, hot router, or a monkey jumping around.
I did however do physical labs at the college, which did include troubleshooting on about every lab.
Uppsala9496
Diamond Member
- Nov 2, 2001
- 5,272
- 19
- 81
ViviTheMage
Lifer
And thus begins an endless source of amusement for the IT staff.
Whether or not you know enough to properly diagnose the problem, you're not going to be treated any differently than those who know nothing about how their equipment works.
Besides, having everyone cover the initial basic troubleshooting steps is protocol. You might not like it, but it eliminates a fair number of incidents and is in place for a reason.
HAHAHA, this is why tech support people hate dealing with customers, because the customers think they know more than the company. You may have gone through some classes but you don't know their system. If you've worked in the IT field you would understand that not everything (almost nothing) really follows the book. There are different hardware vendors, software vendors to deal with in the mix. Also, don't get snotty with the guy on the phone, it's not his job to TS his side of the problem. He probably makes $12hr. If you want to call up and talk to someone that speaks with customers AND can fix a multi-million dollar network then get used to paying hundreds of dollars a month for your service.
Uppsala9496
Diamond Member
- Nov 2, 2001
- 5,272
- 19
- 81
This thread is making my afternoon go by a lot faster. We just need the OP to post again (for comedic sake).
ViviTheMage
Lifer
Concepts are different than specializing in something
Just like you know concepts of math and that consists of addition, subtraction, multiplication, and division. It doesn't mean you know exponents, equations, etc.
Why would they make you TS your network (which can take up to infinite number of minutes with someone less knowledgeable) when all they can do is see your address and then say, "yeah their is an outage, probably be ~1-2 days before it can be fixed, thanks for paying for our services", which is what the second person said...
Originally posted by: montypythizzle
Concepts are different than specializing in something
Just like you know concepts of math and that consists of addition, subtraction, multiplication, and division. It doesn't mean you know exponents, equations, etc.
So far you have demonstrated that you don't know how to troubleshoot networking and were smug. I also think your assumption of equipment constantly rebooting is also very off. There are only a few rare instances where network gear will keep rebooting and all of them are very serious and require manual intervention to restore.
Plus add to the fact that most networks are designed to handle this exact scenario without affecting service means you're still probably way off on your ASSumption.
Originally posted by: spidey07
Originally posted by: montypythizzle
Concepts are different than specializing in something
Just like you know concepts of math and that consists of addition, subtraction, multiplication, and division. It doesn't mean you know exponents, equations, etc.
So far you have demonstrated that you don't know how to troubleshoot networking and were smug. I also think your assumption of equipment constantly rebooting is also very off. There are only a few rare instances where network gear will keep rebooting and all of them are very serious and require manual intervention to restore.
Plus add to the fact that most networks are designed to handle this exact scenario without affecting service means you're still probably way off on your ASSumption.
Well said spidey!!
/thread
Originally posted by: spidey07
Originally posted by: montypythizzle
Concepts are different than specializing in something
Just like you know concepts of math and that consists of addition, subtraction, multiplication, and division. It doesn't mean you know exponents, equations, etc.
So far you have demonstrated that you don't know how to troubleshoot networking and were smug. I also think your assumption of equipment constantly rebooting is also very off. There are only a few rare instances where network gear will keep rebooting and all of them are very serious and require manual intervention to restore.
Plus add to the fact that most networks are designed to handle this exact scenario without affecting service means you're still probably way off on your ASSumption.
HMM, so my troubleshooting skills are lacking eh? Then why WAS it their equipment that was at fault? I guess when my tire goes goes completely flat I can't "ASSume" that their is some kind of hole in the tire???
Originally posted by: montypythizzle
Originally posted by: spidey07
Originally posted by: montypythizzle
Concepts are different than specializing in something
Just like you know concepts of math and that consists of addition, subtraction, multiplication, and division. It doesn't mean you know exponents, equations, etc.
So far you have demonstrated that you don't know how to troubleshoot networking and were smug. I also think your assumption of equipment constantly rebooting is also very off. There are only a few rare instances where network gear will keep rebooting and all of them are very serious and require manual intervention to restore.
Plus add to the fact that most networks are designed to handle this exact scenario without affecting service means you're still probably way off on your ASSumption.
HMM, so my troubleshooting skills are lacking eh? Then why WAS it their equipment that was at fault? I guess when my tire goes goes completely flat I can't "ASSume" that their is some kind of hole in the tire???
Ok, so lets step through your troubleshooting steps here, in a 5 step based methodology please. If you can do that (and DID do that) then we will move forward.
The issue is you saw the lights off, turned your modem off and back on, then assumed it was their end.
Rule #1 was addressed above, Rule #2 is check the physical layer. If something had broken the cable between the wall and the modem, would you still consider it "Your end". How about the sprinkler guy trenching right through your supply line? How about a dead modem? All of those have the same symptoms, but are much different. Looking at the light is one of the steps, but do you even know which step that is?
Originally posted by: montypythizzle
I thought it was not to talk about networking
Wow, this proves you can't learn everything in books, and that you are a n00b (not that being a noob is bad, you just have a lot to learn).
If you want to be a network guy, learn rules #1 and #2, as they cover 90% of the tickets/calls you get.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 23K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
News NVIDIA and Intel to Develop AI Infrastructure and Personal Computing Products- Started by poke01
- Replies: 411
Facebook
Twitter