Few months ago I was a senior consultant for a German ERP well known system. Because of life circumstances I had to move into a new country and change my career into server and network infrastructure. Found your channel and I can say that I've never had a tutor as good as you. I have really improved a lot, many doors have opened to me and all thanks to your classes. Keep the good work Eli Sensei!
If you got a text-to-speach reader to read that last sentence, it would be: He is the best I period T period tutor comma period period I just thought that was funny.
So glad I found you. . I left technology at CD players, never owned an mp3 ever🤣 I was the one calling for help. . . UNTIL we nailed a tech support person for Costco concierge service. . . ( based off tech knowledge from like 97' and CAD training -that was the test they gave me😜) so now, NOW we down the rabbit's hole HARD catching up. . . So glad to have found your channel. 💥💪💪💪
This is the best IT channel I have found online. I agree troubleshooting is the best attribute to have strength in. I am currently refreshing on some things to prepare for my second interview with the IT director. Thanks for your service, do you have any way i can send a donation or support your channel. Thanks Eli fingers crossed i get the job.
Step 7 is more like writing the problem down and how you fixed it so you can find out how to fix it again if it comes up. The badge is from Cisco. They send it out to you once you get certified.
before starting the networking classes here on eli's channel, i was wondering how could i sit with videos with each vid about an hour average. But guess what, i never yawned while going through them. His classes are so straight forward and energetic. Thanks eli
Really I am not getting bored whenever I watch your tutorial even it's been a decade some of your content is damn perfect to learn even now, for beginners like me!! when I need to refresh I always get back to your videos for more clarity. Thanks very much, Eli! Great work and keep going!!
You will probably need to look into another IT job, like computer networking, systems administration, programming, etc. Even then, there will most likely be some collaboration between other people and departments.
Great video and great coverage of the least utilized skillset in IT. I like the way my company's IT works in that we don't look for excuses, we find solutions. We pull people into a conference and we keep pulling more people in until we have enough heads banging around to find the kink in the chain. After we identify the problem and implement the solution, we test and verify resolution. Then we perform root cause analysis, and distribute that information with a "Lessons Learned" conference, focusing on how to incorporate new policies and procedures to address prevention and timely recovery of a similar issue in the future. Of course all of the above happens after my team puts the fire under everyone's asses to stop blameshifting and collaborate. :)
Something I like to do when troubleshooting an issue is: write down all the important details and everything I've done to fix the issue. This can be helpful if something goes wrong and you need to back track the issue. A lot of times there are many fine details that are hard to recall when your under stress and/or pressure. Writing down the important details will help you stay organized. For example: their may be times when you have to move around a lot of files onto different locations on a server or more. Being able to refer to this will save you a lot of time and headaches!
some times while watching certain videos we people have the option of turn off and switch back to some other work. But this guy, its not happening. I use to go from 0.00 and to the end. Hats of to you Eli
Hi, Eli thanks a lot for this important information. I came over here after I committed negligence in my troubleshooting process, so I used to do all that you mentioned on this course, but I underestimated the process, trying to fix the issues quickly I skipped some paths, the result was so bad, a put in risk my reputation as a network technician. So, it's very important to follow all steps even you've been done this for ages. I am watching this video once again, and no matter how long I will do it, today I felt how painful is when you skip a path of troubleshooting to gain time. Customer (user) doesn't understand the process of TSHOOT all they want is their stuff working fine again, and quickly.
You are an absolutely incredible teacher, I work for a WISP and watching these videos even though I know a lot of this stuff touching up on it again really helps. Thanks again!
Eli, I am back again for more training. Again, you do a great job presenting the subject very well and review enough to make sure WE get the point. My main work is in Automation systems and SCADA systems development and maintenance. Networking is a key to linking all this together. Troubleshooting any system is most important. Your step by step process, outside to inside movements in isolation is very helpful. Isolating things that work is as important as finding things do not work. Thanks again
I like the way you deliver your classes and especially the FINAL THOUGHTS on how you summarise the sessions, very professional presented. Thank you really enjoyed.
13 years into the IT Sector...all these that I have learned into the "Battlefield field" into one Video. Awesome job...I am getting a big fun of you my friend...this should be my bible...
Another thing to remember... Google! Google is amazing, and have helped me solve a ton of problems. Use it when you can. Practice smart searching and effiecient word usage. You don't always want to be too specific.
Great informative vids Eli. Wish I'd had a teacher like you! I really like the "Final Thoughts" where you cover again all you've taught. It kind of fixes everything in my mind. It seems you go through a lot of what the problem isn't until you get to what it is!
Just want to add: Kudos on stressing cable tracing. It is so easy to begin the process of moving cables on a port or patch panel, only to find yourself holding two loose ends that are connected!!! And thinking, "UH....OH!"
I work in industrial maintenance recently decided on a career change. I work with a lot of computers we use this exact process just when it comes to computers we don't go this in depth. Usually our responsibility ends at replacing hardware, then we pass it on to bob.
Great video, very educational and interesting. Only one point which I believed you missed, which goes hand in hand with reporting is Documenting. Any problems and changes made should be well documented so the next person that comes to work with it, if it is not yourself knows what has been done.
Eli, I know this is an old video but you spent 10 minutes breaking down a theoretical issue with a user connecting to a web server and then finally at around 30:20 you got around to the first question that I would have asked: "Is this affecting other users at your site?" It would have saved a lot of time and trouble to narrow things down to that specific workstation.
That's great Eli and thinking it is best to do the easy harmless fix checks first eg browser cache out of sync with web server- does the website work in another type of browser -easy fix clear browser cache(not passwords or autofill form data). Just found out CTRL h takes you into most type of browser's history settings.
I will download this video for my colleagues to learn that what they're doing is not right. Troubleshooting is not been spoon-feeding, it is learning to find the fault and fix it.
Thanks Eli, Seriously, these videos are the best thing next to sliced bread. I really enjoyed your Intro to VoIP. It would so awesome if you would do a video on troubleshooting VoIP. Ive been put in a position at work where Im responsible for VoIP and im like WTF most of the time :S Anyways, thanks man. There must me thousands if not tens of thousands of IT people that have gained from this channel. Cant say thanks enough!
I like the steps in the process to analyze the problem and do contact with the people ,also the most important point is the way of providing the service to customer
I wish, WISH that your lessons were applicable in 2020. Unfortunately most IT these days is done via remote management and is almost never on-site. Sadly the position of an in-house IT has been outsourced.
Overestimating the time to fix, as Mr Scott said to Jordy "always add 20 percent to the estimated time, that way if you finish early, they think you are a genius".
Excellent video, you have an amazing ability to convey information, i am definitely going to continue watching all of your videos; I also like your beard wish i could grow one like that.
If personal experience fails at the first approach then save yourself the most time during troubleshooting simply by following the OSI chart. My advice is scaled to expert troubleshooters from support technician up to network or system administration.
i beg you plese tell about The Network layer Network layer concepts, design issues, static and dynamic routing algorithms, shortest path routing, flooding, distance vector routing, link state routing, distance vector routing, multicast routing, congestion control algorithm, internetworking, Ipv4
Hey Eli the computer guy. I'm a fan. Watched alot of your videos. I was wondering if you sell your long sleeve shirts with the the logo on it. If you do where can i go to buy one. I Love your teaching and I'm even grown fond of the shirt.
and with assigned IP addresses.. let me see if i understand.. the ISP assigns a range of ip address 1.92.168.2.0- 99. and then to each of the 100 computers in my example, you would assign a "Static"? IP address? i know a little about a lot so dont let my next question confuse you,cant you use dynamic IP addresses, and merely set a list of allowed mac addresses?
so, you have a 100 person office, local servers. File/print/mail whatever. Im trying to formulate what i think the path of info is for that, but i have no real knowledge of this field.. so regardless of what it is. client computer would send request that travels through the cable, to a router, to a switch, to the server, and then back the same path to the client?
Think that - after watching this vid, that the issue with most companies offering such services is transparency with their clients when things get wonky.