Monday, January 17, 2005

This past weekend I worked on one of the most bizarre "tech support" issues I have ever encountered.  A friend of the family recently upgraded from dial-up-networking to DSL.  From his main workstation, he had been experiencing a problem where he could not post a form on any Web site.  He could browse or download, but submitting a form, such as logging in to his web-based e-mail account or completing a contact form, would not work.  The browser would simply "hang" and never complete the action.  Now begins the troubleshooting steps.

  1. Does the same problem occur in other browsers?  Yes.  Internet Explorer, Netscape, Opera and Mozilla Firefox all exhibit the same problem.
  2. Does the same problem occur on other computers on the network?  No.  Other computers on the network have no problem at all submitting forms, signing in to web-based e-mail, etc.

At this point, I'm thinking the problem must be spyware or some other Internet component that has injected itself somewhere in the TCP/IP pipeline.  However, every anti-spyware and anti-virus utility reports the system is clean.  I try removing every bit of software on the PC that might use the Internet for any reason.  I clear the Startup, Run, RunOnce, stop services... nothing I try fixes the problem.

Okay... only thing left is to format and rebuild.  The computer is running Windows 2000 Pro, and we've already talked about upgrading it to XP Pro SP2.  So, I back everything up -- twice.  Some things I actually back up three times.

Format.  Load Windows XP SP2.  Open Internet Explorer...

SAME PROBLEM.

What is going on here?!

At this point I'm thinking, as bizarre as it may sound, the problem must be in the network card or cable.  We don't have an extra cable or card lying around, so we decide to break for a road trip and grab some dinner.  An hour later we're back with our bag of goodies.

Does changing the cable fix the problem?  Nope.

Does changing the network card fix the problem?  Nope.

The only thing left is the Linksys DSL/cable router.  Since the other computers on the network don't have a problem, I try switching ports.  Still doesn't work.  Now I try bypassing the Linksys router and go directly to the DSL modem.  Guess what?

IT WORKS!

However, my problems aren't over.  I go to the Linksys web site and, of course, there is a firmware upgrade for the BEFSX41.  Unfortunately, I can't download it.  I go to another computer.  I can't download it there, either.  I start searching the Internet and discover (along with quite a few colorful comments on what users think of Linksys) that no one else can download the upgrade, either.  Finally, I find a kind soul has posted a good link to the firmware upgrade hosted somewhere other than Linksys.  I download, apply the upgrade, and...

IT WORKS!

Now, how do you explain that?  What could have been going on with the router that prevented that particular computer from submitting a form??

"When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth." -- Sherlock Holmes

Monday, January 17, 2005 3:50:00 PM (Central Standard Time, UTC-06:00)  #    Disclaimer  |  Comments [1]  | 
 Thursday, January 13, 2005

Thanks to Josh, I discovered and subscribed to two very cool blogs today.  I think it's awesome and very encouraging to see that people involved in full-time ministry are "getting it" and using their blogs as part of their personal ministry.

I'm looking forward to absorbing these great resources :)

Thursday, January 13, 2005 1:48:00 PM (Central Standard Time, UTC-06:00)  #    Disclaimer  |  Comments [1]  | 
 Friday, January 07, 2005

JavaKid posted "Microsoft Certified? ... Not Impressed!" to which I responded.  I thought I would re-post my response here, in case anyone is interested in my view on the value of certification.

I agree that judging a candidate's skills and qualifications for a job based on their certifications is a bit absurd. No industry exam is going to be able to cover the practical skills needed for any given job. I also agree that Microsoft has been notorious for using its certifications to promote technologies and methodologies that went (or are going) nowhere. Does anyone remember Visual Basic ActiveX Documents (*shudder*)?

However, I believe that certifications, including Microsoft's, do have merit. What are they good for?

1. They help you get your foot in the door. Some employers faced with a pile of resumes may choose to use certifications as a filter, or they may place high value on certifications if they already have high-performing employees with certifications. When comparing candidates and all things considered equal, the candidate with a certification may have the edge.

2. Studying for a certification forces you to learn more about a technology (or different aspects) than you might otherwise learn on your own. When I was an NT administrator, I learned tips and tricks while studying for the MCSE exams that had a direct impact on my job. Studying for the MCDBA forced me to learn more about SQL security, which I would have probably never learned on my own, since I spent almost all my time developing databases, writing stored procedures, and so forth.

3. When I'm interviewing a potential candidate, a certification speaks volumes to me -- not in terms of technical skill, but in terms of aptitude, ability to set and obtain goals, and self-discipline, especially if the certification was obtained through self-study. Asking a candidate how and why they obtained a certification might give you an indication of their character and dedication towards a technology.

