maybe you can use a different app to control the wireless connections,
like the intel app.
Maybe it has better control over the spontaneous connections?
I was under the impression windows doesn't auto connect the first time
out, but after
the first connection, then it will auto connect to the specific AP.
ah... in the wireless networks tab on your connection properties,
there is and "Advanced" button.
On that screen there is a check box for "Automatically connect to
non-preferred networks".
clearly you'll want to make sure that isn't checked. There are three
other options there too.
You might be able to use one of them.
You can also go into the preferred networks and click the properties
of the one you don't want, maybe
add some settings that will cause it not to connect. Like give it a
WPA key, which won't work, then it won't
connect?
bb
On Wed, Jul 29, 2009 at 3:36 PM, Brad Bendily<bendily@gmail.com> wrote:
> put baby monitors in strategic locations around the office!
>
>
>
> On Wed, Jul 29, 2009 at 3:33 PM, Chris Jones<techmaster@gmail.com> wrote:
>> I have an issue with a client, I was wondering if any of you have ran
>> into this before, and if you know of any way to prevent it. I've done
>> a ton of research, and have gotten nowhere.
>>
>> My client has a secure internet connection. A lot of their employees
>> have laptops. They have a filtering device that blocks viruses,
>> spyware, spam, etc from getting into their LAN, plus it blocks the
>> users from accessing inappropriate sites from work.
>>
>> The problem is they have a neighbor with a wide open wireless AP, so
>> the employees just get on that and can then do whatever they want.
>> I'm not sure if they're doing it intentionally, or it could just be
>> Stupid Windows (TM) being insistant on connecting to SOMETHING. The
>> fact that they can spend all day on myspace or looking at porn is the
>> minor issue, the major issue being that it is an opening for malware
>> to come into their network, not to mention that it's possible for a PC
>> to route traffic between its WAN and LAN ports, so it could possibly
>> become a security issue as well.
>>
>> From what I can see, there's absolutely no way to do it, which is
>> insane. Windows has a group policy that can block acess to ad hoc
>> networks, but that's about as far as it goes. Apparently MS believes
>> that an AP is far more secure than an ad hoc network.
>> ___________________
>> Nolug mailing list
>> nolug@nolug.org
>>
>
>
>
> --
> Have Mercy & Say Yeah
>
-- Have Mercy & Say Yeah ___________________ Nolug mailing list nolug@nolug.orgReceived on 07/29/09
This archive was generated by hypermail 2.2.0 : 08/06/09 EDT