Quote:
Originally Posted by happytheman
I don't usually go for the whole one up move, but I think this one belongs to me:
Performed a wireless expansion last night at work to allow us to add more wireless access points. This went swimmingly. Four hours later @ 11pm I was contacted by one of the techs that stuff was not working properly on the wireless network. Things went from bad to worse as more and more people called him. Troubleshooting continued until 4am when we got the server admin involved and rebooted the dhcp server.
Then, bright and early this morning I was told that one of the network segments on the wireless network was not functioning properly....soooo I've spent the last three hours troubleshooting. All this AND I'm supposed to come back in to work from 1a - 5a for downtime updates on the network. FML.  |
terribly sorry to hear, Mr. Happy
Quote:
Originally Posted by happytheman
Yes it's bad when users can't get on the network, especially in a healthcare environment.
Sorry, I can speak networking, but couldn't fathom the idea of installing a turbo myself!  |
I'd like to think that I can speak half-a$$ed on both of those subjects
... or should that be talk out of my a$$?
Quote:
Originally Posted by GaleForce
I assume its basically the same thing. Plug this in here, unplug that and plug it in here, rip this out and toss it, cross your fingers and hope for the best when it's time to hit the "start" button  |
The 'plugging in' part is much easier on a network (especially wireless
) than a turbo. It's all the programming required after everything is plugged in that makes it so complicated - far beyond tuning, which is about the closest comparison I can think of...