Obviously, some employers value certification more than others. My personal experience from both sides of the employment table is that certification is very much a worthwhile investment.

Oh -- maybe you should know that I worked for Transcender for three years, so I'm a little biased towards certifications ;)

Friday, January 07, 2005 10:40:00 AM (Central Standard Time, UTC-06:00)  #    Disclaimer  |  Comments [0]  | 
 Friday, December 31, 2004

I think this is very cool.  Bob Parsons, the founder of GoDaddy and original founder of Parsons Technology has started a blog.  I've highly recommended GoDaddy in the past because of their awesome prices and service, as well as knowing that Parsons Technology was originally responsible for great family and Christian software products including QuickVerse and Membership Plus.  After reading Bob's blog, I'm all the more eager to recommend GoDaddy for domain registration and any of their other services.

Friday, December 31, 2004 9:22:00 AM (Central Standard Time, UTC-06:00)  #    Disclaimer  |  Comments [7]  | 
 Saturday, December 25, 2004

Just wanted to take a minute to wish everyone a Merry Christmas!  Read about the birth of Jesus Christ in Luke 2:1-20

Glory to God in the highest, on on earth peace, good will toward men.  -- Luke 2:14

Saturday, December 25, 2004 4:33:00 PM (Central Standard Time, UTC-06:00)  #    Disclaimer  |  Comments [0]  | 
 Tuesday, December 21, 2004

Whether your primary .NET language is VB.NET or C#, a good reference that compares equivalent syntax can really help you with code samples or the occasional project that requires you to step outside of your "comfort zone."  Below are a few resources I have run across.

Update: Language Equivalents on MSDN (courtesy of Josh)

Tuesday, December 21, 2004 7:53:00 AM (Central Standard Time, UTC-06:00)  #    Disclaimer  |  Comments [2]  | 
 Monday, December 20, 2004

A friend of ChristianASP.NET sent me these links last week.  You could use one of these Web Services to pull Bible references into your ASP.NET (or any .NET) application, such as a verse-of-the-day or reference search/lookup.  Wouldn't a tutorial on how to use these Web Services be great?  Well, I'm thinking about...

King James Version
http://www.webservicex.net/WS/WSDetails.aspx?WSID=6&CATID=11

American Standard Version
http://www.francisshanahan.com/Bible.aspx

Thanks Eric!

Monday, December 20, 2004 1:46:00 PM (Central Standard Time, UTC-06:00)  #    Disclaimer  |  Comments [1]  | 
 Friday, December 17, 2004

I'm now on day 3 with the Audiovox PPC-6601 from Sprint.  Overall, I think I made the right decision.  The screen is very nice, and seems to be more clear and have better contrast than my Viewsonic V37.  I think the keypad on the Treo 650 is better, but the slide-out keypad on the 6601 in exchange for more screen real estate is definitely a plus.

Exchange ActiveSync works like a champ, and I also have a POP3 account set up.  It's so cool to be driving down the Interstate, receiving and reading new e-mails, all the while oblivious to other drivers honking and careening out of the way.

You definitely need a headset for making & taking calls.  The phone is just a little too big to feel comfortable next to your face.  I feel silly every time I make a call in a public place.  Plus, there's the greasy smears and dusting of beard crust on the screen when I'm through.  I suspect even if you've just scrubbed your face with Noxzema (which I apparently need), you're going to leave smears on the screen.  The included stereo earbuds and microphone work very well.  Man, I gotta start cleaning my ears, too.

Speaking of earbuds, I loaded up a few MP3s.  It works, but the sound quality leaves a little to be desired. 

I was disappointed that the battery only lasted 9 hours yesterday.  Of course, I had used it quite a bit making calls, surfing the Internet, and letting my co-workers handle it.  I definitely need to get another cradle for the house, or at least a charger.  Unfortunately, I've had a hard time finding accessories.

My next goal is to try out the bluetooth support.  From what I've read, it's possible to use the phone as a modem.  May laptop doesn't have bluetooth, so I need to buy a USB adapter.  I'd also like to try one of those bluetooth headsets.

The phone has locked up on me a few times, requiring a reset.  That disturbs me.  I'm also a little bummed out that it doesn't have a built-in camera.  I guess you get what you pay for.  Hey... wait a minute!

PPC-6601 Update: Here's a picture.

Friday, December 17, 2004 1:08:00 PM (Central Standard Time, UTC-06:00)  #    Disclaimer  |  Comments [0]  |