Clean install ubuntu 16.04 cannot connect to wifi using NetworkManager, but nmtui worksWireless is Connected but No access to Internet 12.10Ubuntu 13.10: Can't connect to WifiWi-Fi connected but no network accessrtl8192cu and Alfa AWUS036NHR v2 cannot connect to any networkWifi Connection Issues on Ubuntu 16.04Connect/Disconnect cycle with ALFA Networks AWUS036H in Ubuntu 16.04-64bitWifi extremely slow on ubuntu 16.04, tried almost everything and still not working properlyUse USB wifi instead of internal - manage
A bob hanging in an accelerating train moves backward. What is the force moving it backward?
C - wrapping globals in a struct?
Why is SpaceX not also working on a smaller version of Starship?
Can span be constexpr?
Threatening to discontinue a service for a client
How can I speed up secure erasing of a disk?
What happens when a land attacks then stops being a creature?
Rats biting off fuel line ( again and again and again )!
"the whole shabang" vs "the whole shebang"
Failed to call the method because [Sitecore.Data.Items.Item] does not contain a method named "op_Addition"
Translate the French quote "Il n’y a pas d'amour, il n’y a que des preuves d’amour" to English?
Where to stand for this winter view in Grindelwald, Switzerland?
Why do some journal proofs insert dozens of typesetting mistakes?
How to write ODE for matrices?
Why does this process map every fraction to the golden ratio?
Contacted by head of school regarding an issue - should I be worried?
Do gray aliens exist in Star Trek?
Match blood types in C
Should I present forged documents in a Penetration Test/Red team engagement?
Why does the hyperref documentation suggest using gather instead of equation?
How can medieval knights protects themselves against guns?
Can a Barbarian/Wizard multiclass cast a spell with a magic item while raging?
Transferring $ from LLC to Personal account
What is a flight ticket coupon?
Clean install ubuntu 16.04 cannot connect to wifi using NetworkManager, but nmtui works
Wireless is Connected but No access to Internet 12.10Ubuntu 13.10: Can't connect to WifiWi-Fi connected but no network accessrtl8192cu and Alfa AWUS036NHR v2 cannot connect to any networkWifi Connection Issues on Ubuntu 16.04Connect/Disconnect cycle with ALFA Networks AWUS036H in Ubuntu 16.04-64bitWifi extremely slow on ubuntu 16.04, tried almost everything and still not working properlyUse USB wifi instead of internal - manage
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
I've performed a fresh installation of Ubuntu 16.04 on my Asus N56VZ. Sadly, i cannot connect to wireless networks using the NetworkManager. I am able to see wireless networks, though.
I tried to connect to my network using the GUI and entered my password. But after that, nothing happens. I see no attempt to connect to this network, and I don't get an error either. I can see that the network manager saved my network, and I double and triple-checked whether the password and all other configurable parameters are correct.
Funny thing is - I am able to connect using nmtui
without any problems.
I have not been able to test whether this is a problem with this specific network or if it is a general problem. I highly suspect the latter though, as I had no problem using said network on Ubuntu 15.04.
Output of some interesting commands:
Before connecting using nmtui
:
iwconfig
enp4s0 no wireless extensions.
lo no wireless extensions.
wlp3s0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
lspci -vvnn | grep Network
03:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01)
Subsystem: AzureWave AR9485 Wireless Network Adapter [1a3b:2c97]
sudo service NetworkManager status
(after I tried and failed to establish a connectiong using the NetworkManager)
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since So 2016-04-24 00:03:32 CEST; 15min ago
Main PID: 788 (NetworkManager)
Tasks: 3 (limit: 512)
CGroup: /system.slice/NetworkManager.service
└─788 /usr/sbin/NetworkManager --no-daemon
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2249] device (wlp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2253] manager: NetworkManager state is now CONNECTING
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2265] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2270] device (wlp3s0): Activation: (wifi) access point 'FRITZ!Box 7362 SL' has security, but secrets are required.
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2277] device (wlp3s0): state change: config -> need-auth (reason 'none') [50 60 0]
Apr 24 00:18:49 Tesla NetworkManager[788]: <warn> [1461449929.2418] device (wlp3s0): No agents were available for this request.
Apr 24 00:18:49 Tesla NetworkManager[788]: <info> [1461449929.2419] device (wlp3s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Apr 24 00:18:49 Tesla NetworkManager[788]: <info> [1461449929.2422] manager: NetworkManager state is now DISCONNECTED
Apr 24 00:18:49 Tesla NetworkManager[788]: <warn> [1461449929.2427] device (wlp3s0): Activation: failed for connection 'FRITZ!Box 7362 SL'
Apr 24 00:18:49 Tesla NetworkManager[788]: <info> [1461449929.2437] device (wlp3s0): state change: failed -> disconnected (reason 'none') [120 30 0]
After connecting, iwconfig
yields:
enp4s0 no wireless extensions.
lo no wireless extensions.
wlp3s0 IEEE 802.11bgn ESSID:"FRITZ!Box 7362 SL"
Mode:Managed Frequency:2.427 GHz Access Point: 34:31:C4:30:7D:13
Bit Rate=72.2 Mb/s Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=66/70 Signal level=-44 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:105 Missed beacon:0
I would be happy for any suggestions.
networking wireless network-manager asus 16.04
add a comment
|
I've performed a fresh installation of Ubuntu 16.04 on my Asus N56VZ. Sadly, i cannot connect to wireless networks using the NetworkManager. I am able to see wireless networks, though.
I tried to connect to my network using the GUI and entered my password. But after that, nothing happens. I see no attempt to connect to this network, and I don't get an error either. I can see that the network manager saved my network, and I double and triple-checked whether the password and all other configurable parameters are correct.
Funny thing is - I am able to connect using nmtui
without any problems.
I have not been able to test whether this is a problem with this specific network or if it is a general problem. I highly suspect the latter though, as I had no problem using said network on Ubuntu 15.04.
Output of some interesting commands:
Before connecting using nmtui
:
iwconfig
enp4s0 no wireless extensions.
lo no wireless extensions.
wlp3s0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
lspci -vvnn | grep Network
03:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01)
Subsystem: AzureWave AR9485 Wireless Network Adapter [1a3b:2c97]
sudo service NetworkManager status
(after I tried and failed to establish a connectiong using the NetworkManager)
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since So 2016-04-24 00:03:32 CEST; 15min ago
Main PID: 788 (NetworkManager)
Tasks: 3 (limit: 512)
CGroup: /system.slice/NetworkManager.service
└─788 /usr/sbin/NetworkManager --no-daemon
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2249] device (wlp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2253] manager: NetworkManager state is now CONNECTING
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2265] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2270] device (wlp3s0): Activation: (wifi) access point 'FRITZ!Box 7362 SL' has security, but secrets are required.
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2277] device (wlp3s0): state change: config -> need-auth (reason 'none') [50 60 0]
Apr 24 00:18:49 Tesla NetworkManager[788]: <warn> [1461449929.2418] device (wlp3s0): No agents were available for this request.
Apr 24 00:18:49 Tesla NetworkManager[788]: <info> [1461449929.2419] device (wlp3s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Apr 24 00:18:49 Tesla NetworkManager[788]: <info> [1461449929.2422] manager: NetworkManager state is now DISCONNECTED
Apr 24 00:18:49 Tesla NetworkManager[788]: <warn> [1461449929.2427] device (wlp3s0): Activation: failed for connection 'FRITZ!Box 7362 SL'
Apr 24 00:18:49 Tesla NetworkManager[788]: <info> [1461449929.2437] device (wlp3s0): state change: failed -> disconnected (reason 'none') [120 30 0]
After connecting, iwconfig
yields:
enp4s0 no wireless extensions.
lo no wireless extensions.
wlp3s0 IEEE 802.11bgn ESSID:"FRITZ!Box 7362 SL"
Mode:Managed Frequency:2.427 GHz Access Point: 34:31:C4:30:7D:13
Bit Rate=72.2 Mb/s Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=66/70 Signal level=-44 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:105 Missed beacon:0
I would be happy for any suggestions.
networking wireless network-manager asus 16.04
Did you get anywhere with this? I'm new to Ubuntu and Linux. Version 14 the wireless worked fine but am seeing these symptoms on a clean install of 16.04
– Po-ta-toe
Apr 26 '16 at 15:11
To be honest, I haven't tried any further yet. After I connected via nmtui, everything worked; and I wasn't able to test it with an other network yet.
– Mesaph
Apr 28 '16 at 17:31
connecting to a wired network, getting the updates and enabling a third party driver fixed it for me
– Po-ta-toe
Apr 28 '16 at 17:41
Could you please try to connect to a wireless access point and then run the network diagnostics? It includes a bunch of other information that may be relevant under the circumstances like a kernel log excerpt (including messages from the wireless network adapter driver).
– David Foerster
May 26 '16 at 13:34
@Mesaph I cannot thank you enough for pointingnmtui
out.
– brisssou
Jun 23 '16 at 8:48
add a comment
|
I've performed a fresh installation of Ubuntu 16.04 on my Asus N56VZ. Sadly, i cannot connect to wireless networks using the NetworkManager. I am able to see wireless networks, though.
I tried to connect to my network using the GUI and entered my password. But after that, nothing happens. I see no attempt to connect to this network, and I don't get an error either. I can see that the network manager saved my network, and I double and triple-checked whether the password and all other configurable parameters are correct.
Funny thing is - I am able to connect using nmtui
without any problems.
I have not been able to test whether this is a problem with this specific network or if it is a general problem. I highly suspect the latter though, as I had no problem using said network on Ubuntu 15.04.
Output of some interesting commands:
Before connecting using nmtui
:
iwconfig
enp4s0 no wireless extensions.
lo no wireless extensions.
wlp3s0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
lspci -vvnn | grep Network
03:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01)
Subsystem: AzureWave AR9485 Wireless Network Adapter [1a3b:2c97]
sudo service NetworkManager status
(after I tried and failed to establish a connectiong using the NetworkManager)
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since So 2016-04-24 00:03:32 CEST; 15min ago
Main PID: 788 (NetworkManager)
Tasks: 3 (limit: 512)
CGroup: /system.slice/NetworkManager.service
└─788 /usr/sbin/NetworkManager --no-daemon
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2249] device (wlp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2253] manager: NetworkManager state is now CONNECTING
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2265] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2270] device (wlp3s0): Activation: (wifi) access point 'FRITZ!Box 7362 SL' has security, but secrets are required.
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2277] device (wlp3s0): state change: config -> need-auth (reason 'none') [50 60 0]
Apr 24 00:18:49 Tesla NetworkManager[788]: <warn> [1461449929.2418] device (wlp3s0): No agents were available for this request.
Apr 24 00:18:49 Tesla NetworkManager[788]: <info> [1461449929.2419] device (wlp3s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Apr 24 00:18:49 Tesla NetworkManager[788]: <info> [1461449929.2422] manager: NetworkManager state is now DISCONNECTED
Apr 24 00:18:49 Tesla NetworkManager[788]: <warn> [1461449929.2427] device (wlp3s0): Activation: failed for connection 'FRITZ!Box 7362 SL'
Apr 24 00:18:49 Tesla NetworkManager[788]: <info> [1461449929.2437] device (wlp3s0): state change: failed -> disconnected (reason 'none') [120 30 0]
After connecting, iwconfig
yields:
enp4s0 no wireless extensions.
lo no wireless extensions.
wlp3s0 IEEE 802.11bgn ESSID:"FRITZ!Box 7362 SL"
Mode:Managed Frequency:2.427 GHz Access Point: 34:31:C4:30:7D:13
Bit Rate=72.2 Mb/s Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=66/70 Signal level=-44 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:105 Missed beacon:0
I would be happy for any suggestions.
networking wireless network-manager asus 16.04
I've performed a fresh installation of Ubuntu 16.04 on my Asus N56VZ. Sadly, i cannot connect to wireless networks using the NetworkManager. I am able to see wireless networks, though.
I tried to connect to my network using the GUI and entered my password. But after that, nothing happens. I see no attempt to connect to this network, and I don't get an error either. I can see that the network manager saved my network, and I double and triple-checked whether the password and all other configurable parameters are correct.
Funny thing is - I am able to connect using nmtui
without any problems.
I have not been able to test whether this is a problem with this specific network or if it is a general problem. I highly suspect the latter though, as I had no problem using said network on Ubuntu 15.04.
Output of some interesting commands:
Before connecting using nmtui
:
iwconfig
enp4s0 no wireless extensions.
lo no wireless extensions.
wlp3s0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
lspci -vvnn | grep Network
03:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01)
Subsystem: AzureWave AR9485 Wireless Network Adapter [1a3b:2c97]
sudo service NetworkManager status
(after I tried and failed to establish a connectiong using the NetworkManager)
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since So 2016-04-24 00:03:32 CEST; 15min ago
Main PID: 788 (NetworkManager)
Tasks: 3 (limit: 512)
CGroup: /system.slice/NetworkManager.service
└─788 /usr/sbin/NetworkManager --no-daemon
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2249] device (wlp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2253] manager: NetworkManager state is now CONNECTING
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2265] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2270] device (wlp3s0): Activation: (wifi) access point 'FRITZ!Box 7362 SL' has security, but secrets are required.
Apr 24 00:18:24 Tesla NetworkManager[788]: <info> [1461449904.2277] device (wlp3s0): state change: config -> need-auth (reason 'none') [50 60 0]
Apr 24 00:18:49 Tesla NetworkManager[788]: <warn> [1461449929.2418] device (wlp3s0): No agents were available for this request.
Apr 24 00:18:49 Tesla NetworkManager[788]: <info> [1461449929.2419] device (wlp3s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Apr 24 00:18:49 Tesla NetworkManager[788]: <info> [1461449929.2422] manager: NetworkManager state is now DISCONNECTED
Apr 24 00:18:49 Tesla NetworkManager[788]: <warn> [1461449929.2427] device (wlp3s0): Activation: failed for connection 'FRITZ!Box 7362 SL'
Apr 24 00:18:49 Tesla NetworkManager[788]: <info> [1461449929.2437] device (wlp3s0): state change: failed -> disconnected (reason 'none') [120 30 0]
After connecting, iwconfig
yields:
enp4s0 no wireless extensions.
lo no wireless extensions.
wlp3s0 IEEE 802.11bgn ESSID:"FRITZ!Box 7362 SL"
Mode:Managed Frequency:2.427 GHz Access Point: 34:31:C4:30:7D:13
Bit Rate=72.2 Mb/s Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=66/70 Signal level=-44 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:105 Missed beacon:0
I would be happy for any suggestions.
networking wireless network-manager asus 16.04
networking wireless network-manager asus 16.04
edited Sep 14 at 18:46
Pablo A
4,5653 gold badges23 silver badges49 bronze badges
4,5653 gold badges23 silver badges49 bronze badges
asked Apr 23 '16 at 22:47
MesaphMesaph
1511 gold badge2 silver badges5 bronze badges
1511 gold badge2 silver badges5 bronze badges
Did you get anywhere with this? I'm new to Ubuntu and Linux. Version 14 the wireless worked fine but am seeing these symptoms on a clean install of 16.04
– Po-ta-toe
Apr 26 '16 at 15:11
To be honest, I haven't tried any further yet. After I connected via nmtui, everything worked; and I wasn't able to test it with an other network yet.
– Mesaph
Apr 28 '16 at 17:31
connecting to a wired network, getting the updates and enabling a third party driver fixed it for me
– Po-ta-toe
Apr 28 '16 at 17:41
Could you please try to connect to a wireless access point and then run the network diagnostics? It includes a bunch of other information that may be relevant under the circumstances like a kernel log excerpt (including messages from the wireless network adapter driver).
– David Foerster
May 26 '16 at 13:34
@Mesaph I cannot thank you enough for pointingnmtui
out.
– brisssou
Jun 23 '16 at 8:48
add a comment
|
Did you get anywhere with this? I'm new to Ubuntu and Linux. Version 14 the wireless worked fine but am seeing these symptoms on a clean install of 16.04
– Po-ta-toe
Apr 26 '16 at 15:11
To be honest, I haven't tried any further yet. After I connected via nmtui, everything worked; and I wasn't able to test it with an other network yet.
– Mesaph
Apr 28 '16 at 17:31
connecting to a wired network, getting the updates and enabling a third party driver fixed it for me
– Po-ta-toe
Apr 28 '16 at 17:41
Could you please try to connect to a wireless access point and then run the network diagnostics? It includes a bunch of other information that may be relevant under the circumstances like a kernel log excerpt (including messages from the wireless network adapter driver).
– David Foerster
May 26 '16 at 13:34
@Mesaph I cannot thank you enough for pointingnmtui
out.
– brisssou
Jun 23 '16 at 8:48
Did you get anywhere with this? I'm new to Ubuntu and Linux. Version 14 the wireless worked fine but am seeing these symptoms on a clean install of 16.04
– Po-ta-toe
Apr 26 '16 at 15:11
Did you get anywhere with this? I'm new to Ubuntu and Linux. Version 14 the wireless worked fine but am seeing these symptoms on a clean install of 16.04
– Po-ta-toe
Apr 26 '16 at 15:11
To be honest, I haven't tried any further yet. After I connected via nmtui, everything worked; and I wasn't able to test it with an other network yet.
– Mesaph
Apr 28 '16 at 17:31
To be honest, I haven't tried any further yet. After I connected via nmtui, everything worked; and I wasn't able to test it with an other network yet.
– Mesaph
Apr 28 '16 at 17:31
connecting to a wired network, getting the updates and enabling a third party driver fixed it for me
– Po-ta-toe
Apr 28 '16 at 17:41
connecting to a wired network, getting the updates and enabling a third party driver fixed it for me
– Po-ta-toe
Apr 28 '16 at 17:41
Could you please try to connect to a wireless access point and then run the network diagnostics? It includes a bunch of other information that may be relevant under the circumstances like a kernel log excerpt (including messages from the wireless network adapter driver).
– David Foerster
May 26 '16 at 13:34
Could you please try to connect to a wireless access point and then run the network diagnostics? It includes a bunch of other information that may be relevant under the circumstances like a kernel log excerpt (including messages from the wireless network adapter driver).
– David Foerster
May 26 '16 at 13:34
@Mesaph I cannot thank you enough for pointing
nmtui
out.– brisssou
Jun 23 '16 at 8:48
@Mesaph I cannot thank you enough for pointing
nmtui
out.– brisssou
Jun 23 '16 at 8:48
add a comment
|
3 Answers
3
active
oldest
votes
I have been having the same issue, While not a fix, I found that restarting the network manager works. I have included the instructions to do this below.
From the command line
Stopping Network Manager
sudo /etc/init.d/network-manager stop
Starting Network Manager
sudo /etc/init.d/network-manager start
This worked for me. Funny that it worked fine during the install as root, but not once my user was created. Is this due to the new user not being added to some kind of networking config?
– Todd
May 18 '16 at 12:43
add a comment
|
I solved the problem by typing my password into a document, and then copying and pasting it into the password field.
For some reason the connection was timing out before I could type my (long) password in but not giving me any messages about it.
1
-1 Your case seems a bit different: you probably had a bogus non-printable character (e. g. a new-line character) in the wireless password when you pasted it from the clipboard. In OP's case the network manager complains that there was no secret supplied at all which is quite different from the wrong secret.
– David Foerster
May 26 '16 at 13:37
1
No, I have same fix. If you insert password fast - it works =)
– demon101
Aug 22 '16 at 19:25
2
Typing it into gedit and pasting it worked for me as well. How bizarre
– Matt Setter
Sep 4 '16 at 10:28
@demon101: The question isn't about your or Anna's issue but about OP's. How do you know it was the “same fix” for them? They didn't accept an answer or comment positively on one.
– David Foerster
Nov 6 '16 at 4:24
1
@DavidFoerster your -1 is not justified. It exactly helped me to solve the same issue had. So I'll add +1.
– Semo
Jan 29 '17 at 15:08
|
show 2 more comments
ubuntu 16.04 doesn't have properly configured wireless driver.. I installed Ubuntu 16.04 in 3 machines and no one came with working wireless. Straight forward solution could be, user Ethernet cable to use Internet, then
sudo apt-get update
- now goto > system setting > software updates > additional driver
- now if it shows wireless driver, install it and you are done.
If it doesn't solves your problem you probably need to use logging tools like dmesg, syslog, journalctl, lshw.. know your wireless hardware and google the respective driver.
@DavidFoerster Your comment was so strong I believe it SHOULD have been an answer instead. Anyway, this comment-like answer saved my day ;)
– mizurnix
Nov 5 '16 at 22:51
add a comment
|
protected by Community♦ Jun 3 '16 at 17:37
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have been having the same issue, While not a fix, I found that restarting the network manager works. I have included the instructions to do this below.
From the command line
Stopping Network Manager
sudo /etc/init.d/network-manager stop
Starting Network Manager
sudo /etc/init.d/network-manager start
This worked for me. Funny that it worked fine during the install as root, but not once my user was created. Is this due to the new user not being added to some kind of networking config?
– Todd
May 18 '16 at 12:43
add a comment
|
I have been having the same issue, While not a fix, I found that restarting the network manager works. I have included the instructions to do this below.
From the command line
Stopping Network Manager
sudo /etc/init.d/network-manager stop
Starting Network Manager
sudo /etc/init.d/network-manager start
This worked for me. Funny that it worked fine during the install as root, but not once my user was created. Is this due to the new user not being added to some kind of networking config?
– Todd
May 18 '16 at 12:43
add a comment
|
I have been having the same issue, While not a fix, I found that restarting the network manager works. I have included the instructions to do this below.
From the command line
Stopping Network Manager
sudo /etc/init.d/network-manager stop
Starting Network Manager
sudo /etc/init.d/network-manager start
I have been having the same issue, While not a fix, I found that restarting the network manager works. I have included the instructions to do this below.
From the command line
Stopping Network Manager
sudo /etc/init.d/network-manager stop
Starting Network Manager
sudo /etc/init.d/network-manager start
edited May 17 '16 at 9:25
dedunumax
5,7183 gold badges17 silver badges27 bronze badges
5,7183 gold badges17 silver badges27 bronze badges
answered May 17 '16 at 3:09
KamillionKamillion
511 bronze badge
511 bronze badge
This worked for me. Funny that it worked fine during the install as root, but not once my user was created. Is this due to the new user not being added to some kind of networking config?
– Todd
May 18 '16 at 12:43
add a comment
|
This worked for me. Funny that it worked fine during the install as root, but not once my user was created. Is this due to the new user not being added to some kind of networking config?
– Todd
May 18 '16 at 12:43
This worked for me. Funny that it worked fine during the install as root, but not once my user was created. Is this due to the new user not being added to some kind of networking config?
– Todd
May 18 '16 at 12:43
This worked for me. Funny that it worked fine during the install as root, but not once my user was created. Is this due to the new user not being added to some kind of networking config?
– Todd
May 18 '16 at 12:43
add a comment
|
I solved the problem by typing my password into a document, and then copying and pasting it into the password field.
For some reason the connection was timing out before I could type my (long) password in but not giving me any messages about it.
1
-1 Your case seems a bit different: you probably had a bogus non-printable character (e. g. a new-line character) in the wireless password when you pasted it from the clipboard. In OP's case the network manager complains that there was no secret supplied at all which is quite different from the wrong secret.
– David Foerster
May 26 '16 at 13:37
1
No, I have same fix. If you insert password fast - it works =)
– demon101
Aug 22 '16 at 19:25
2
Typing it into gedit and pasting it worked for me as well. How bizarre
– Matt Setter
Sep 4 '16 at 10:28
@demon101: The question isn't about your or Anna's issue but about OP's. How do you know it was the “same fix” for them? They didn't accept an answer or comment positively on one.
– David Foerster
Nov 6 '16 at 4:24
1
@DavidFoerster your -1 is not justified. It exactly helped me to solve the same issue had. So I'll add +1.
– Semo
Jan 29 '17 at 15:08
|
show 2 more comments
I solved the problem by typing my password into a document, and then copying and pasting it into the password field.
For some reason the connection was timing out before I could type my (long) password in but not giving me any messages about it.
1
-1 Your case seems a bit different: you probably had a bogus non-printable character (e. g. a new-line character) in the wireless password when you pasted it from the clipboard. In OP's case the network manager complains that there was no secret supplied at all which is quite different from the wrong secret.
– David Foerster
May 26 '16 at 13:37
1
No, I have same fix. If you insert password fast - it works =)
– demon101
Aug 22 '16 at 19:25
2
Typing it into gedit and pasting it worked for me as well. How bizarre
– Matt Setter
Sep 4 '16 at 10:28
@demon101: The question isn't about your or Anna's issue but about OP's. How do you know it was the “same fix” for them? They didn't accept an answer or comment positively on one.
– David Foerster
Nov 6 '16 at 4:24
1
@DavidFoerster your -1 is not justified. It exactly helped me to solve the same issue had. So I'll add +1.
– Semo
Jan 29 '17 at 15:08
|
show 2 more comments
I solved the problem by typing my password into a document, and then copying and pasting it into the password field.
For some reason the connection was timing out before I could type my (long) password in but not giving me any messages about it.
I solved the problem by typing my password into a document, and then copying and pasting it into the password field.
For some reason the connection was timing out before I could type my (long) password in but not giving me any messages about it.
edited May 26 '16 at 13:58
Android Dev
12.6k7 gold badges35 silver badges67 bronze badges
12.6k7 gold badges35 silver badges67 bronze badges
answered May 26 '16 at 12:06
AnnaAnna
411 bronze badge
411 bronze badge
1
-1 Your case seems a bit different: you probably had a bogus non-printable character (e. g. a new-line character) in the wireless password when you pasted it from the clipboard. In OP's case the network manager complains that there was no secret supplied at all which is quite different from the wrong secret.
– David Foerster
May 26 '16 at 13:37
1
No, I have same fix. If you insert password fast - it works =)
– demon101
Aug 22 '16 at 19:25
2
Typing it into gedit and pasting it worked for me as well. How bizarre
– Matt Setter
Sep 4 '16 at 10:28
@demon101: The question isn't about your or Anna's issue but about OP's. How do you know it was the “same fix” for them? They didn't accept an answer or comment positively on one.
– David Foerster
Nov 6 '16 at 4:24
1
@DavidFoerster your -1 is not justified. It exactly helped me to solve the same issue had. So I'll add +1.
– Semo
Jan 29 '17 at 15:08
|
show 2 more comments
1
-1 Your case seems a bit different: you probably had a bogus non-printable character (e. g. a new-line character) in the wireless password when you pasted it from the clipboard. In OP's case the network manager complains that there was no secret supplied at all which is quite different from the wrong secret.
– David Foerster
May 26 '16 at 13:37
1
No, I have same fix. If you insert password fast - it works =)
– demon101
Aug 22 '16 at 19:25
2
Typing it into gedit and pasting it worked for me as well. How bizarre
– Matt Setter
Sep 4 '16 at 10:28
@demon101: The question isn't about your or Anna's issue but about OP's. How do you know it was the “same fix” for them? They didn't accept an answer or comment positively on one.
– David Foerster
Nov 6 '16 at 4:24
1
@DavidFoerster your -1 is not justified. It exactly helped me to solve the same issue had. So I'll add +1.
– Semo
Jan 29 '17 at 15:08
1
1
-1 Your case seems a bit different: you probably had a bogus non-printable character (e. g. a new-line character) in the wireless password when you pasted it from the clipboard. In OP's case the network manager complains that there was no secret supplied at all which is quite different from the wrong secret.
– David Foerster
May 26 '16 at 13:37
-1 Your case seems a bit different: you probably had a bogus non-printable character (e. g. a new-line character) in the wireless password when you pasted it from the clipboard. In OP's case the network manager complains that there was no secret supplied at all which is quite different from the wrong secret.
– David Foerster
May 26 '16 at 13:37
1
1
No, I have same fix. If you insert password fast - it works =)
– demon101
Aug 22 '16 at 19:25
No, I have same fix. If you insert password fast - it works =)
– demon101
Aug 22 '16 at 19:25
2
2
Typing it into gedit and pasting it worked for me as well. How bizarre
– Matt Setter
Sep 4 '16 at 10:28
Typing it into gedit and pasting it worked for me as well. How bizarre
– Matt Setter
Sep 4 '16 at 10:28
@demon101: The question isn't about your or Anna's issue but about OP's. How do you know it was the “same fix” for them? They didn't accept an answer or comment positively on one.
– David Foerster
Nov 6 '16 at 4:24
@demon101: The question isn't about your or Anna's issue but about OP's. How do you know it was the “same fix” for them? They didn't accept an answer or comment positively on one.
– David Foerster
Nov 6 '16 at 4:24
1
1
@DavidFoerster your -1 is not justified. It exactly helped me to solve the same issue had. So I'll add +1.
– Semo
Jan 29 '17 at 15:08
@DavidFoerster your -1 is not justified. It exactly helped me to solve the same issue had. So I'll add +1.
– Semo
Jan 29 '17 at 15:08
|
show 2 more comments
ubuntu 16.04 doesn't have properly configured wireless driver.. I installed Ubuntu 16.04 in 3 machines and no one came with working wireless. Straight forward solution could be, user Ethernet cable to use Internet, then
sudo apt-get update
- now goto > system setting > software updates > additional driver
- now if it shows wireless driver, install it and you are done.
If it doesn't solves your problem you probably need to use logging tools like dmesg, syslog, journalctl, lshw.. know your wireless hardware and google the respective driver.
@DavidFoerster Your comment was so strong I believe it SHOULD have been an answer instead. Anyway, this comment-like answer saved my day ;)
– mizurnix
Nov 5 '16 at 22:51
add a comment
|
ubuntu 16.04 doesn't have properly configured wireless driver.. I installed Ubuntu 16.04 in 3 machines and no one came with working wireless. Straight forward solution could be, user Ethernet cable to use Internet, then
sudo apt-get update
- now goto > system setting > software updates > additional driver
- now if it shows wireless driver, install it and you are done.
If it doesn't solves your problem you probably need to use logging tools like dmesg, syslog, journalctl, lshw.. know your wireless hardware and google the respective driver.
@DavidFoerster Your comment was so strong I believe it SHOULD have been an answer instead. Anyway, this comment-like answer saved my day ;)
– mizurnix
Nov 5 '16 at 22:51
add a comment
|
ubuntu 16.04 doesn't have properly configured wireless driver.. I installed Ubuntu 16.04 in 3 machines and no one came with working wireless. Straight forward solution could be, user Ethernet cable to use Internet, then
sudo apt-get update
- now goto > system setting > software updates > additional driver
- now if it shows wireless driver, install it and you are done.
If it doesn't solves your problem you probably need to use logging tools like dmesg, syslog, journalctl, lshw.. know your wireless hardware and google the respective driver.
ubuntu 16.04 doesn't have properly configured wireless driver.. I installed Ubuntu 16.04 in 3 machines and no one came with working wireless. Straight forward solution could be, user Ethernet cable to use Internet, then
sudo apt-get update
- now goto > system setting > software updates > additional driver
- now if it shows wireless driver, install it and you are done.
If it doesn't solves your problem you probably need to use logging tools like dmesg, syslog, journalctl, lshw.. know your wireless hardware and google the respective driver.
edited May 27 '16 at 1:20
Videonauth
27.6k12 gold badges83 silver badges109 bronze badges
27.6k12 gold badges83 silver badges109 bronze badges
answered May 17 '16 at 8:47
user545033user545033
311 bronze badge
311 bronze badge
@DavidFoerster Your comment was so strong I believe it SHOULD have been an answer instead. Anyway, this comment-like answer saved my day ;)
– mizurnix
Nov 5 '16 at 22:51
add a comment
|
@DavidFoerster Your comment was so strong I believe it SHOULD have been an answer instead. Anyway, this comment-like answer saved my day ;)
– mizurnix
Nov 5 '16 at 22:51
@DavidFoerster Your comment was so strong I believe it SHOULD have been an answer instead. Anyway, this comment-like answer saved my day ;)
– mizurnix
Nov 5 '16 at 22:51
@DavidFoerster Your comment was so strong I believe it SHOULD have been an answer instead. Anyway, this comment-like answer saved my day ;)
– mizurnix
Nov 5 '16 at 22:51
add a comment
|
protected by Community♦ Jun 3 '16 at 17:37
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
Did you get anywhere with this? I'm new to Ubuntu and Linux. Version 14 the wireless worked fine but am seeing these symptoms on a clean install of 16.04
– Po-ta-toe
Apr 26 '16 at 15:11
To be honest, I haven't tried any further yet. After I connected via nmtui, everything worked; and I wasn't able to test it with an other network yet.
– Mesaph
Apr 28 '16 at 17:31
connecting to a wired network, getting the updates and enabling a third party driver fixed it for me
– Po-ta-toe
Apr 28 '16 at 17:41
Could you please try to connect to a wireless access point and then run the network diagnostics? It includes a bunch of other information that may be relevant under the circumstances like a kernel log excerpt (including messages from the wireless network adapter driver).
– David Foerster
May 26 '16 at 13:34
@Mesaph I cannot thank you enough for pointing
nmtui
out.– brisssou
Jun 23 '16 at 8:48