Aspire E13: ES1-311-P87D / Problems with WiFi-Adaptor Broadcom 802.11n

Heinzi22

Hello,

my aforementioned machine, while generally running OK under it's OnBoard-System Win 8.1 / 64, in one respect virtually makes me mad from the very start, concerning it's WiFi-Adoptors way of working (or not-working) in some special respect. Things being OK with wireless networking as far as standard access points (via Routers) are concerned, this godd. unit makes one go up the wall trying to build local, peer-to-peer-based, so called hostednetwork-connections to one or more WiFi-equipped machines nearby. Further relevant data concerning the machine's system might be: Driver-Date 2014/07/13 & Driver-Version# 6.30.223.250.

The wickednesses, ordered by gravity, are as follows:

- Starting the device in an aforementioned, properly defined context by entering .. \: netsh wlan start hostednetwork into terminal (and therefore getting built the desired connection) generally only works about 2 times a year without any problems at all. The regular case instead being the system to report proper starting, but lacking any reaction of the counter-machines, additional devices for testing purposes (like a cellphone) simply stating the unit / the network being out of reach. This situation occurs without any relevance concerning the distance between the units, regardless of being 10 centimeters, 10 meters or whatever,with about tenfold calling for starting and stopping the device by the corresponding sequences in order to get it up and running in the end, even including wireless networking's complete switch-off and activating it again. On this background I would infer the problem being localized in the machine, its WIFi-Adaptor or its configuration (only being changed in order of testing those values that seemingly hint towards power-management issues).

- After having got things running, the problems regularly do not stop. Although sometimes the connection then stays alive as long as needed and even for hours, far more often it collapses again after short amounts of time. Occasionally already after 10 sec, in other cases maybe 5 minutes or 15, whatever, then after some additional time establishing the connection on its own as is preconfigured.

Some points and observations might be of relevance now:

- Setting the System's general power configuration to a value like "balanced" (instead of "maximum"), things are completely bad (again with the exception of accessing regular access-points like routers, things running w/o problems then).

- Any time the hostednetwork-connections (as mentioned) collapse, a look onto the list of available WiFi-Networks (containing about let's say 10 items during startup) then only shows 3 or 4 (of formerly ten) being left. That happens without having been switched off by their owners, since after deactivating wireless networking & switching it on again, all 10 items appear again just like before. In quite a number of cases then the hosted-network connection is re-established too.

Assuming some power-management adjustment being at issue here, up to now I got no Information at all (concerning the operating system / it's vendor), which the point of interest might be in order to cure this annoyance.

Anyone ideas?

Many greetz

Heinzi

JackE

Open Device Manager. Network folder. Right click Microsoft Virtual Wifi adapter. Click properties. Power management tab. Try disabling power saver mode by unchecking box. Jack E/NJ