(no subject)

[loosechanj.livejournal.com]

This luser wannabe thinks he's a sysadmin because he's heard of tcpdump. *snicker*

Right. That's why you had to have the office manager ask the local techie to help you. Because the network didn't seem to be assigning automatic addresses. Go back to reading the script to your peers on the phone monkey fart.

Comments

[loosechanj.livejournal.com]

All that would do is make him sound like an arrogant know-it-all wannabe, which doesn't quite help his case. Since you claim to know him, what's his real job title? He may have an IQ of 220, but he sure as shit doesn't know diddly about networking.

[kuang.livejournal.com]

How many times have you walked into a place as an admin and had instant access to everything without having to either get your claws into the existing tech or getting the manager to unlock the guts of the network so you can sort it for yourself?

While you're at it you might want to try a bit of socratic irony to find out what historically what you're letting yourself in for by posing a few dumb questions at the resident 'expert' to see what they say.

And while you're waiting for *that* you might as well have a poke around to see what's happening elsewhere. I personally can't see the problem..

[stevenothing.livejournal.com]

Out of curiosity, if you moved in to a new serviced office, and the network connection you've been given doesn't work, what would you do?

[loosechanj.livejournal.com]

Given that my job as a systems admin would be to fix just such a problem for others, I would find out why and fix it. But I guess that's just too much to ask out of new hires anymore?

[stevenothing.livejournal.com]

My job as sysadmin is indeed to fix problems for others. But that's on a different network, with different machines.