First month in first IT job - not so sure...

Finally got my foot in the door doing help desk at an MSP, but I'm wondering if I'm even ready for this?

Ive been introduced to a lot of new proprietary technology. So far I'm doing things like password resets, account creations, etc - a lot of tier 1 stuff, which is very easy.

As for my knowledge, I've taken a class on Windows server and I practically have the knowledge found in A+. I'm starting to think this isn't enough...

Today I was having problems connecting a clients printer. Found out that I couldn't even ping it. Same subnet, same default gateway, everything. I remoted into another one of their users who could print off the same printer. Again, same subnet and all. That PC could print and ping the printer successfully, but couldn't ping the PC I was working on initially.

Anyway, I did all that I could with my limited knowledge. Walked up to the senior techs and told them my issue and one of them says sarcastically "it's time you start being a tech."

This was very offsetting for me. I know all the techs here have been at my point in their lives, but I'm starting to think if I'm even ready for this.

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

lunarian

I am really glad that I am not the only one that hates printers.

Anyways, I say just keep learning and don't worry about people like that. Everyone started out somewhere and someday he may be coming to you for help and you can decide to show him some karma or to be nice and friendly and help out. Either way, grats on your first job and keep on trucking!

psaechao

Hi Everyone,

Wow, thanks for all the replies! I enjoyed reading all your comments.

As far as the fix, it turns out that whatever port the user was running their Ethernet cable from, something must've been configured on the router/switch from preventing it from seeing the other devices. I had the user find and use a different cable and it worked out perfectly. I was able to see other devices on the network, as well as the network printer.

We are an MSP and we do all our troubleshooting remotely - many of you may know the hardship of this. I, too, have found that printers and mobile devices suck...

On a different note, the IT director at my old company (they are a mortgage company so IT is internal) reached out to me about an open position. The position is actually a networking job which entails going out to branch locations and setting up network infrastructure. I'm hoping this is something that I can enjoy when I go to work!

newinew54

do not get discourage.. you will find jerks in this world but hey it is part of the leaning experience.. then you will find people that really know their staff and will go out of their way to teach you.. stay with it.

cowill

markulous wrote: »

So you research an issue, try your best to troubleshoot it, and all you get is a sarcastic comment when you ask for help? Wow...

My best advice is keep your head down and try to gain as much experience as you can until you can find something else with a better learning environment.

When anyone takes on new responsibilities or unfamiliar tasks they feel the same way as you. There's no shame in feeling intimidated or having bad days where you get your butt kicked. It happens.

The middle paragraph means a lot!! By the sounds of things you are in s**** environment...DO NOT let that determine how you feel about
IT and if you got it or not...gain skills and keep it moving.....

systemstech

Sounds like the PC wasn't on the same network. Anyways, don't even worry about it dude. With his attitude, you'll surpass him before you know it.

White Wizard

psaechao wrote: »

Hi Everyone,

Wow, thanks for all the replies! I enjoyed reading all your comments.

As far as the fix, it turns out that whatever port the user was running their Ethernet cable from, something must've been configured on the router/switch from preventing it from seeing the other devices. I had the user find and use a different cable and it worked out perfectly. I was able to see other devices on the network, as well as the network printer.

We are an MSP and we do all our troubleshooting remotely - many of you may know the hardship of this. I, too, have found that printers and mobile devices suck...

On a different note, the IT director at my old company (they are a mortgage company so IT is internal) reached out to me about an open position. The position is actually a networking job which entails going out to branch locations and setting up network infrastructure. I'm hoping this is something that I can enjoy when I go to work!

Was the port on a different VLAN? Seen that a million times.