Now that my sound function works, and I vented about the User Access Control, let's get to a serious problem: networking. If you've never heard the phrase “DHCP Broadcast Flag” before, you're in good company. DCHP (Dynamic Host Control Protocol) is the rock-solid protocol that assigns IP addresses to devices as they connect to the network. I say rock-solid, but that's before Microsoft's bizarre configuration change turned DHPC into a source of incredible frustration. I've been fighting networks for over two decades and never, ever had to worry about DHCP before, but that was before Microsoft's incompetence with Vista.
I might be picking out which sledgehammer to use on my new computer if not for an article in Windows Secrets last week. Since I was awaiting for my HP PC with Vista, the headline “Microsoft DHCP Bugs Make Windows Lose Networking,” caught my eye. The problem described by Windows Secrets is exactly the problem I have with this new system.
When a computer or other network devices starts and powers up the network port, it must have a unique IP address to join the network. If two devices have the exact same IP address, your network gets real screwy real fast. So each device must either have an IP address configured, or ask the network for an available address. The ability to track unused addresses, and provide an open IP address to devices as needed, is one huge reason we haven't run out of IP addresses yet even though it seems every gadget in the world is now on one network or another. Thank you, private network address management gurus who built DHCP.
Every server or router type device can be a DHCP server. In small companies and home networks, the router is the most common, and logical, choice. Even the cheapest routers from a discount online store handle DHCP address management without problem.
Until Vista, that is. As DHCP evolves they've added a Broadcast Flag to newer devices. The common method for such advances is to continue support for the old model (no Broadcast Flag) while adding some extra speed or features for the newer models (with broadcast Flag).
Microsoft chose, with Vista, to use the Broadcast Flag no matter what. If you have an older router or one that doesn't support the Broadcast Flag you can't network. Worse, all Vista tells you is “network cable unplugged.”
Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world
jfruh
Apple syncing patent can't come soon enough
pasmith
New Twitter features borrow from 3rd party clients
Esther Schindler
Open Source Changes the Software Acquisition Process
mikelgan
How to set up continuous podcast play on the new iTunes
David Strom
Five important Windows 7 mobility features
sjvn
Guard your Wi-Fi for your own sake
Sandra Henry-Stocker
Grepping on Whole Words
Sidekick: The Good News & the Bad News
Either way you look at it Microsoft Data Center management did not follow standards or best practices in this failure. In which case it makes me wonder more about the outsourcing of corporate data much less personal data.
- mburton325
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.
Shooting at the wrong target
This whole series has been just another "let's crap on Vista" piece without looking at where the real problem lies.The vast majority of your issues are not with Vista at all.
In part 1 you mention problems with:
The sound card being disabled in the BIOS, a lot of whining about bundled in software, the fact that no discs were included with the unit, the fact that you find UAC annoying, an issue with the network card.
Of these problems, only the network connection being disabled is perhaps a Vista problem. UAC is what it is, and I will definitely say it could've been implemented better. However, it can be disabled if you want to do so.
The sound card being disabled in the BIOS and having no current drivers installed for the device would've resulted in no sound coming from the speakers no matter what OS you run. Both that and the fact that there are no discs in the box are the fault of the manufacturer of the system and there is no way you can blame either one on Vista or Microsoft, same with the bundled in junkware.
In part two you list a conflict between Windows firewall and Norton's. Again, this is not a problem with Vista. In XP if you have multiple firewalls running you're going to get conflicts, in OS X or Linux you'd get conflicts as well. The proper method of installing a newer firewall would be to disable the Windows firewall first, then install your new software and turn it on. If Norton was preinstalled on the system and causing issues then it is again the fault of the manufacturer for not configuring this properly beforehand. Microsoft can't be responsible for that.
Finally in part 3 you list the DHCP issue. I've installed several Vista systems and never seen this come up. Ever. I've used several different types of routers, from old wired D-Links, a TrendNet Wireless b/g router, a Hawking wireless b/g and now a D-Link Wireless N. Plus installs onto our corporate LAN. Not once have I ever encountered this with Vista Business, Vista Home Premium, or Vista Enterprise. Not to say that the problem does not exist, I'm sure it does, but it is likely an extremely rare occurrence. It appears to me that most hardware has no problems dealing with Vista's implementation of DHCP, so once again the issue looks to be at least partly the fault of the router's manufacturer.
In most cases, the problems you listed are due to 3rd party driver issues that are not Microsoft's fault. I've had similar issues where my hardware hasn't worked well with Vista, but it's not because of Vista it's the manufacturer. Vista was in development for a long time, when I installed it and my All-In-Wonder x800 lost its PVR features it was not Microsoft's fault, it was ATI/AMD who said they were not supporting these features in Vista.
When my Lexmark All-In-One printer/scanner/copier didn't work, it wasn't Microsoft's fault it was the fact that Lexmark didn't have driver's available. Despite the fact that Vista was in beta for an extended period of time, they still had not issued a compatible driver for their hardware upon its release.
Vista is not without issues but the vast majority of what people call "Vista problems" are not "Vista problems" at all. The media has given Vista a much worse reputation than it deserves by misinforming the masses as to where the issues really lie. Your articles are perfect examples of this.
Shooting response
I hoped to make it clear some of the problems can be blamed on HP. But for most small business users, it's hard to tell whether the hardware or software vendor is to blame.Read the summary and see if you still believe I'm unfair to Vista.
James