** Description changed:
The iwlwifi drivers give exceptional performance on all APs I have
connected to, be they WEP, WPA or open. The only time this system lets
- me down is when connecting to my campus wireless network. Newtwork
- manager will only sometimes connect, and even manually config
I've been experiencing this same problem on my campus network for a
while, and switching to WICD seems to have fixed it for me, too!
I think it's worth noting that the access points on my campus are Aruba
Networks access points, and we use the SafeConnect system for network
authentication. We act
I can confirm that switching to WICD fixes the problem for me partially
- I see a large number of APs for the same SSID, and can always connect
to at least one of them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
This bug affects me too. Can anybody confirm that wicd solves the
problem?
Cheers,
S.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924082
Title:
Intel Centrino 6300 Cannot connect direct probe tim
I can confirm this bug. I have an intel advanced N 6320 card and I get
the same direct probe failure messages on my campus wifi. The network
works fine in windows and on my phone/tablet, but I cannot connect when
using network-manager. I'll try wicd as suggested to confirm the issue
is in network-m
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924
When I was using network-manager, I could connect fine to every network except
the campus network, which is composed of a ton of APs everywhere. When trying
to connect to the campus network I would usually get the following:
[ 12.059405] wlan0: direct probe to 00:24:6c:60:d0:00 (try 1/3)
[ 12.258
Sorry -- there's just really nothing in that bug report that supports
this. If you can, please test with a different card or whatnot, but
there's still no reason to believe a success might then be because it's
the different card. Didn't you mention you sometimes successfully
connect?
Stating the d
The only thing is - this is a problem in network-manager. My previous
network card had no trouble, and having installed wicd I have never seen
this problem. I don't think that this is an overcrowding issue, and that
there is still an issue with network-manager.
--
You received this bug notificati
Thank you for filing this bug report and helping to make Ubuntu better.
Your syslog excerpt explains precisely why the connection times out and
authentication is denied while trying to connect: there's an error
response from the accesspoint, in the form of the "status 17" message.
I understand th
10 matches
Mail list logo
