Are you trained by your company?

[255-255-255-0.livejournal.com]

Are you trained by your company?

I was just wondering because I called my local ISP last night due to a dropped connection.

I had a bit of a chat to the bloke who was answering their support calls.
He suggested, (among other things) I could have a damaged NIC.
I pinged the NIC and got a response, pinged my router and got a response.
I told him this.

Him : “So how do you ping your NIC?”
Me: Using the ping command (Duh) < I didn’t actually say Duh ;-)
Him : “What’s the address, do I just type in PING NIC ?

Comments

[insomnius.livejournal.com]

Are you trained by your company?

Not really, no.

[255-255-255-0.livejournal.com]

Well I'm not either, I just thought this sort of stuff would be taught if the tech person didn't know?
How naive am I :-)

[insomnius.livejournal.com]

Indeed. It's not a hugely problematic problem that I don't get trained, because if I don't know I get embarrassed and go find out for myself.

This is not true of all our tech people :/

[insomnius.livejournal.com]

There may be jobs out there which require some form of knowledge and/or skills.

Maybe I should go out and find one before my brain explodes.

[zig-mover.livejournal.com]

how DO you ping your NIC?

[brothersterno.livejournal.com]

very carefully: You don't want to shake up the TCP too much, you might get some packet loss.

[255-255-255-0.livejournal.com]

You want to be realy carful with that TCP stack if you ping it too much it may fall over and rebuilding a stack of pings over a TCP connection with no internal ping nic support is no easy task.
If too many stacks fall you could end up with a heap of falling stacks without a Netbeui. <<<<<<<<<<<<<<<<<<<<<<<<<<<< j/k

ping 127.0.0.1

[brothersterno.livejournal.com]

well, if you overload the TCP, the IP gnomes end up carrying too much stuff through the system of tubes which makes up the Internet, and they get tired and have to stop for some beers to catch their breath. This is called "Latency" by internet engineers (gnome wranglers) to hide the fact that their transport agents are (more or less) drunk. Of course, some of the packet carrying gnomes drink a little too much, and pass out or forget their loads, which causes packet loss. If you have 100% packet loss your tube is broken, or there are too many gnomes trying to fit through, and some will just say "fuck it", drop their load, and go drink beer until the traffic dies down. You can resolve this by installing bigger tubes, which are analogous to the subway, with its larger carrying capacity and greater install expense than roads and cars.

There's no place like 127.0.0.1.

I've never found pinging the NIC to be that effective.

[zig-mover.livejournal.com]

Doesn't that just test your TCP/IP configuration? I think you can ping 127.0.0.1 with no adapter present..

[brothersterno.livejournal.com]

yeah, it just means the NIC is installed. I've had strange problems occur where uninstalling and reinstalling the NIC to a different PCI slot fixes strange synch no surf problems, but it pings to 127.0.0.1 just fine.

[255-255-255-0.livejournal.com]

Yes you are right, I hang my head in shame, slope of to a corner a look embarrassed for at least a month.

Pinging 127.0.0.1 does only give loop-back response to test IP configuration.
I don’t know who I was listening to all those years ago, it just worked and I believed ever since ….......

I'd best get it over with before anyone else says it:


Laugh @ >>>>>>>>>>> 255_255_255_0 <<<<<< What a t00l


In penance for my total 127.0.0.1 noobness check out this link:

http://www.crisscross.com/forum/Worlds_worst_hacker%25_IRC_t%20ranscript/m_422436/tm.htm

It even makes me look smart

[ihateemo.livejournal.com]

Throw a pin at the bracket. It makes a little "ping!" noise if you do it just right.

Works for me!!1!

[trixtah.livejournal.com]

trix@flossie:~$ ping NIC
PING NIC (127.0.0.1) 56(84) bytes of data.
64 bytes from NIC (127.0.0.1): icmp_seq=1 ttl=64 time=0.038 ms
64 bytes from NIC (127.0.0.1): icmp_seq=2 ttl=64 time=0.039 ms
64 bytes from NIC (127.0.0.1): icmp_seq=3 ttl=64 time=0.038 ms
64 bytes from NIC (127.0.0.1): icmp_seq=4 ttl=64 time=0.038 ms

--- NIC ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 0.038/0.038/0.039/0.004 ms


[one probably shouldn't talk about hosts files to Mr Ping NIC, it might confuse the poor lad]

Re: Works for me!!1!

[jecook]

::falls out of chair laughing::

[the-s-guy.livejournal.com]

Am I trained by my company?

Well, short-term contractor at the moment. Whadda YOU think? :)

[255-255-255-0.livejournal.com]

I did get some training once, (in three years) I got 2 days on SQL Server.
I think if I needed, wanted or asked for it I would get it.

What I was geting at really was you would think each person would get training up to a certain level.

[taiki.livejournal.com]

the ISP co. i worked for taught us how to ping localhost.

no one figured it out except those who knew it before hand.

[jecook]

Yes, our company has training for the techs, but let me explain why.

We don't have general computer maintenance training; canidates are expected to have an A+ with them or equivlent experience when they are hired. We do have training on all the software pand some of the hardware packages that are either unique to our installation, unique to the industry we are in, or stuff that written in house. In addition, we do have a professional development program for various certifications, mostly along the MSCA/MSCE track, which also includes the Network+ certification.

I'm probably the only tier 1 tech there who has the raw experience of a tier 2/3 tech, but has no formal certifications to prove it.

[kayfox.livejournal.com]

What is this training you speak of?