Prod and wait

I don't like to post a somewhat serious response to a fun article but as a recovering Windows support tech who has read lots of packet sniff collections of MS network cruft, I can't stand to see someone experiencing the prod and wait phenomenon without sharing some common causes.

Some common causes are:

1. MS Outlook - No surprise there, but MS Outlook is a network pig that insists on sending out a horrible number of "are you still there" minimum size packets to the MS Exchange server. If the MS Exchanger server is slow or is accessed over a WAN link, then MS Outlook will slow down the entire OS. Easiest way to fix is turn on the "Connect to my Exchange mailbox using HTTP" option. It is a much more sane way for Outlook to jabber at the Exchange server.

2. Shortcuts to files on servers on the other side of a WAN link - If you are the kind of person with shortcuts littered throughout the desktop and start menu, this will slow down the entire OS because almost every time you ask the OS to do something, it will send out 'are you there' minimum sized packets to all the servers where you have shortcuts before it does what you want it do. Seems insane, but there you have it. Best way to fix it is to not have shortcuts that point to servers that are not on your LAN.

3. Shortcuts to files that don't exist - See point 2 but multiply the effect by about 10 because the file is not there, which means more jabbering (are you really, really, really not there?). The fix is to clean up your shortcuts.

4. Some turd decided to redirect your 'My Documents' to a file server that is on the other side of a WAN - See point 2 but now add in even more 'are you there' packets because the one folder the OS must see is on the other side of WAN link. This is hard to fix because 9 times out of 10, a MS drone has set this configuration up centrally and is managing your desktop :p

These problems are common in business networks where servers have been consolidated into a couple of data centers (who knows where) but the MS drones have not consulted the network folks on the impact of latency introduced by *all* WAN links on the OS's that are used. The fact is, Windows is set up for LAN latencies and even an extra 5 ms of latency causes the Windows OS's to pause when poked. It can't be fixed by buying more bandwidth. It is a function of latency. Try searching the interweb for Big Fat Pipes if you want an eye opener on the subject.

MS Windows can be modified somewhat via the registry to reduce the impact of latency higher than LAN latency, but for that, you must do more research (and not be locked out of it by the MS drones).

How did Canada get dragged into this?

"embarrassed about their own country's lack of accomplishment. We see it all the time here in Canada."

Hold the show their anonymous buddy. Canada suffers from some shortcomings (name a country that doesn't) but lack of accomplishment is not one of them. I suggest you read a history book, watch the CBC, or even stoop to using wikipedia. Start with http://en.wikipedia.org/wiki/Battle_of_Vimy_Ridge.

Sometimes they learn

As much as it pains me to point out anything positive about MS Exchange, they have remedied somewhat the stupidity of using minimally sized packets over WAN links (or any kind of network) mentioned by James Findley.

Buried in the account options of the MS Outlook client is the option to access the MS Exchange server via HTTP or as they put it "Connect to my Exchange mailbox using HTTP". There are some other options to further tweak the settings.

By doing so, you can get two bonuses;

1. MS Outlook will not bog down your whole OS while it sends, checks,sends, checks and basically babbles at the MS Exchange server over a WAN link with latency higher than 10 ms.

2. If the MS Exchange server connectivity is lost, you will not have to reboot your PC while MS Outlook goes insane. You can carry on using your PC until connectivity to the MS Exchange box is back.

MS Outlook 2003 has this option. Not sure when it was first made available.

Of course to use it, the MS Exchange version must support it and it must be turned on.

Turning on these options have made a distasteful task (relying on MS Exchange) a little less bitter.

Enterprise Networking

I agree with Glen Turner. How come no mention of the retreat?

I was working at a 3Com shop at the time and as part of the companies Y2K upgrades, we installed 3Com's CoreBuilder 7000 at most of the companies locations. OC3 speeds using LAN Emulation. I even invested the effort in becoming 'certified' on the CoreBuilder 7000. Horrible management interface. Especially compared to the CoreBuilder 5000 (I think the only thing the two product lines shared was a name) but those boxes are still delivering 155 Mbps and are rock solid. I hear that the company has finally manufactured a business case for removing them and moving to some Cisco shite solution but it remains to be seen if they can justify it yet.

Why? Because my boss at the time of the retreat convinced the hand wringers to buy spare equipment on E-Bay when the other organizations dumped there equipment in a panic. He bought enough spares for pennies to mitigate all risk and accommodate growth.

Hard to justify moving off of a solution that is solid and still exceeds capacity requirements.

Anyone actually deploy any CoreBuilder 9000's?

Done one right,,,,once

Yes. Usually mgmt, the architect, and the construction trades ususally manage to keep IT out until it is to late. But I did work for a small manufacturing company once upon a time where I got to do it right. They involved us at the beginning and we got such wonderful things as;

* Installed port density based on footage, not the current number of staff. This meant when they added or moved staff, no desperate calls to a cabler were required AND when the auditor quislings showed up for the yearly audit and were crammed into warehouse space, we could actually give them network connectivity without scrambling.

* Wall jacks were installed at what we we called "crotch level" (this amused the CFO and CEO so much that I am sure that is the only reason we got this approved) not ankle level. This makes it easier to connect and move stuff around. Looks better to.

* And, we did not have to share our network closets with janitor closets. That was heaven.

I don't work there anymore, but I still hear they know how to involve IT. Don't lose faith. These places do exist.

litigation culture north of the border - Which Border

Thankfully, the litigation culture in Canada is not even close to what it is in the states. Lawyers and insurance companies spread FUD to convince us otherwise, but the reality is we are thankfully free of nuisance litigation relative to the US.

She won't get a dime unless the organizations she tries to sue have spines of jelly.