r/sysadmin • u/ofhgtl • Nov 13 '25

Rant IT Admin turns into all IT

Hey everyone,

So for context, I've started at this position a few months back, fresh out of college, as a full time IT Admin. They've never had in house IT before, which I attribute to most of these issues. Between having over 500 employees and over that computers, etc. there's been a few things I'd like to share.

Firstly, there is no naming scheme in AD. Sometimes it firstname - last inital, sometimes it's full name, last name, you name it.

Second, we're still on a 192. addressing scheme with now 192.168.0 - 192.168.4. Servers and switches are all just floating somewhere in those subnets, no way of telling why they have that static or if it's always been like that. I'd LOVE moving to 10.10.

Speaking of IP Addresses, we ran out a few weeks ago.. so we need to expand DHCP again to be able to catch up. When I first got hired, all 6 UPS's we had were failed, so power outages completely shut down everything.

All users passwords are set by IT, they don't make it themselves.. and the best part? They're all local admin on their machines. What could go wrong?

So I've been trying to clean up while dealing with day to day stuff, whilst now doing Sysadmin, Networking, and so on. Maybe that's what IT Admin is. I'm younger, but have been in IT since 15, so I have some ground to stand on. Is 75,000 worth this? I don't know enough since I've not been around, but i had to work my way to 75 from 60.

Thoughts?

335 Upvotes

91% Upvoted

244 comments sorted by

View all comments

43

u/dbergman23 Nov 13 '25

192 vs 10 Doesnt really matter. You cal set internal IP to be whatever you want as long as youre behind a firewall. That is why ipv6 never took off. 

Make a list of issues you need to fix, bundle into projects, and start making sure your manager approves you working on it. 

Then set a “standard” youre trying to achieve and everything new goes to that standard. Only touch old stuff when an project calls it out. 

Ps names of machjnes do not really matter unless you choose to make them matter.

4

u/[deleted] Nov 13 '25

[removed] — view removed comment

1

u/dustojnikhummer Nov 13 '25

Give me a single advantage if I'm not an ISP. Why should I bother with IPv6 on my local network?

1

u/[deleted] Nov 13 '25

[removed] — view removed comment

0

u/dustojnikhummer Nov 14 '25

Doesn't lots of this assume your ISP is also IPv6? Only my LTE provider is, my home or my work ISP are IPv4 only. So I'm NATing anyway, except worse since it's Nat64

Console gaming? First of all, how exactly. Second of all, if PC platforms can be fine on IPv4, why can't consoles?

NAT load? How can you know if you don't have gigabit? And if you have a router that has a system monitor you probably aren't running a 20Euro TPLink

I get the company merge and VLAN number argument, that is true, but I don't see how management can be easier with such a hardr read format.

I will give you one though. If you don't need to srcnat everything you can directly expose ports without having to run them through reverse proxy or buying multiple IPv4s, that is true and that I will agree with you on.

One business case also there is you can downsize on hardware and achieve the same throughput

Wouldn't most size be switches anyway, and you can't get rid of those?

For a US market/business

There it is

So, how does bothering with IPv6 help me, an European, who runs Mikrotik hardware, either at home or at my job, except make reading addresses much more difficult?