Vista hates my WiFi... How can I fix it?

I just made the transfer from a notebook with Windows XP Home SP2 to one with Windows Vista Home Premium SP1 (32 bit). So far, so good - aside from the headache of figuring out where certain settings and such reside. However, when it came to trying to use the wifi, I have run into a huge snag. Bear in mind that this is a connection in another - nearby - house, but I've been given permission to use it and such. I just don't get control over resetting the router or any of that, so my troubleshooting is limited.

On the notebook with XP, I could only get wifi signal if I put the computer straight in the middle of my bed. This was fine, considering the airflow was managed in the back rather than from the bottom. Though the signal was weak (usually just one bar) and it tended to take up to 7 minutes to connect, it worked properly though with frequent disconnects. But it still got the job done. The computer, according to the documentation, received wireless b and g only. I figured I'd mention that in case it's important.

On my new notebook with Vista, however, I can get wifi signal pretty much anywhere in my bedroom at two bars rather than one. However, I cannot use it on the bed due to the airflow being managed at the bottom. Suffocating a new computer: not my idea of a bright idea. So I'm limited to desk areas, but I figured that would be fine if I'm picking up signal. Unfortunately, Vista barely gives it 3 seconds to gather a response then immediately says it could not connect. When using the diagnose option, it just says the signal is weak. But I can't quite understand why it won't give it time to connect like XP did. This computer receives wireless a, b, g, and n according to the documentation. Again, such is provided in case it proves to be relevant.

The wireless connection is coming from a linksys router and is an unsecured connection. To the best of my recollection (since I've had the previous notebook for nearly 4 years, it's hard to remember) I have not changed the default wireless settings on either computer, except to disable the file and printer sharing on both and to turn off the bluetooth reception on this computer when it's not in use. The XP machine uses ZoneAlarm free firewall, but this one uses Windows Firewall (thanks to ZA deciding it wouldn't install properly on my Vista).

So I would like to know: What exactly is going wrong here? And is there some way to force Vista to wait longer than 3 seconds before throwing away its efforts to connect?

 

My guess is differences in reception/transmission between hardware. Not much you can do if it is.

 

Try going outside and closer to the house. If you get signal, you know where's the problem. You could also try a 3rd party software to connect instead of letting Vista manage your connections.

 

really? I think OS doesn't matter in wifi connection.
------------------------------------------------------
try to create a passive reflector for less than $1 of cost.
It's the cheapest way to boost your connection.

 

I'm betting it's hardware. I'd also try to use a 3rd party like Network Magic. Hope this helps.

 

Nice triple post...

 

Try disabling the wireless adapters power saver. You can do so in its properties in Device Manager.

 

Sorry it took so long to get back to this. Anyway, I tried disabling the power saver, but that didn't change anything at all. However, I did tote it outside and closer to the house where the router resides. Sure enough, it connected and ran smoothly. I tried leaving it connected and toting it back inside, and it continued telling me it was online for about three minutes before updating that it was not, in fact, receiving any signal. Still, it listed two bars for the connection even after I had proven that the location I was in had no signal.

Not to be a bother, but this sort of bugs the bejeebus out of me, getting false signal readings. Is there some way to calibrate the wireless receiver (sort of like you can calibrate a battery meter to determine the true charge)? Or is this just some sort of fluke with the router and computer interaction?

Either way, thanks for helping the best you all could. Looks like this one may actually not be Vista's fault. *GASP*

 

Sorry, NBR was messing up when I was trying to post it.