Skip to main content

Wi-Fi under Vista

We just bought my wife a new Dell Inspiron 1525 for her business. It came with Vista Home Ultimate. This is our second computer with Vista and for the most part, I love it and haven't had any issues--except for wireless configuration.

Home
We have 802.11 pre-n at home so I configured it with all the security bells and whistles. However, oddly, I had to dumb down to WPA-Personal from WPA2-Personal to get the 802.11g laptop to connect. I'm still not sure why but WPA2 just wouldn't fly. This was also true for my Dell desktop talking 802.11g.

Public
I enjoy working at Panera from time to time: good snacks, quiet (relatively...compared to my house and work environments), and the Wi-Fi is decent (and free). My wife brought her laptop there recently and I could not for the life of me get the 1525 connected to Wi-Fi. I couldn't even get Vista to tell me what networks were available. Both my other two 802.11g laptops under XP connect just using the "View Available Wireless Networks" dialog.

Vista annoys me from a wireless standpoint because, coupled with Dell's proprietary dialog, there are at least four areas in which to configure wireless. What? With all the fancy wizards and usability, why do I need to visit three different spots?

Finally, I gave up and started trolling Google. Didn't find much there either. After bringing it home, I started from scratch: Start >> Network and boom. There it is: Network browsing and file sharing is not enabled... Hello! Where were you before? I swear it wasn't there. So, that was my issue. Enable this and the rest is downhill.



I'm all for features disabled by default for security but the help documentation should have highlighted this as one of the first steps to try in diagnosing the issue. Nope.

Well, it's probably because I'm dense but if you run into this issue, now you know. Happy [un-cabled] browsing.

Comments

Popular posts from this blog

TFS Error | The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception.

Posting this one for the search engines. If you ever receive the exception "The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception.", more than likely, your drive space is at 0 on your TFS application tier box.

I encountered this at a client recently. The root cause was that IIS logs had filled up the OS drive (C:\). I switched IIS logging to the applications drive (D:\) which cleaned up the OS drive and resolved the issue.

Detailed message:


TF53010: The following error has occurred in a Team Foundation component or extension:


Date (UTC): 6/7/2011 4:18:53 PM

Machine: TFSATBOX

Application Domain: /LM/W3SVC/8080/ROOT/tfs-1-129519118182628600

Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727

Service Host: 7ecfbd77-b386-4d75-b038-b05474782696 (DefaultCollection)

Process Details:

Process Name: w3wp

Process Id: 3676

Thread Id: 5752

Ac…

Verified by Visa: Everything We Tell Folks to Avoid

Phishing is defined by F-Secure as: "Fraudulent e-mail or website claiming to be legitimate seeking indentifiable information. Phishing is an attempt to steal your personal data."When I recently attempted an online purchase from WalMart using my VISA card, being a security wanta-be, I immediately thought phishing when redirected to verifiedbyvisa.com and saw this dialog:

Seriously, these folks have to be kidding. You're asking for my personal data during a transaction and claim that's its a service "...at no additional cost." Wow! Thanks...but absolutely not, you jokers. As a malicious thief, I can go a long way with this data.

This is exactly the type of experience which aids malfeasance and the folks trying to steal personal data / identities. How long have we been working to educate folks to avoid providing this type of data under these type of circumstances? Years. And we're just now starting to turn the corner.

VISA, get rid of this! When folks submi…

Windows 10 Creator's Update and Office Conflicts

Recently, Microsoft pushed the "Creators Update" out to Windows 10. It was available in April but it seems to have been force-pushed in the past 2 days. On my mother-in-law's computer, Creator's caused Excel to render a "Bad Image" message when attempting to start declaring "MSVCP140.dll is either not designed to run on Windows or it contains an error". I attempted the SFC and DISM repairs as advised on Tom's site to no avail. When I attempted an Office repair, Office disappeared completely. At this point, I definitely started to panic.

Fortunately, I noticed a pending reboot due to an install/update. Allowing Windows to install that update and rebooting twice brought Excel and Office back to life. I did have to re-register the software but all is well now. If you encounter this issue, stop what you're doing and install/restart Windows. Anecdotally, I've since hear of many folks encountering similar issues.