Have been running 64-bit 7 for months with no issues using WPA2-AES with PSKs.
~Patrick
On Sep 28, 2010, at 3:48 PM, "Linchuan Yang"
mailto:lichu...@alcor.concordia.ca>> wrote:
Many of our windows 7 clients have this problem. We found a solution: in the
“Network Properties”, go to the “Securi
Ding,
A big flat network is only attractive until you have many users on it that
destroy the quality of service.
We ran a big flat network with over 4000 users and eventually moved away from
it.
You can live with the big flat network but you have to constantly filter new
broadcasting protocols
We have several wireless VLANs using /21s for each building, no issues
so far.
On 9/28/2010 4:21 PM, David Gillett wrote:
We use several /20 and /21 VLANs across each campus, with traffic
generally routed only if it needs to reach another VLAN (or campus).
We DON'T, at Aruba's recommend
We use several /20 and /21 VLANs across each campus, with traffic
generally routed only if it needs to reach another VLAN (or campus).
We DON'T, at Aruba's recommendation, do that for our wireless services,
instead deploying them in multiple /24s (several assigned to each SSID). If
I recall c
Many of our windows 7 clients have this problem. We found a solution: in the
"Network Properties", go to the "Security" tab, there is a button named
"Advanced settings". Play with the check box of "Specify authentication
mode": some clients should check it, and others should uncheck it.
Good l
I posted with a gmail account before, but there is no response. Now I am
reposting w/ my edu account, and would really appreciate your opinion on this.
Hi All,
We are thinking of migrating our captive portal wireless network to dot1x
mobility wireless network.
Given that we will need one o
Anyone experiencing any issues with Windows 7 64 bit machines staying connected
to WPA2-AES enabled WLAN. Specifically the client associates and authenticates
properly, is assigned an IP. Shortly afterwords client is repeatedly prompted
to enter their credentials. Disabling the client wlan int
I've read anecdotal accounts that some NIC drivers default to 00:11:22:33:44:55
when an error occurs or when it's unable to determine/set the true Mac address,
I didn't think that parallels would generate a fake nic though..
---
Justin Hao
On Sep 28, 2010, at 2:39 PM, "Hanset, Philippe C" wrot
One more piece of info on the 00:11:22:33:44:55 weirdness:
We have a user registered in NetReg with MAC address 00:11:22:33:44:55,
It is an Imac and was registered on our network in Parallels (browser reference
is Windows NT 6.1).
I wonder how many of these strange MAC addresses are generated by
you can also run android on a jailbroken iPhone, though I'd wonder why.
/john
On 9/28/10 9:11 AM, "Jeff Wolfe" apparently wrote:
> We tracked one down yesterday and it turned out to be a Windows Mobile
> phone running Android. Decidedly not a MAC.. :)
>
> -JEff
>
>
> On 9/28/10 10:44 AM, And
We tracked one down yesterday and it turned out to be a Windows Mobile
phone running Android. Decidedly not a MAC.. :)
-JEff
On 9/28/10 10:44 AM, Andrew Clark wrote:
I'm seeing them here at the University of Minnesota as well. Thanks
for the heads-up! I'll see what I can discover once I can
I'm seeing them here at the University of Minnesota as well. Thanks
for the heads-up! I'll see what I can discover once I can get a hold
of one of these clients.
--
Andrew D. Clark
Network Operations Engineer
University of Minnesota, Networking/Telecom Services
2218 University Ave SE
Minneapoli
The PC should request an arp for the gateway. Do you have any arp filtering
along the path?
We had a case where some wireless array will drop arp request from windows
vista computers. Disabled the arp filtering or arp broadcast restriction
fixed the issue we had.
Schilling
On Tue, Sep 28, 201
No, it is not the base SSID.
No ARP is being sent from the WiSM. Should the PC request the ARP or should it
come unsolicited? The PC does not show any request for one.
-jcw[cid:image001.jpg@01CB5EE5.62050910]
-
John Watters
The SSID that fails is being broadcast. The issue persists across all APs and
across WiSMs and even across 6506 switches (the ones with the WiSMs). Will look
for a different NIC driver -- pretty sure they are running the latest version,
will try for a level or two back. All tablets have the same
Does the WEP ssid that is not working happen to be the radio's base BSSID? We
have a similar issue with a different vendor and different device.
I would say that you may need to end up performing a packet capture to see
where the traffic is dropped.
==
Ryan Holland
Network Engineer, Wir
Is the particular ssid being broadcast? Try a different wireless driver on the
tablets. Are the tablets showing the issue across all ap's or just a specific
model?
~Patrick
On Sep 27, 2010, at 4:40 PM, "Watters, John"
mailto:john.watt...@ua.edu>> wrote:
I need some help with a strange new p
17 matches
Mail list logo
