Hard Light Productions Forums
Off-Topic Discussion => General Discussion => Topic started by: an0n on February 23, 2004, 08:41:56 pm
-
I've just got my wireless network working (not my idea, BTW).
I had all the hardware set-up within 5 minutes and all the software done 10 minutes after that (Stupid XP restore-points took ages to create).
I then spent the next 5 or so hours trying to figure out why I couldn't connect to the internet. I went through ever setting on the router, every cable, every connection and found nothing wrong. The laptop showed the router was okay and the router showed the modem was fine.
Then about 10 minutes ago it hit me: Turn off the modem.
Five hours of scouring for cables to try different things, installing and uninstalling software, changing hardware and swearing. Yet all I need to do was kill the modem and restart it so it would use the RJ45/Base-T connection through the router instead of using the USB connetion straight to my desktop.
Five hours of my life that could have been saved if someone had just tripped on the cable.
But the strangest thing is, instead of taking out my anger on the NW forumites, I actually find all this amazingly funny.
-
Yeah, been there. 'S why these days I always start at the most basic level and work my way up. "The most basic level" involving a hammer, so that at the very least I'll have enough going wrong to keep me occupied while I look for the problem later.
What forumites would you take it out on, anyway?
-
Point taken.
-
rotfl @ you
that's why you always work up from the bottom of the OSI model not down from the top like you just did
(Physical, Data Link, Network, Transport, Session, Presentation, Application)
-
LOL the OSI model's a joke. it's a theory. its main use is for teaching n00bs what networking's about, not real-life application, but i hate it anyway, because it's a big part of Cisco, and i don't like Cisco.
actually, you should've worked with the TCP/IP model
haha j/k LOL :D :D :p
-
Stealth: the TCP/IP model is basically the same as the OSI model - i just remember the OSI model better because I happen to have half a CCNA (i already knew how to network -- formal training is just bragging rights)
there is nothing wrong with the OSI and is a good model for thin-client archetecture
-
Originally posted by Kazan
rotfl @ you
that's why you always work up from the bottom of the OSI model not down from the top like you just did
(Physical, Data Link, Network, Transport, Session, Presentation, Application)
Thats just plain common sense...
-
Ugh...OSI...I can guarentee that I'll fail that part of the A+. And the Net+ alltogether, now that I think about it. We havent had much time in class to do any actual work with all the busted PC's and mantinence jobs. The county has been having massive problems with virus infestation. They shut down the internet for a few days last week so that we could get an assesment on the problem. Naturally, my school was, with two exceptions, completely virus free. Unfortunately, the rest of the 3k computers in the county were about 98% infected. Oh well, they are thinking of hiring a few of us to go to the schools and clean them up.
-
Originally posted by Kazan
Stealth: the TCP/IP model is basically the same as the OSI model - i just remember the OSI model better because I happen to have half a CCNA (i already knew how to network -- formal training is just bragging rights)
there is nothing wrong with the OSI and is a good model for thin-client archetecture
Kazan... i was kidding about the TCP/IP model... that's why i said "haha j/k lol :D :D :p"
but seriously, the OSI model isn't supposed to be taken literally. the whole reason it was invented was for teaching/explaining network concepts. i happen to have three quarters of a CCNA ;). although you're right, to an extent it's supposed to be used as a reference, but not step by step, just basically the concept. so yeah, he should've started at the bottom and worked his way up ;) . oh, and the Cisco curriculum this year's a joke.
-
All
People
Seem
To
Need
Data
Processing
After 3 years of Cisco, thats about the extent of my knowledge :D:D
-
we learned it
Please
Do
Not
Throw
Sausage
Pizza
Away
-
I forgot our mnemonic
i remember the other one for
Data
segments
Packets
Frames
Bits
-- we were giving one of the guys (peter) a hard time that day and someone popped off "Don't Send Pete For Bacon" (which is the PC version, the unix [jk] version is "Don't Send Pete For B1tches")
-
hahahahaha lol
that's a good way of remembering it. i never got around to memorizing the data types at different layers. it seemed pointless at the time lol