Itchy

I'm getting the itch to write some serious .NET code. It's bad enough that the new job hasn't allowed me to write anything serious in .NET (I wrote a small little utility the other day), but I've been living in the ASP/VB6 world fighting fires. Is there anything worse than having to write VB6 code? I don't think so.

What I might have to do is fire up www.examining.net again. I don't have the time and energy to turn it into the full-fledged .NET study site that I wanted to originally, but I figure I can define a series of small projects or study topics that need to be done, then attack them one at a time and post articles about them to the site.

That's food for thought, anyway. First, I have to get my home network infrastructure working. When I moved to the new house, I went completely wireless and the Win2K3 server doesn't like it. I have a D-Link DWL-2100AP access point connected to the cable modem, and a D-Link DWL-G810 bridge in the office, connected to a netgear switch. The Win2K3 server and a WinXP client connect to the switch.

The WinXP client likes this arrangement just fine. The server, however, can only see the bridge and the WinXP box. Actually, I had it working once. Just once. I don't know what I did to get it that way, and I didn't change anything after it worked, other than a reboot to install a new power strip. It's incredibly frustrating. If anyone reading this (all three of you) have any ideas, please let me know! Since I'm not able to get email at home until this is resolved, use daviskyle @ gmail.com