On Fri, 02 Jul 2004 23:33:17 GMT,
arthur-temp-(E-Mail Removed) (Arthur
Shapiro) wrote:
>About the only other fact is that the T30 is Win 2000, whereas all the other
>machines are XP Pro.
I have a customer with an IBM T30 running Windoze 2000 that had a
similar but not identical problem. I don't recall exactly which DLink
card he was using. He would successfully connect to his office LAN
and get a DHCP supplied IP address. However, when he went to lunch at
the local restaurant (that has wireless), he had to run:
ipconfig /release
ipconfig /renew
before his machine would dispose of the office IP addresses and pickup
a new IP address from the restaurant. It seemed to want to hold onto
the old IP address. When he goes back to the office, he has to do the
same proceedure again.
Later, we discovered that simply unplugging the wireless card, waiting
a few seconds for Windoze to complain, and then plugging it back in,
seemed to have the same effect without manually renewing the IP
address.
I realize that you said your Cisco card didn't "connect". I'm not
sure what you mean by "connect". Did it fail to associate? If you
can see the SSID of the access point, you've successfully associated.
If not, did it fail to deliver a valid IP address? Run:
Start -> Run -> cmd
ipconfig
If the IP address is 169.254.xxx.xxx, you didn't get an IP address
from the wireless router.
If you're running some kind of personal firewall (Zone Alarm, Norton
Firewall, McAfee Firelwall, etc), turn it off to see if it's getting
in the way.
--
Jeff Liebermann
(E-Mail Removed)
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060 AE6KS 831-336-2558