Saturday, October 27, 2007

My doppelgänger is preventing me from giving blood

About two weeks ago, I went to give blood for the Red Cross.  It had been at least five years since I had last given blood and there was really no excuse for that.  The Red Cross had a few rooms in another building in our complex and I made an appointment to give some blood.

When I got there, they asked for my donor card.  I had no idea where it was, but that didn't faze them.  They could look me up in the computer.  I gave them my name, date of birth, and Social Security number.  And that's when the fun began.

After entering in that data into their computer, I was flagged as being in-eligible for giving blood.  Forever.  And forever is a mighty long time.  I was given a form letter that included an 800 number that would provide more details.  Due to HIPAA restrictions, the staff at the Red Cross station could not tell me why I had been banned.

So I called that 800 number and talked to a Red Cross representative.  It turns out that there is another Christopher Miller with the same date of birth as me, but living half way across the country.  He has an illness that has banned him from ever donating blood. 

Because we have the same name and birth date, when my data is entered in the local Red Cross database, they hit his record in the national registry.  And they don't look at the SSN number.

The fun continues.  Back at the 800 number, I was told that the only way I can give blood is to not use my Red Cross donor card and never give out my SSN.  Without the SSN, they don't check the national database.

That's the mind-boggling part.  They don't check the national database unless I provide a SSN, but if I provide a SSN they wont use it to filter out other people with the same name and birth date.  That's just wrong. 

Saturday, October 06, 2007

Technical Support: Verizon FiOS vs McAfee

It all started this morning when my wife went to check her email. She said that it wasn't working, so I took a quick look. She uses Thunderbird to check her Verizon FiOS email account. Thunderbird would connect to the POP3 server, incoming.verizon.net, but would time out after a minute or two with the message "Connection to server incoming.verizon.net timed out".

So I pinged incoming.verizon.net and it responded right back, so it didn't seem like a DNS resolution type of error. I logged into her email through Verizon's online webmail interface. That worked, so her account and password were still good. I went to the Verizon FiOS portal page and went through the various help topics. It didn't like Firefox so I fired up IE7. It didn't like Vista and complained that Windows 98 wasn't supported.

That ruled out online support, but it did surrender a toll-free tech support number: (888) 553-1555. (btw, if you ever need to find support number, try the gethuman database) I went down the automated phone tree until it got to the part where it said that I would need to speak a human. And then told that the wait time for a human would be 31 minutes.

Here's where Verizon goes the extra mile. I was given the choice between waiting on hold for the next available human or they would call me back in 31 minutes. I took the "call me back" option and went on with life. About 30 minutes later, Verizon called back and I got to talk with FiOS tech support rep. That's pretty cool.

Within 2 minutes, we determined that the email protection in the McAfee Security Center was blocking Thunderbird. I've only had to call FiOS tech support a couple of time and each time I got a person who knew his stuff and didn't blindly follow a script.

Basically, if you go into the McAfee Security Console and disable email protection, Thunderbird works. Enable it again and Thunderbird can't access the POP3 server. Pretty easy to duplicate and it was repeatable.

Yesterday, we saw a McAfee popup notifying that an update had been installed. Mentally, I had filed that under "Yeah, whatever". It seemed that the latest update was the culprit.

This was the free version of McAfee that you can get with FiOS, via MSN Premium. Getting the free McAfee is a story for another posting, they don't make it easy. Since the McAfee was more or less provided by FiOS, I figure there would be support, more or less. The FiOS guy told me that I would have to contact McAfee support and he gave me the number (800-337-6840) and offered to transfer me over.

I took the transfer and spent the next 25 minutes on hold, which was less far exciting than it sounds. After reaching a tech support specialist named "Terry", the real fun began.

The first thing Terry asked me was the email account that I had registered my copy of McAfee Security Center under. I tried explaining to Terry, that I never had to register my copy McAfee and that it was provided by MSN Premium via Verizon FiOS. Tery mulled thatover for a minute and then asked me for the asset code of my Dell computer. Apparently Terry thought I had eval version McAfee provided by Dell. The funny part is my wife's machine is new Dell desktop, but we had ordered it with the "no software pre-installed" option and her machine did not come with any preinstalled anti-virus application.

I told Terry that I did not have an asset code to give him and it was not relevant to this issue. At this point he finally grokked that I had the McAfee that comes with MSN Premium and I would not be his database. After walking through the steps that duplicate the problem, Terry told me that the solution would be uninstall McAfee Security Center and install a new version. Terry then gave me an issue number and started to wrap the call up. I had no confidence that this would work and requested for Terry to stay on the line. Terry agreed.

I asked Terry how that be different a version than the one that had just updated himself. He said that the currently installed copy had corrupted files. I asked how about he knew this and he said that other people were having this issue. I uninstalled McAfee Security Center and downloaded the latest version through MSN Explorer. You get a 500KB installer and it grabs the actual installable bits from the Internet. While it was downloading, it displayed the usual metrics of size, time, download speed. The download speed averaged around 45Kb/sec. I have the 20Mbps/5Mbps plan with FiOS, I should have been getting a much faster download. Terry told me that the was heavy demand on their servers with users having to manually download McAfee Security Center.

So after reinstalling McAfee Security Center, nothing was fixed. Thunderbird would only work if email protection was disable. Terry then asked me to turn off the PC and power it back up with the F8 key pressed down. I asked why, and he said that we would need to boot up in Safe Mode to see if the email would work without McAfee Security Center running. I made the point that it would be a waste of time since we already new that it work when email protection was disable. Terry made it clear that this step had to be followed. To make a short story long, that didn't work either.

Terry then put me on hold to talk to another support person. After a minute or two on hold, Terry came back to say that this was known issue and an updated would be issued through the McAfee update process within 24 to 48 hours. The work around is to disable email protection and try again in 2 days.

At this point, I have better than an hour and half sunk into this phone call. I told Terry that I was upset that I went through uninstalling, downloading, reinstalling, and rebooting into Safe Mode for an issue that they already knew about. Terry then told me that reinstall had fixed the problem all that reported it. There were a couple others that were not fixed and an update would be coming for them. I then asked Terry how he could use "all" in one sentence, but indicate "not all" in the next. Terry did not understand that question so we ended the call at that point.

At this point I have a lot of respect for Verizon FiOS tech support and almost none for McAfee. I pretty much got what I paid for, no question about that.