3COM AP issuing new ip address to clients

[dtorres]

All of my wireless clients are equipped with a Dell TrueMobile 1550 Series wireless NIC. The are associate with a 3COM 8000 AP. I have configured the NIC cards using windows XP on the client side. They will initially connection and get a IP Address from my DHCP server and work fine. A few minutes or secconds later they are dropped from the network and assigned a random IP Address not reconized on my network. I have to then open the Wireless NIC staus icon and wait for it to get another IP address from my DHCP server. I have tried to assign a static IP address to the wireless nic but it continues to drop its connection. I have three AP's around the office so I am sure interferance isn't an issue.

Any help would be greatly apprecaited.

"D"

 

[manarth]

"I have three AP's around the office so I am sure interferance isn't an issue."

my guess is it's picking up a stray IP from a rogue AP
next time you find a stray IP, use "ipconfig /all" to discover the IP address of the provisioning DHCP server, then use "arp" to determine the MAC address of the rogue server - hopefully this should allow you to work out which device is running interference!

<marc> i wonder what will happen if i press this...[ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]

 

[dtorres]

I went through and connected to my AP's via the web interface and I was unable to connect to one of them. I ended up rebooting the AP and after that I was able to connect to it. This seemed to resolve the issue of clients getting an IP address not on my network. This morning I had a client in one of the conference rooms getting an unknown IP address and not being able to connect to the network. The client was located directly under the access point and the signal strengh was reporting weak. For what ever reason, it seems to be picking up the signal from the AP located in the center of the office that I had to reboot. I rebooted the one what was directly above the client and they connected to it just fine. I never had this issue until I began using XP to configure the clients NIC.

&quot;D&quot;