Wifi-menu -o: CONNECTING FAILED

EDIT: It seems my problem is just this: I installed netctl and I have started it using systemd. When I write sudo wifi-menu -o, and try to connect to my wireless network using the correct password (I've tried many times), it just instantly tells me "CONNECTING FAILED" - without any apparent waiting for the router to respond, although I don't know.
Edit: I tried NetworkManager as well, and connecting via nmtui, it says "Could not activate connection: Activation failed"... Help.
(old)
I was using connman on my desktop until a recent system upgrade where it only said "Input/output error" when I tried to connect to wireless networks. I installed the packages netctl, ifplugd and wpa_actiond and read a bit about netctl on arch wiki. With `wifi-menu -o` I generated a profile in /etc/netctl for my wireless network. I called the profile "31". I have enabled and started netctl using systemctl. I also wrote `sudo netctl enable 31`. Now, when I write `sudo netctl start 31`, I get this error:
$ sudo netctl start 31
Job for [email protected] failed. See 'systemctl status [email protected]' and 'journalctl -xn' for details.
$ systemctl status netctl@31
● [email protected] - Automatically generated profile by wifi-menu
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: failed (Result: exit-code) since on. 2014-08-20 14:04:10 CEST; 55s ago
Docs: man:netctl.profile(5)
Process: 5669 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
Main PID: 5669 (code=exited, status=1/FAILURE)
Here is the profile:
$ sudo cat /etc/netctl/31
Description='Automatically generated profile by wifi-menu'
Interface=wlp3s0
Connection=wireless
Security=wpa
ESSID=31.
IP=dhcp
Key=\"<a lot of characters that are irrelevant>
If you need more information, please tell. Thanks!
Edit: Shamefully.. I was a bit too fast to post. I read this just when I posted and it worked!
Edit 2: Rebooted and still the same problem. journalctl -xn says nothing about network errors.
Edit 3: Rebooted, and ran journalctl -xn as super user. It now gave relevant information:
# journalctl -xn
-- Logs begin at sø. 2014-05-25 20:44:50 CEST, end at on. 2014-08-20 19:11:08 CEST. --
aug. 20 19:10:57 3rlend network[27525]: Failed to bring the network up for profile '31'
aug. 20 19:10:57 3rlend systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
aug. 20 19:10:57 3rlend systemd[1]: Failed to start Automatically generated profile by wifi-menu.
-- Subject: Unit [email protected] has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit [email protected] has failed.
-- The result is failed.
aug. 20 19:10:57 3rlend systemd[1]: Unit [email protected] entered failed state.
aug. 20 19:10:59 3rlend ntpd[1253]: bind(23) AF_INET6 fe80::720:3f17:85cc:2894%2%2#123 flags 0x11 failed: Cannot assign requested address
aug. 20 19:10:59 3rlend ntpd[1253]: unable to create socket on enp4s0 (21) for fe80::720:3f17:85cc:2894%2#123
aug. 20 19:10:59 3rlend ntpd[1253]: failed to init interface for address fe80::720:3f17:85cc:2894%2
aug. 20 19:11:08 3rlend pacserve[29800]: [Errno 19] No such device
aug. 20 19:11:08 3rlend systemd[1]: pacserve.service: main process exited, code=exited, status=71/n/a
aug. 20 19:11:08 3rlend systemd[1]: Unit pacserve.service entered failed state.
Edit 4: Tried to set up the profile again using wifi-menu; seems I have overlooked an important detail: wifi-menu tells me "CONNECTING FAILED" even though I'm sure I wrote the right password (several times). The router uses wpa2.
Last edited by Ploppz (2014-08-21 19:12:43)

Same problem here. Seriously, the team's arch have to see what the hell is wrong with the packages that are responsible for the wireless system.

Similar Messages

Asha 302 wifi problem - "WLAN connection failed"

I have nokia asha 302 two days. I have problem with wifi connection. I see "my wifi" in wifi list, but when I click connect, I get message "WLAN connection failed". Version of mobile Asha is 14.78.
I have router Ovislink WN-200R. My wifi setinngs is in attachment (set 1).
I tried to change password, change security system, set to without security system, ... - without changing. At last I found bug and one solution. When I set wifi, how is in attachment (set 2), is to possible to connect with Asha 302.
But in my house I use PC with wifi N for speed. Do you know any other solution?
PS. I use Nokia 5530, Iphone 4GS, HTC desire S too. And I don`t have this problem.
Thanks a lot
Attachments:
Asha_302_wifi_problem.png ‏98 KB

DennIz wrote:
"Wrong Password"
There are several reasons why that could happen. One reason: Your network changed from WPA2-PSK back to WPA1-PSK. Some Wi-Fi access-points have silly mixed-mode settings. If your network is in mixed mode, first try the old version: WPA-only (WPA-PSK). Because some very old Wi-Fi access-points do not support WPA2 correctly even for multicast, as next step try the more secure version 2: WPA2-PSK. If that does not work:
Do you have a Mac OS X computer around?
If yes, please, go to Applications » Utilities » Terminal and enter
/System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport -I -s
The last part (Security) should be ‘WPA2(PSK/AES/AES)’ and nothing else.
Do you have a Windows Vista, Windows 7, or Windows 8 computer around?
If yes, please, open a command prompt (as Administrator, keys: Windows-R), and enter
netsh wlan show networks mode=bssid
The network type has to be not Ad-hoc but Infrastructure.
The basic rates should be ‘1 2 5.5 6 11 12 24’ (IEEE 802.11g/n) and nothing else.
Do you have a Android device around?
If yes, install the free Wifi Analyzer. Within that tool, please, tap the wrench icon (Settings) » Show full securities. Then go back and have a look at your Wi-Fi.
It must be [WPA2-PSK-CCMP][ESS] and nothing else.
If the connection still fails, please go to the configuration interface of your Wi-Fi access point and change your access-point back to the old WPA-PSK (TKIP-only) and 802.11g (only). If not available, avoid 802.11n and go for 802.11b/g. Does it work now?
If it still does not work, change your settings back to WPA2-PSK (AES-CCMP) only and 802.11g/n. Then, post the results of the above tools. If you do not like to post them into the public, you can send me a private message. But those information are public to your neighbours anyway.

WIFI - mail - history connect Fail

Touchpad won't recognize wifi or show my mail history unless I reboot it, then I can connect & it shows all my mail history. What is wrong & the solutiion?

Sorry about that.
A "sticky" post is a special post that answers a lot of commonly asked questions. We mark it to "stick" to the top of the message listing where it can be easily seen by users looking for answers. They have orange sides on them.
Here's a direct link to the thread at the top of this section:
http://h30434.www3.hp.com/t5/webOS-Hardware-and-Software/How-to-use-the-webOS-Doctor-on-the-TouchPad...
WyreNut
I am a Volunteer here, not employed by HP.
You too can become an HP Expert! Details HERE!
If my post has helped you, click the Kudos Thumbs up!
If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

OS X 10.8.4 wifi says "connection failed", but connects anyway; cannot save password

I am using OS X 10.8.4 that came with my MBP. When I connect to my home wifi that requires a WPA 2 password, it says "Connection Failed", but anyway connects to the internet. Also, my password is not being saved, and I need to enter it everytime.
After reading several forums, I have already tried the following:
1. removing airport preference list from Library/Preferences/SystemConfiguration
2. Removing network password from the keychain
3. Using Keychain first aid
4. Using disk utility and doing repair disk.
5. Doing DHCP release in Network Preferences.
6. Removing my network from the preferred network list and connecting again.
I am using a D-link modem. It should not be a problem, because the same MBP could remember the password before. The problem happened when I tried to fix my wifi because it would take long to connect after waking from sleep, when I deleted the airport preferences list, and removed the keyring.

Back up all data. Don't continue unless you're sure you can restore from a backup, even if you're unable to log in.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Enter the following command in the Terminal window in the same way as before (triple-click, copy, and paste):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
This time you'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
Take this step only if you have trouble with Step 1 or if it doesn't solve the problem.
Boot into Recovery. When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
res
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

Wifi setup: wifi-menu fails but wpa_supplicant works

Guys,
I've installed archlinux for the first time, and I'm mighty pleased. I've been following the installation guides, and have run into a slightly annoying issue.
When I try to setup my wifi(WPA) with "wifi-menu", I end up with "CONNECTION FAILED" error message. The steps I'm following are.
# wifi-menu
In ncurses
1. choose the SSID
2. Enter the password
Result - CONNECTION FAILED
However, running wpa_supplicant command from commandline works well.
# wpa_supplicant -B -i wlp3s0 -c <(wpa_passphrase "ssid" "password")
.. works!
So, wifi drivers are properly loaded for sure. I believe that wifi-menu internally uses wpa_supplicant. Why would "wifi-menu" command fail? Ultimately I want to use netctl profiles to automatically enable the wifi rather than manually enabling wi-fi every time. Any ideas?

@luisgmarine, I have tried it with and without the single quotes -- no difference. Thanks for the idea though.
@progandy, Interesting. I'm not sure how to figure out if it's an issue with the router communication or not, though.
Anyway, thanks for the ideas and thoughts. I'll mark this as solved, because it is working; I was just curious to see if there was an apparent explanation.

[Solved] Cannot connect with wifi-menu after login

I can't connect to the internet after I login. When I try to connect, it says:
Job for netctl@my\x2dnetwork.service failed. See "systemctl status 'netctl@my\x2dnetwork.service'" and "journalctl -xe" for details.
#systemctl status 'netctl@my\x2dnetwork.service'
● netctl@my\x2dnetwork.service - A simple WPA encrypted wireless connection
Loaded: loaded (/etc/systemd/system/netctl@my\x2dnetwork.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2015-02-06 16:37:35 CST; 1min 23s ago
Docs: man:netctl.profile(5)
Process: 574 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
Main PID: 574 (code=exited, status=1/FAILURE)
Feb 06 16:37:35 mac network[574]: Starting network profile 'my-network'...
Feb 06 16:37:35 mac network[574]: The interface of network profile 'my-network' is already up
Feb 06 16:37:35 mac systemd[1]: netctl@my\x2dnetwork.service: main process exited, code=exited, status=1/FAILURE
Feb 06 16:37:35 mac systemd[1]: Failed to start A simple WPA encrypted wireless connection.
Feb 06 16:37:35 mac systemd[1]: Unit netctl@my\x2dnetwork.service entered failed state.
Feb 06 16:37:35 mac systemd[1]: netctl@my\x2dnetwork.service failed.
#journalctl -xe
Feb 06 16:37:17 mac dbus[217]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 06 16:37:17 mac udisksd[436]: udisks daemon version 2.1.3 starting
Feb 06 16:37:17 mac dbus[217]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 06 16:37:17 mac udisksd[436]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 06 16:37:18 mac polkitd[271]: Registered Authentication Agent for unix-session:c2 (system bus name :1.29 [/usr/lib/polkit-gnome/polkit-gnome-authen
Feb 06 16:37:18 mac dbus[217]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 06 16:37:18 mac avahi-daemon[481]: Found user 'avahi' (UID 84) and group 'avahi' (GID 84).
Feb 06 16:37:18 mac avahi-daemon[481]: Successfully dropped root privileges.
Feb 06 16:37:18 mac avahi-daemon[481]: avahi-daemon 0.6.31 starting up.
Feb 06 16:37:18 mac avahi-daemon[481]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Feb 06 16:37:18 mac dbus[217]: [system] Successfully activated service 'org.freedesktop.Avahi'
Feb 06 16:37:18 mac avahi-daemon[481]: Successfully called chroot().
Feb 06 16:37:18 mac avahi-daemon[481]: Successfully dropped remaining capabilities.
Feb 06 16:37:18 mac avahi-daemon[481]: Loading service file /services/sftp-ssh.service.
Feb 06 16:37:18 mac avahi-daemon[481]: Loading service file /services/ssh.service.
Feb 06 16:37:18 mac avahi-daemon[481]: Network interface enumeration completed.
Feb 06 16:37:18 mac avahi-daemon[481]: Registering HINFO record with values 'X86_64'/'LINUX'.
Feb 06 16:37:18 mac avahi-daemon[481]: Server startup complete. Host name is mac.local. Local service cookie is 1997621208.
Feb 06 16:37:18 mac avahi-daemon[481]: Service "mac" (/services/ssh.service) successfully established.
Feb 06 16:37:18 mac avahi-daemon[481]: Service "mac" (/services/sftp-ssh.service) successfully established.
Feb 06 16:37:30 mac sudo[510]: mac : TTY=pts/0 ; PWD=/home/mac ; USER=root ; COMMAND=/usr/bin/wifi-menu
Feb 06 16:37:30 mac sudo[510]: pam_unix(sudo:session): session opened for user root by mac(uid=0)
Feb 06 16:37:35 mac network[574]: Starting network profile 'my-network'...
Feb 06 16:37:35 mac network[574]: The interface of network profile 'my-network' is already up
Feb 06 16:37:35 mac systemd[1]: netctl@my\x2dnetwork.service: main process exited, code=exited, status=1/FAILURE
Feb 06 16:37:35 mac systemd[1]: Failed to start A simple WPA encrypted wireless connection.
-- Subject: Unit netctl@my\x2dnetwork.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit netctl@my\x2dnetwork.service has failed.
-- The result is failed.
Feb 06 16:37:35 mac systemd[1]: Unit netctl@my\x2dnetwork.service entered failed state.
Feb 06 16:37:35 mac systemd[1]: netctl@my\x2dnetwork.service failed.
Feb 06 16:37:35 mac sudo[510]: pam_unix(sudo:session): session closed for user root
Feb 06 16:37:48 mac dbus[217]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager
Feb 06 16:37:48 mac dbus[217]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop
Feb 06 16:37:50 mac logger[626]: ACPI action undefined: PNP0C0A:00
Feb 06 16:38:31 mac logger[653]: ACPI action undefined: PNP0C0A:00
Feb 06 16:39:13 mac logger[657]: ACPI action undefined: PNP0C0A:00
When I ip link set ... down, I wifi-menu and it connects. No need to ip link set ... up.
Here's my /etc/systemd/system/netctl\@my\\x2dnetwork.service as mentioned above.
.include /usr/lib/systemd/system/[email protected]
[Unit]
Description=A simple WPA encrypted wireless connection
BindsTo=sys-subsystem-net-devices-wlp4s0.device
After=sys-subsystem-net-devices-wlp4s0.device
Not sure if this is relevant. Also mentioned above. This is /usr/lib/network/network.
#! /bin/bash
. /usr/lib/network/globals
## Check if a string represents a network interface
# $1: potential interface name
is_interface() {
# Strip any old school alias specifier
[[ -d "/sys/class/net/${1%%:?*}" ]]
## Add an interface
# $1: interface type
# $2: interface name
# $3: interface link (optional)
# $4...: additional arguments
interface_add() {
local type="$1" name="$2" link="$3"
do_debug ip link add ${link:+link "$link"} name "$name" type "$type" "${@:4}" || return
if [[ -x "$PROFILE_DIR/interfaces/$name" ]]; then
source "$PROFILE_DIR/interfaces/$name"
fi
## Delete an interface
# $1: interface name
interface_delete() {
bring_interface_down "$1"
ip link delete "$1"
## Check if an interface is up
# $1: interface name
interface_is_up() {
local flags
read flags < "/sys/class/net/${1%%:?*}/flags"
# IFF_UP is defined as 0x1 in linux/if.h
(( flags & 0x1 ))
## Activate an interface
# $1: interface name
bring_interface_up() {
local interface=$1
ip link set dev "$interface" up &>/dev/null
timeout_wait "${TimeoutUp:-5}" 'interface_is_up "$interface"'
## Deactivate an interface
# $1: interface name
bring_interface_down() {
local interface=$1
ip link set dev "$interface" down &>/dev/null
# We reuse the up timeout (down normally is faster)
timeout_wait "${TimeoutUp:-5}" '! interface_is_up "$interface"'
if [[ $# -ne 2 || $1 != @(start|stop) ]]; then
exit_error "Usage: $0 {start|stop} <profile>"
fi
ensure_root netctl
# Ensure we are not in a transient directory
cd /
# Expose the profile name
Profile=$2
load_profile "$Profile"
case $1 in
start)
report_notice "Starting network profile '$Profile'..."
if is_interface "$Interface" && interface_is_up "$Interface" && \
! is_yes "${ForceConnect:-no}"; then
report_error "The interface of network profile '$Profile' is already up"
exit 1
fi
if ! "${Connection}_up"; then
report_error "Failed to bring the network up for profile '$Profile'"
exit 1
fi
# JP: sandbox the eval
if ! ( eval $ExecUpPost ); then
report_error "ExecUpPost failed for network profile '$Profile'"
# Failing ExecUpPost will take the connection down
"${Connection}_down"
exit 1
fi
report_notice "Started network profile '$Profile'"
stop)
report_notice "Stopping network profile '$Profile'..."
# JP: sandbox the eval
if ! ( eval $ExecDownPre ); then
report_error "ExecDownPre failed for network profile '$Profile'"
# Failing ExecDownPre will leave the profile active
exit 1
fi
if ! "${Connection}_down"; then
report_error "Failed to bring the network down for profile '$Profile'"
exit 1
fi
if is_interface "$Interface" && interface_is_up "$Interface" && \
! is_yes "${ForceConnect:-no}"; then
report_error "The interface of network profile '$Profile' did not go down"
exit 1
fi
report_notice "Stopped network profile '$Profile'"
esac
Last edited by rollypolio (2015-02-07 16:37:01)

I honestly don't remember. I believe I was trying to set up i3status dhcp at the time. Could have been the DHCP configuration file I created at /etc/systemd/network that broke my netctl configuration. I should have mentioned that first. I broke the internet and walked away two days ago and it's slowly coming back to me. I don't follow the relation between systemd, netctl, and dhcp configuration so I'm sorry if I'm not picking up on solutions provided in your links.
I commented the file out right after I started receiving those errors.
$cat /etc/systemd/network/MyDhcp.network
#[Match]
#Name=wlp4s0
#[Network]
#DHCP=v4
$ls -la /etc/systemd/network/MyDhcp.network
drwxr-xr-x 2 root root 4096 Feb 6 09:29 .
drwxr-xr-x 5 root root 4096 Feb 5 20:15 ..
-rw-r--r-- 1 root root 43 Feb 6 09:29 MyDhcp.network
$cat /etc/netctl/my-network
Description='A simple WPA encrypted wireless connection'
Interface=wlp4s0
Connection=wireless
Security=wpa
IP=dhcp
ESSID='ap_becca'
# Prepend hexadecimal keys with \"
# If your key starts with ", write it as '""<key>"'
# See also: the section on special quoting rules in netctl.profile(5)
Key='*********'
# Uncomment this if your ssid is hidden
#Hidden=yes
# Set a priority for automatic profile selection
#Priority=10
#cat /etc/netctl/wlp4s0-Nexxt_5F6CB8
Description='Automatically generated profile by wifi-menu'
Interface=wlp4s0
Connection=wireless
Security=none
ESSID=Nexxt_5F6CB8
IP=dhcp
#cat /etc/netctl/wlp4s0-SJBS
Description='Automatically generated profile by wifi-menu'
Interface=wlp4s0
Connection=wireless
Security=wpa
ESSID=SJBS
IP=dhcp
Key=********
I noticed the first profile does not require sudo.
$ ls -la
total 32
drwxr-xr-x 5 root root 4096 Feb 2 09:32 .
drwxr-xr-x 81 root root 4096 Feb 7 09:42 ..
drwxr-xr-x 2 root root 4096 Jan 31 22:50 examples
drwxr-xr-x 2 root root 4096 Jan 13 07:23 hooks
drwxr-xr-x 2 root root 4096 Jan 13 07:23 interfaces
-rw-r--r-- 1 root root 422 Jan 31 22:52 my-network
-rw------- 1 root root 138 Feb 2 09:32 wlp4s0-Nexxt_5F6CB8
-rw------- 1 root root 145 Feb 2 06:36 wlp4s0-SJBS
I hope this helps.
Which one should I be looking at?:
$ls /usr/lib/systemd/system/ | grep netctl
[email protected]
[email protected]
netctl.service
[email protected]
netctl-sleep.service
To repeat myself, I can connect using wifi-menu after I ip link set wlp4s0 down. I'm just looking for a fix so I can set up automatic connections.
EDIT: I deleted /etc/systemd/network/MyDhcp.network and now it works at startup. Any idea why a commented out file would be having an adverse effect like this?
Last edited by rollypolio (2015-02-07 16:41:41)

'Connection Failed' msg when trying to connect my TX to wifi

I have a Palm TX that I bought used. The seller said it was in good order (she bought an iPhone), everything else works on it, my router is a Linksys and is working properly for the laptop. I have been on the phone and live chat with Palm support (they say they can't help). I have read the major posts about common problems (by Wyrenut, I think and on brighthand). I have done a soft reset and a hard reset with no change.
HELP! The TX picks up the signal and shows our SSID. We use WPA-PSK and I've entered the key code several times and I'm sure it's correct. The TX also will pick up signals elsewhere, such as hotels and restaurants, but still says 'connection failed'.
Is there a way to tell if it is a hardware problem? If maybe I got a lemon? (I hope not) All else works properly. I can sync, etc.
Can anyone help? If it helps, I was told it is 2 yrs old. Also, I've emailed the seller and asked if the wifi connection was working when she last used it, but nothing yet.
Post relates to: Palm TX
This question was solved.
View Solution.

MAC filtering is turned off by default in just about every router. If you haven't turned it on, then it shouldn't be in effect. I don't own a Linksys, but MAC filtering should be in the Wireless settings somewhere.
When you did the resets, did you test the TX immediately without a Hotsync? If not, it may be software-related.
Are you sure the router is set to broadcast in /b mode, or "Mixed /b and /g"? If set to "/b,/g, and /n" try backing off to just b and g, no /n.
WyreNut
I am a Volunteer here, not employed by HP.
You too can become an HP Expert! Details HERE!
If my post has helped you, click the Kudos Thumbs up!
If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

Network manager in xfce doesn't connect but wifi-menu does?

I may be misunderstanding how to use this since I've never done wireless from the command line before, but here is my situation:
I just installed arch on my Acer Aspire One and used both the wired and wireless from the command line. I had never done wireless from the command line before and just followed the Beginners Guide and used wifi-menu to select the network to connect to. It was very very smooth and connected me in seconds. After installing xfce I decided I wanted a tray icon for selecting wireless stuff and so I installed networkmanager and network-manager-applet. After starting nm-applet it reported my wireless as disconnected (even though it was connected) and when I asked it to connect to my network it was unable to connect. I restarted the computer and still no success. While I can get by with wifi-menu, it would be awfully nice if I could get network manager to work with xfce. Does anyone have any thoughts on this?
Thanks in advance.

I switched to using wicd and after a little while of using it it seems to work pretty well. It works significantly better than NetworkManager and doesn't drop connections very often so long as the signal is good.
My one complaint is that every so often a process called wicd-monitor likes to start using 100% cpu on one of my cores. Since this is a netbook and power is critical, I usually end up killing the process or restarting wicd so that it stops draining my battery.

Wifi menu kills bluetooth connection

This is very weird behaviour. I have a Kaiser Baas bluetooth keyboard with integrated trackpad. I also use wifi to connect to the internet via my modem-router.
Since installing Yosemite, the keyboard looses its connection to my Mac Mini if I move the mouse pointer and hover over the Wifi menu. However, that is only if the Mac Mini was not able to make a wifi connection.
For some reason, my Mac Mini doesn't always see my router's broadcast ssid. When that happens, the wifi menu looks like a giant version of what it looks when connected. I turn wifi off and on and still it can't see my router. Strange because it can see three other wifi spots in my suburb. Then, if I put the Mac Mini to sleep and wake it again, yes, it can see the ssid and connects automatically.
Then, the problem with my bluetooth keyboard is solved too.
Just what is going on with wifi and bluetooth in Yosemite. OS X networking has always been fragile, flaky and temperamental but this is getting especially obtuse.
Has anyone seen this behaviour ?
Garry

Thanks. I'll try a different keyboard-trackpad-mouse and look for more reports on wifi problems. I've not yet found any on theses discussions boards which involve both bluetooth and wifi but, as 10.10 is still young it might be developing.
The Kaiser Baas is not very suited to OS X although they say it is compatible. It works but, the Trackpad prefs pane doesn't recognise it and the mouse pane options don't work very well with it either. So, it could be related to the problem. Still, I don't understand why it should lose the bluetooth connection just because I've accessed the wifi menu.
Cheers.
Garry

Hp Ink Advantage 4515 WIFI connection failed

Connection fails with blue screen and error code: B8154250. It asks printer restart but doesn't solve the issue. Power source plug out and plug in tried. Set factory settings also not satisfactory. How should I reset the printer or upload new firmware. If WIFI switched off there's no error message. Printer is 2 month old. Please help. I give the last chance before bring it to the service.

I have just purchased HP4507 all in one printer and wanted to take advantage of the instantink
offer with the enrolement card I got with the printer. However, when I try to enrol it tells me that
my enrolement key number is for the UK only and not valid.
??????? anyone able to tell me how I enrol for the instantink.

Want stream Netflix to blueray via Airport Express wifi. The blueray finds my wifi but the wireless connection failed - said, Ensure DHCP server is enabled on router and restart router. Don't think I have DHCP server. Suggestions anyone?

Want to stream Netflix to blueray player via my existing Airport Express wifi. The player finds my wifi but the wireless connection fails - says, " Ensure DHCP server is enabled on router and restart router." I don't think I have a DHCP server. Suggestions anyone?

I can't speak specifically regarding LG, but the Whole Home feature on Direct TV (record a movie on one DVR and watch it on another TV in another location) just won't work with wireless, and I have a strong fast connection at 300 Mbps. Ethernet works perfectly.
Few audio/video products will accept "n" wireless at 5 GHz. I suspect that your LG accepts a 2.4 GHz signal, which would top out at 130 Mpbs.
If you are trying to stream High Definition video, especially at 1080P, my opinion would be that it is unlikely that you will be able to do so reliably using wireless.
Perhaps another user who has figured out how to do this will post with some input.

Wifi connection failed

Hi,
When I try to connect to the internet using my iMac, I get the error 'connection failed' and i cant connect to the internet. All the other computers and devices connect to the wifi just fine so i know it is a problem with the mac and nothing else. What is causing this error and how do i fix the problem?
I had this same problem about a month ago, so I completely cleaned and re-installed the operating system and updated to Yosemite. This fixed the problem until now.
Thanks

Can you connect to the internet using ethernet?

No connection with server, connection failed, asks wifi password

our i-pas has always worked great, suddenly we couldn't use internet anymore. Connection failed and ask wifi password.
I installed the new version of i-tune and re-installed our i-pad. Still no connection. What to do?

Hi,
Please make sure,
1. Correct user ID and password entered
2. There is no firewall/ antivirus turned on
Thanks & Regards,
Nagarajan

Bad news for "connection failed, wlan / wifi not f...

Sometime ago I wrote this in my blog: Conn. failed Wlan not found
And, like most of you who are now reading this post, I've spent hours trying to google a solution, totally without success. But at least, after so much reading and learning, I've come to a definite (and very teaching) conclusion: this issue is due to nothing less but a shameful bug in Symbian^3's DHCP client. There's no blaming the router's settings or characteristics, because with exactly the same routers and settings, most other phones can connect.
However, I always hoped that the Nokia crew were taking note of this bug and working on it, and I've spent months waiting for a fix in some of the firmware updates. I've done two updates since I got the phone (mine is a C7, but I believe it's a Symbian^3 "feature"), to no avail: disheartedly, both times I've seen that the bug remained there.
"Maybe in Symbian Belle?" I said to myself. "Of course. They can't be that blunt! The've got to fix it in Belle." So, yesterday I updated my C7 with the "leaked" Belle firmware and, you know what? Yes! They've been certainly working on the bug! This way:
So far, when trying to connect to some wireless routers we got the error message: "Conn. failed. Wlan not found". Now, after making us wait so much for Belle (and not yet officially released), there's no such message any more!
Oh, well, certainly we still can't connect to the router, but now the message reads: "Connection failed. Wi-fi netw. not found".
Nokia, this is un-be-lie-va-ble. I know you're reading this. Will you ever fix the mentioned problem in Symbian? It's no small bug, folks.

Hi Torben
Thank you for contacting Nokia Care customer support.
Since we wrote last I have got a lot more experience with the Belles situation in this area.
Recently suspicion fell on a bug in old saved data from the "Anna" that causes general network error.
To solve it, there must be a backup - but NOT the programs / settings, since they bear the error.
Subsequently, disconnect the phone from, select the Offline profile (Press and hold the cards on the off button and choose the one on this list)
"Ring" now * # 7370 # accept and enter the security code is 12345, if it asks for it.
Your security code if you have change it.
Set Time & Date and reviewing start-up menus.
Get immediately sent to the settings for data and multimedia.
Restart your phone and try now about the Internet is working properly.
Do they do it; you can safely restore contacts and whatever else you have in your backup.
I would personally appreciate it if you want to participate in a brief survey that will be about my response to you. Customer survey will receive a separate e-mail.
If there is anything I can do for you, then you're obviously more than welcome to contact me again.
Sincerely
Jannik Petersen
Nokia Care

Wifi-menu not working.

Everytime I try and connect to wifi, but i used the arch iso just to see if i can get wifi-menu working and it worked. Soo idk...
$sudo wifi-menu
Scanning for networks.... failed
No networks found
http://i.imgur.com/uLbKd9b.png

ip link set up wlp1s0 up
RTNETLINK answers: Operation not possible due to RF-kill
lspci -k
01:00 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter
Subsystem: Lenovo device b736
Kernel driver in use : rt18723be
Kernel modules: rtl18723be
02:00.0 Ethernet controller Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Ethernet Controller (rev 10)
Subsystem: Lenovo Device 3812
Kernel drive in use r8169
Kernel modules: r8169
Sorry if i didn't do something correctly. I just went off google searches.

Wifi-menu -o: CONNECTING FAILED

Similar Messages

Maybe you are looking for