Stupid Windows Networking
I really don't like running most of my systems in DHCP mode, because I port forward a lot of stuff at various times (things like the PVR Video Sharing forwards and any games I want to host, etc). But this latest install of XP is really pissing me off. I set it to a static IP address (still in the same netmask and out of the DHCP assignment range) and it can't connect to the internet anymore. I've noticed that my laptop has always had issues with dropping connectivity, and it always seems to stem around the fact that it has firewire and windows wants to try to install a bridge between the firewire and the lan card (and that typically is where things go bad). But you can't remove the bridge or it all goes to hell. So, I just have to run the "network wizard" and each time, it is a little different on the outcome (stupid freaking wizard). I'm sure if they would just give me direct access to this stuff, it would work, but Microsoft always does its best to bury advanced setup stuff (which probably helps mom and pop, but it really irritates me). Anyway, now, I can't even figure out HOW to get back into the TCP/IP properties window to change it to static. I think I lost TCP/IP all together, because it won't pull up from the same location it did just a couple hours ago.

Seems like Windows networking has always sort of been, "problematic", at best (attrocious on Win98, got better with SE and ME, and XP has actually been pretty reasonable, except for the problems noted above). This is probably just another arguement for Jason and Daryl to justify why I should move to Linux, but oh well.

- posted by Jeff @ 8:25 AM | 0 comments