Bill, We have seen the same problem. XP is very aggressive to re-DHCP when it loses it's network connection. We haven't explored the issue long enough to determine what can be done about it.
This seems to be a XP issue, not a BlueSocket issue. Hope that helps. -Steve Schallehn Iowa State University At 10:05 AM 10/31/02, you wrote:
We are currently proving the concept of utilizing BlueSocket aggregation devices (or similar) to give us seemless wireless connectivity across our campus. We are investigatinbg this route as our architecture standatrds will not accomodate a separate VLAN for wireless that spans multiple buildings. We are are observing is that with Windows operating systems (Including WINCE 2002) prior to WINXP, the BlueSicket device is working as advertised in providing hand-off of auhtneticiated connection from one building switch to the next. However with WINXP, the momentary loss of signal when transiting from APs is enough to cause WINXP to react to a "network media failure", release the IP address and immediately request a new IP address. While this is not an issue where the APs are located on the same subnet and the probability of same IP address use is high, but for APs on different subnets, the same IP address is not returned and the BlueSocket device cannot maintain the tunnel it created to allow the roam. Question is: anybody else seeing this? Anybody trying this technique with Vernier and not having the problem? Bill Paraska Director, University Computing and Communications Information Systems and Technology (404) 651-0881 ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/memdir/cg/.
********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/memdir/cg/.
