Print Story Sunshine and Roses
Diary
By Phil the Canuck (Wed Nov 14, 2007 at 09:52:15 AM EST) (all tags)
Aside from all of my problems with how he's running things, I always thought The Boss was a generally decent guy with a relatively good (for management) grasp of the basics.


We have a VPN server at work. This shouldn't come as a surprise to anyone. Our VPN server is running on a Dell Poweredge 2650 that also runs our web server. It is massively overpowered for what it's doing right now, but that's because it was retired from its original job just after The Boss started. You know, after he spent all of his honeymoon budget on new HP servers that are even more overpowered. It is, in short, a real server designed to do real server things. It has been dead-on reliable for over two years now (in its role as VPN server).

Webby has been doing a lot of work for The School.

The School, if I haven't talked about it enough, is where The Boss originally worked. He is their IT director in addition to being our IS director. We used to (pre-this boss) be compared to The School's IT, despite their network being smaller and their effectively limitless budget. They never had any problems and everything was always sunshine and fucking roses over at The School. Not surprisingly, as we've gotten to know The Boss and his network better, it turns out that's not really the case. The perceived perfection at The School is a combination of The Boss snowing the shit out of his boss, and his boss wanting to cover up the things The Boss can't hide so that everyone thinks The School is perfect.

Anyway, back to Webby. He's been having all sorts of trouble keeping a stable connection to The School's VPN. This is obviously a problem with my network, since everything is always sunshine and fucking roses at the school. Despite my investigations showing no problems on our end, every time Webby has a problem I'm re-tasked with finding what's wrong with my network. Never mind that, on the average weekday, there's five or so telecommuters who would be screaming bloody blue murder if they were being disconnected every thirty seconds.

Last week The Boss was chatting with us while Webby was up-and-down on the VPN. He mentioned how he was having trouble staying connected to The School all weekend, then he told me to find out what was wrong with my network that was causing Webby to disconnect. Resisting the urge to leap across the room and throttle him, I suggested that maybe The Boss should do some investigating to rule out problems at The School. No need, he assured me, everything was sunshine and fucking roses over at The School.

Yesterday I found out that The Boss is running his VPN (and a couple of other things) on a retired desktop with an integrated NIC. He has been having trouble with all of the other things he runs on that box.

Today I'm at home, since my son is sick, and my VPN server is doing fine. Sunshine and fucking roses.

< Plot of a Bad Porn Movie? | BBC White season: 'Rivers of Blood' >
Sunshine and Roses | 4 comments (4 topical, 0 hidden) | Trackback
So basically by jayhawk88 (2.00 / 0) #1 Wed Nov 14, 2007 at 10:04:24 AM EST
It seems the problem is that you're network is having trouble compensating for latency?



I didn't think of that by Phil the Canuck (2.00 / 0) #2 Wed Nov 14, 2007 at 11:36:19 AM EST
It's been my fault all along.

[ Parent ]

fucking roses by wiredog (2.00 / 0) #3 Wed Nov 14, 2007 at 02:30:32 PM EST
Given the thorns on roses: Ouch!

Earth First!
(We can strip mine the rest later.)



I hereby claim to know nothing about VPN by m0rk (2.00 / 0) #4 Thu Nov 15, 2007 at 03:47:47 AM EST
but I do know that years ago, some where in Europe, Cisco was responsible for VPN failure due to poor packet tagging, in which every 10 thousandth packet was being dropped due to bad tags, causing connection failure across th VPN.

It took a team of 9 engineers some thing like 12 months to discover this. They endlessly peered in to the network finding that every thing had been set up by the book and was interfacing well cross-platform-style between Linux and Cisco's routing tables. It turned out that poor packet tagging resulting in dropped packets was the issue.

Repeat that to yourself, 9 engineers, 12 months. That's a lot of money to discover that it was Cisco's fault.



Sunshine and Roses | 4 comments (4 topical, 0 hidden) | Trackback