Wifi works in bootcamp Windows XP but not in Leopard

[writeous]

Im currently experiencing a problem with my wifi connection. It works while im at home on my secure connection, but when on an unsecure one, it only works for about 20 mins, then it times out. It shows that its still connected, but nothing works on it. The sad part is that when I run windows xp, it works fine. Is this something common with Leopard?

[Neutral Gamer]

There's quite a few people who have been having wireless problems with Leopard while Tiger, Windows and Linux exhibit no such problems on the same hardware:
http://forums.macrumors.com/showthread.php?t=392852

On that thread though I'm sure most people complain about the connection dropping either after a very short amount of time or when they try and download a large file. Your lasts for 20 minutes which means you may have some other problem.

However, it may be worth you trying out the following steps that I did which made my connection a lot better (still not perfect though):


1. In Network Preferences click on the Airport section on the left.
2. Make sure Location is Automatic and "Ask to join new networks" is unselected.
3. Click the Advanced button.
4. Make sure your network is in the Preferred Networks table. And make sure when you created your network before that you selected "Remember this network".
5. Tick "Remember any network this computer has joined"
6. Untick the other two options.
7. In the TCP/IP section set "Configure IPv4" to "Manually".
8. Put in your local IP address for "IPv4 Address".
9. Put in the Subnet Mask from your Router's configuration web page. (Mine was 255.255.252.0).
10. Put in the IP address of your Router - again you can find this from your Router's configuration web page.
11. Set "Configure IPv6" to "Off".
12. In the DNS section remove all the DNS Servers and add the ones that again should be found in your Router's configuration web page. (For me it was 194.168.4.100 and 194.168.8.100).
13. Press OK and then press Apply.


If that doesn't work then there's quite a few of us hoping that the 10.5.2 update will fix the problem, any day now ... :D