Current Events > That "eureka moment" in IT is great. Especially with complex problems.

(+) Yeah! (+)

I think this is pretty much what draws me to network engineering and IT in general. Network engineering is very complex, but it isn't hard. There are a number of rules you need to understand about every little thing, but once you understand and internalize that stuff, then you get to be pretty good at it.

It can be pretty stressful trying to figure out a problem, but once you figure it out and fix it, it feels great.

That moment when you remember it has to be turned on at the wall.

Was the fix turning it off and on again?

LordFarquad1312 posted...

Was the fix turning it off and on again?

Wireless wasn't working in a certain area of a building. I found that some VLAN tags were missing on the upstream switchports that were connected to the switch in that area of the building. Once I added those back in, wireless started working.

How much is it VPN issues for remote workers

JuanCarlos1 posted...

How much is it VPN issues for remote workers

Problems with VPN issues for remote workers isn't a common problem I've dealt with. The hard part is getting the client VPN infrastructure set up in the 1st place, but once that's done it works the same way for everyone.

Any problems reported are typically either:

• A user having their own internet connectivity problems and therefore problems connecting to the VPN
• Internet connectivity problems at the core, which means everyone is having problems connecting to VPN.

My last job had me doing a lot of IT work and I absolutely hated it.

I thought this was going to be about the Stephen King book or movies.

MutantJohn posted...

My last job had me doing a lot of IT work and I absolutely hated it.

I would say I have a general disdain for that "IT generalist role" professionally. There are some areas of IT I like outside of networking, but networking is my jam. I wouldn't want to be imaging laptops or doing general troubleshooting for users. I had enough of that in my 5.5 years of doing tech support.

CableZL posted...

I would say I have a general disdain for that "IT generalist role" professionally. There are some areas of IT I like outside of networking, but networking is my jam. I wouldn't want to be imaging laptops or doing general troubleshooting for users. I had enough of that in my 5.5 years of doing tech support.

Ugh, no kidding.

I was hired as a software dev and when I had to keep installing and setting up these tablets, it was really a big part of why I quit.

CableZL posted...

* A user having their own internet connectivity problems and therefore problems connecting to the VPN

Thats me every other week after forgetting to plug in the internet repeater from its source.

Debugging computer programs when I was in school was sooooo frustrating, but I agree TC, when you hit that compile button and the program finally fucking works... its great

CableZL posted...

I would say I have a general disdain for that "IT generalist role" professionally. There are some areas of IT I like outside of networking, but networking is my jam. I wouldn't want to be imaging laptops or doing general troubleshooting for users. I had enough of that in my 5.5 years of doing tech support.

Haha, this is what I do, basically. I do want to eventually "level up" and go into a System Admin role, but the one thing I dislike is having to be on-call 24/7 (my organization's SysAdmins have talked about it before).

Solar_Crimson posted...

Haha, this is what I do, basically. I do want to eventually "level up" and go into a System Admin role, but the one thing I dislike is having to be on-call 24/7 (my organization's SysAdmins have talked about it before).

Yeah, I lived that on-call 24/7/365 life at my old job. It wasn't bad at first when it was a small company, but when they started rapidly expanding in size around 2018, it was terrible.

At my current job, I'm part of a big team of network engineers. Now I'm only on call one week out of every 7 or 8 weeks or so.

What does VPN mean?

Sunhawk posted...

What does VPN mean?

Virtual Private Network. It has a few different use cases.

1. Site to Site VPN tunnel: Creates an encrypted connection between two different locations. Used to keep certain kinds of data from being readable as it goes through the public internet.
2. Client VPN: Used to give a user at a remote location a connection into a company's network that is both secure and portable.
3. MPLS (Multi-protocol label switching) VPN: A much more expensive VPN solution where an ISP will segment off a private network for multiple sites to connect to. This data does not necessarily need to be encrypted and does not pass through the public internet between locations.

Is the Eureka Moment in IT when you learn about the turtle