11-27-2009 06:55 AM - edited 11-27-2009 07:00 AM
We have several Lenovo T500 with the Intel 5300 AGN Wirless card. We use the latest drivers from Lenovo System Update. We have updated also the BIOS, Power Management and Hotkeys. We use Windows XP SP3 with the latest hotfixes.
We have the problem, that the T500 connects to the accesspoint but does not always receive a IP address. After several reboots it always works. We have T60, T61 notebooks running which do not have this problem.
What can we do to make wireless work more reliable with T500 notebooks?
11-28-2009 06:56 AM - edited 11-28-2009 06:57 AM
I had the same problem with my T400 running Vista. Any time the network changed the first attempt at connection came up w/out an IP address. A reboot fixed it - until next time.
What solved it was downgrading to a 5100. This was suggested by a Lenovo 2nd-tier tech after trying a different 5300.
I hope there's an easier fix, but this is what finally worked for me.
Z.
R40 XP Pro + Linux + Solaris, T43 XP Pro + Linux + Solaris, T61 XP Pro + Win 7 + VMs, T400 Win 7 Pro 64 + too many VMs to count, New T420 - a work in progress ... GeezBlog
11-29-2009 07:33 AM - edited 11-29-2009 07:33 AM
11-29-2009 07:39 AM - edited 11-29-2009 08:06 AM
Lately I'm running Win 7 64 and just using the windows tools. I will probably install AC since I like some of the extra controls it provides. I have not tested the 5300 in Win 7. I'm still using the 5100.
When I experienced the problem, I was running Vista. It did not matter if I used Access Connections or uninstalled it and used just the windows network management. The problem was the same: no IP address issued when re-establishing a connection. Once it failed a reboot fixed it. Temporarily.
[edit] Please understand that I'm not saying a hardware change will fix your problem. Only that it might.
Z.
R40 XP Pro + Linux + Solaris, T43 XP Pro + Linux + Solaris, T61 XP Pro + Win 7 + VMs, T400 Win 7 Pro 64 + too many VMs to count, New T420 - a work in progress ... GeezBlog
11-30-2009 12:01 AM
We're not using Access Connections, we use the windows tool.