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

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)]

I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent!

I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around.

Thanks in advance!

Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario...
I'm workin…

Shrinking WSS (Sharepoint) SQL Server Log Files

Yesterday, while migrating a source repository from StarTeam to TFS, I received the following error:
"TF30042: The database is full. Contact your Team Foundation Server administrator."Excuse you? Sure enough, my 100+ GB drive was full on the server. But I'd only migrated around 1000 items. Surely SQL wasn't consuming 100MB per file.

Turns out (yes, there was a lot of crud on the drive but...) the majority of the space, almost 40GB was being consumed by the Windows Sharepoint Services WSS Content data and log SQL Server files. Huh? I still need to investigate and understand why this portal, which is 100% unused, grew so large. Regardless, here's what I did to resolve:

Since this is not yet a production database, I flipped the SQL recovery option from Full to Simple for WSS Content and several other databases. Detail here and here.
Executed the maintenance plan for all the databases to get backups and clear out some of these files. That didn't help much. The Auto_…