I used to much prefer IBM AC, but it frequently led to problems similar to yours. After reading the posts here, I finally not only turned IBM AC off, I removed it. I never established a definitive diagnosis of the problem, but it *seemed* like the TP software and Windows (WXP SP3) were contending over who would control the connections. Evidently Windows *must* do some of that and it or AC or both would not hand off to the other properly. Sometimes I could avoid a reboot by clearing all the buffers (netconfig reset or something; sorry it's been so long since I did those "hacks"). Especially because IBM AC couldn't handle the more advanced security connections (WPA2 etc.), I had to use Windows to establish secure connections at University, businesses, etc. Once I dumped AC and resigned myself to using MS Windows connections exclusively, I have never had any of those problems again. W7 has been even better than WXP: faster, easier, and automatic, seamless switching of profiles. Sorry I didn't solve that problem; I was only able to avoid it. max
On Thu, Jan 17, 2013 at 1:27 AM, Jeffrey Race <jr...@attglobal.net> wrote: > Problem as follows (on T43 WXP) using IBM Access Connections > > 9 a.m. Use profile 1 associate with wifi AP 1 -- good > > 5 pm Disconnect successfully, close QCWIZARD > > 6 p.m. Plug in to wired LAN -- good > > 9 p.m. Unplug from wired LAN > > 10 p.m. Use profile 2 associate with wifi AP 2 -- "Connection Failed" > !!! > "waiting for IP configuration" times out > > 10:05 p.m. Reboot WXP > > 10:10 Use profile 2 associate with wifi AP 2 -- good > > Why do I fail to be issued IP address? > > How can I avoid the current requirement to reboot when I > move to a different AP? > > > > _______________________________________________ > Thinkpad mailing list > Thinkpad@stderr.org > http://stderr.org/cgi-bin/mailman/listinfo/thinkpad > _______________________________________________ Thinkpad mailing list Thinkpad@stderr.org http://stderr.org/cgi-bin/mailman/listinfo/thinkpad
