Access Connections 3.81 and Wireless Zero Configuration issu

[gerdh]

Hello,

I have three IBM machines running:
T40 2373 92u
a) with IBM Philips-make 801.11ab MPCI card;
b) with IBM Atheros-make 801.11abg (II) MPCI card
X31 2672-cbu - Intel centrino 801.11b MPCI card
X41T 1866-6TU with IBM Atheros-make 801.11abg (II) MPCI card
- all machines run XP Pro SP2

I usually have recent drivers installed; so:

with Access Connections 3.81, the wireless connections connect and drop off after about a minute or so, on and off: the connection terminate because Windows tries to connect again. Actually, on all machines after install and on the factory image; Windows Wireless Zero configuration Service features "Automatic Start" and is running -> on the Wireless network connection Properties, "Wireless Networks" register card is present and "Windows will manage your connections" is checked (!) - this seems odd.

I would expect this register card to be greyed out passive and Access Connections to be the only client SW to manage the connection.

Once I stop the Wireless Zero Configuration Service, AC works fine and as expected.

Any recommendation very appreciated how to fix this. Maybe it ain't broke (it's a feature?)

Gerd

[briank]

I think you're on the right path with the Wireless Zero Config.
http://www.math.uwaterloo.ca/mfcf/compu ... ss/xp.html
http://support.microsoft.com/default.as ... -us;826942

WinXP SP2 fixes the problem but I think it does the same thing you can do by manually changing the WZC settings.

[GomJabbar]

Once I stop the Wireless Zero Configuration Service, AC works fine and as expected.

Any recommendation very appreciated how to fix this.

Only the obvious. Go to Start > Control Panel > Administrative Tools > Services, then go to the Wireless Zero Configuration service, Stop the service and set to Disabled.

[gerdh]

The point I was trying to make is that IBM ships the machines with Windows XP SP2 and Wiress Zero config Service "Automatic" and running and Acess Connection Wireless Client running on top. It should work, but does'nt.

The error first comes with a confusing behavior, but then I got following impression:

After a cold start, this seems to work fine; however, once you standby or hibernate the machine, the Zero Config Service and Access Connection have a mismatch and trouble starts, Connections build up and drop off after a few moments.

It's just the X31 with Intel 801.11b card that manages to stay sync even after standby or hibernation and does not show this problem.

In have this behavior with both the IBM 11ab MPCI card and the IBM (Atheros) 11abg (gen) II MPCI card and AC3.81. Why do I have to run XP with a modified, stopped service as a patch? I disabled the "Automatic profile switching" and reworked my Access Points twice (signal booster, high-gain antenna, firmware update, etc...ok, this is always helpful). By now, I can truly say that it was not a "Zero Config" experience.

I also like AC 3.81 and would not like to roll back because in 3.81 you get much more info to what the root cause of trouble is compared to older versions where you had to use your own set of tools to go figure.

Anyone else with this experience or is it just me?

Gerd

[GomJabbar]

Wireless Zero Configuration service is a Windows method for managing wireless devices. If you have other software (such as Access Connections) that performs this service, there is no need to have both services running. I do not consider disabling Wireless Zero Configuration service 'a patch'. At any rate, the service is always available if you decide you need it at some future date. You are not uninstalling the Wireless Zero Configuration service.

BTW, Microsoft has patches and hotfixes for certain problems that may come up. A patch is not necessarily a bad thing.