[SOLVED]netctl not connected

wireless-wpa profil file;
Description='A simple WPA encrypted wireless connection'
Interface=wlp20s0
Connection=wireless
Security=wpa
IP=dhcp
ESSID='TD-W8101G_1'
# 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='key'
# Uncomment this if your ssid is hidden
#Hidden=yes
# netctl start wireless-wpa
Job for netctl@wireless\x2dwpa.service failed. See 'systemctl status netctl@wireless\x2dwpa.service' and 'journalctl -xn' for details.
# journalctl -xn
-- Logs begin at Prş 2013-04-11 03:43:28 UTC, end at Paz 2013-04-14 23:32:29 UTC. --
Nis 14 23:20:28 arch systemd[1]: Unit netctl@wireless\x2dwpa.service entered failed state
Nis 14 23:22:35 arch systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: Unit systemd-tmpfiles-clean.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-tmpfiles-clean.service has begun starting up.
Nis 14 23:22:35 arch systemd-tmpfiles[2111]: stat(/run/user/1000/gvfs) failed: Permission denied
Nis 14 23:22:35 arch systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-tmpfiles-clean.service has finished starting up.
-- The start-up result is done.
Nis 14 23:22:44 arch slim[1415]: opera: Activated running instance
Nis 14 23:24:25 arch slim[1415]: Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.con
Nis 14 23:32:22 arch su[1675]: pam_unix(su:session): session closed for user root
Nis 14 23:32:25 arch slim[1415]: Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.con
Nis 14 23:32:29 arch su[2163]: (to root) sleepforlife on /dev/pts/0
Nis 14 23:32:29 arch su[2163]: pam_unix(su:session): session opened for user root by sleepforlife(uid=1000)
# systemctl status netctl@wireless\x2dwpa.service
[email protected] - Networking for netctl profile wirelessx2dwpa
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
Active: inactive (dead)
Docs: man:netctl.profile(5)
Last edited by sleepforlife (2013-04-15 07:20:39)

journalctl -xn
-- Logs begin at Prş 2013-04-11 03:43:28 UTC, end at Pzt 2013-04-15 09:24:51 UTC
Nis 15 09:24:42 arch slim[1415]: Fontconfig warning: "/etc/fonts/conf.d/50-user.
Nis 15 09:24:47 arch su[2996]: (to root) sleepforlife on /dev/pts/0
Nis 15 09:24:47 arch su[2996]: pam_unix(su:session): session opened for user roo
Nis 15 09:24:51 arch systemd[1]: Starting Networking for netctl profile wireless
-- Subject: Unit netctl@wireless\x2dwpa.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit netctl@wireless\x2dwpa.service has begun starting up.
Nis 15 09:24:51 arch network[3004]: Starting network profile 'wireless-wpa'...
Nis 15 09:24:51 arch network[3004]: Interface 'wlan0' does not exist
Nis 15 09:24:51 arch network[3004]: Failed to bring the network up for profile '
Nis 15 09:24:51 arch systemd[1]: netctl@wireless\x2dwpa.service: main process ex
Nis 15 09:24:51 arch systemd[1]: Failed to start Networking for netctl profile w
-- Subject: Unit netctl@wireless\x2dwpa.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02c
-- Unit netctl@wireless\x2dwpa.service has failed.
-- The result is failed.
lines 1-23
-- Logs begin at Prş 2013-04-11 03:43:28 UTC, end at Pzt 2013-04-15 09:24:51 UTC
Nis 15 09:24:42 arch slim[1415]: Fontconfig warning: "/etc/fonts/conf.d/50-user.
Nis 15 09:24:47 arch su[2996]: (to root) sleepforlife on /dev/pts/0
Nis 15 09:24:47 arch su[2996]: pam_unix(su:session): session opened for user roo
Nis 15 09:24:51 arch systemd[1]: Starting Networking for netctl profile wireless
-- Subject: Unit netctl@wireless\x2dwpa.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit netctl@wireless\x2dwpa.service has begun starting up.
Nis 15 09:24:51 arch network[3004]: Starting network profile 'wireless-wpa'...
Nis 15 09:24:51 arch network[3004]: Interface 'wlan0' does not exist
Nis 15 09:24:51 arch network[3004]: Failed to bring the network up for profile '
Nis 15 09:24:51 arch systemd[1]: netctl@wireless\x2dwpa.service: main process ex
Nis 15 09:24:51 arch systemd[1]: Failed to start Networking for netctl profile w
-- Subject: Unit netctl@wireless\x2dwpa.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02c
-- Unit netctl@wireless\x2dwpa.service has failed.
-- The result is failed.
Nis 15 09:24:51 arch systemd[1]: Unit netctl@wireless\x2dwpa.service entered fai
lines 1-24/24 (END)

Similar Messages

How to solve launch_msg not connected

my powerbook g4 wont boot ;error launch_msg not connected how to solve this issue

There may be a way to start in single-user mode, enter the correct command
and then restart from there into the normal GUI. However the info in your post
suggests two different products, as PowerBookG4 cannot run Mt Lion 10.8.5...
If your computer is a MacBook, running a more recent OS X than a PPC G4
can, then your topic could be moved by a Host into the correct ASC area.
•Start up in Single-User or Verbose Mode:
Mac OS X: How to start up in single-user or verbose mode - Apple Support
•7 Mac Startup Options Every OS X User Should Know:
http://www.tekrevue.com/tip/mac-startup-options/
Depending on how you arrived at the message, the path should be clear.
If you have a complete or duplicate backup of your computer content, a
different path could be taken to attempt to erase & install a new OS X.
More information may be needed; esp. if host should relocate your post.
Good luck & happy computing!

[SOLVED] netctl not bringing up my network at boot

I recently converted from netcfg to netctl and but my network is not coming up ever at boot time. Once the machine is booted I can bring it up manually using
netcfg start ethernet-static
It is obviously an static IP address and I copied the netctl sample script and then modified it. Here is my ethernet-static profile.
Description='A basic static ethernet connection'
Interface=enp2s0
Connection=ethernet
IP=static
Address=('192.168.0.5/24')
#Routes=('192.168.0.0/24 via 192.168.1.2')
Gateway='192.168.0.1'
DNS=('192.168.0.1')
## For IPv6 autoconfiguration
#IP6=stateless
## For IPv6 static address configuration
#IP6=static
#Address6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
#Routes6=('abcd::1234')
#Gateway6='1234:0:123::abcd'
The output of journalctl -d | grep net is the following
un 14 08:40:03 kfrance-home kernel: Initializing cgroup subsys net_cls
Jun 14 08:40:03 kfrance-home kernel: audit: initializing netlink socket (disabled)
Jun 14 08:40:03 kfrance-home kernel: drop_monitor: Initializing network drop monitor service
Jun 14 08:40:03 kfrance-home systemd[1]: Expecting device sys-subsystem-net-devices-enp2s0.device...
Jun 14 08:40:03 kfrance-home kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Jun 14 08:40:03 kfrance-home kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
Jun 14 08:40:03 kfrance-home systemd-udevd[171]: renamed network interface eth0 to enp3s0
Jun 14 08:40:03 kfrance-home systemd-udevd[168]: renamed network interface eth0 to enp2s0
Jun 14 08:40:07 kfrance-home network[253]: Starting network profile 'ethernet-static'...
Jun 14 08:40:12 kfrance-home network[253]: No connection on interface 'enp2s0'
Jun 14 08:40:12 kfrance-home network[253]: Failed to bring the network up for profile 'ethernet-static'
Jun 14 08:40:12 kfrance-home systemd[1]: netctl@ethernet\x2dstatic.service: main process exited, code=exited, status=1/FAILURE
Jun 14 08:40:12 kfrance-home systemd[1]: Failed to start A basic static ethernet connection.
Jun 14 08:40:12 kfrance-home systemd[1]: Unit netctl@ethernet\x2dstatic.service entered failed state.
Jun 14 08:47:53 kfrance-home sudo[1300]: kfrance : TTY=pts/1 ; PWD=/home/emily ; USER=root ; COMMAND=/usr/bin/netctl start ethernet-static
Jun 14 08:47:53 kfrance-home systemd[1]: Starting A basic static ethernet connection...
Jun 14 08:47:53 kfrance-home network[1307]: Starting network profile 'ethernet-static'...
Jun 14 08:47:57 kfrance-home network[1307]: Started network profile 'ethernet-static'
Jun 14 08:47:57 kfrance-home systemd[1]: Started A basic static ethernet connection.
Nothing from netcfg, or any other network service, is leading to a conflict for configuring the network.
systemctl list-units | grep net
[email protected] loaded active exited A basic static ethernet connection
network.target loaded active active Network
I do have two ethernet ports but from what I can tell the naming of the two ports is consistent.
netctl status shows that my ethernet-static profile is the only profile and is active.
I know I could connect without using netctl but want to get this working. Any ideas?
Last edited by kfrance (2013-06-15 04:12:06)

I fixed the problem. I changed the device name of the ethernet device I wanted to use using an udev-rule, according to the notes on the Network Configuration wiki page, to make sure that it wasn't a naming conflict and that solved it.

[SOLVED] Remmina not connecting

Hello all,
I installed Remmina and freerdp following the wiki, and I have two Windows Server 2008 R2 installs with the remote desktop option "Only allow with Network Authentication" selected in Windows. When connecting the first time I could connect to both servers, but that only lasted one time. Now I can only connect to one of the servers, and the only thing that changed was I went home for the night, and came in the next morning.
When trying to connect to the one of the servers I get an error message "Unable to connect to RDP server <server name>".
I verified all the settings with the server that worked, and they are configured the same way. I also verified the settings on the server, no go.
I'm not sure what to look at to see what could be wrong.
any ideas?
--nixIT
EDIT... Solved thread, just deleted the ~/.freerdp/known_hosts file
Last edited by nixIT (2014-03-18 14:49:09)

Thank you alot I must have read the wiki wrong or somthing cause I thought I need to but those ! in from of all network operations. Well I removed them and places wicd in the deamon and reboot and everything is up and running....:D

[Solved] Netctl - Cannot connect to wireless network

Hi,
since I replaced netcfg with netctl a week ago, it worked just fine. Today, however, i wanted to connect to a different wireless network and i couldn't make it work.
Here's some information about how i connected to my home network (which worked fine):
I changed the netcfg config files to match netctl syntax (as described in the wiki)
I activated netctl-auto@wlan0
The connection to the network was established almost immediately after (re)boot or resume after suspend
First off: I double-checked the config file for the second network. Both syntax and SSID/passphrase are correct. Also, I don't have special characters in my network/profile names, the names in brackets are placeholders.
Here's what happens after a fresh reboot (only the second network is in range of my pc, so it doesn't connect to my first - working - network):
Netctl-auto is active and running, but seems to repeatedly lose connection to the second network:
# systemctl status netctl-auto@wlan0
[email protected] - Automatic wireless network connection using netctl profiles
Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled)
Active: active (running) since Fri 2013-05-17 00:28:03 CEST; 13min ago
Docs: man:netctl.special(7)
Process: 453 ExecStart=/usr/bin/netctl-auto start %I (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/[email protected]/[email protected]
├─480 wpa_supplicant -B -P /run/wpa_supplicant_wlan0.pid -i wlan0 -D nl80211,wext -c/run/network/wpa_supplicant_wlan0.conf -W
└─483 wpa_actiond -p /run/wpa_supplicant -i wlan0 -P /run/network/wpa_actiond_wlan0.pid -a /usr/lib/network/auto.action
May 17 00:41:40 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
May 17 00:41:41 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'
May 17 00:41:48 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
May 17 00:41:48 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'
May 17 00:41:51 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
May 17 00:41:51 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'
May 17 00:41:54 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
May 17 00:41:54 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'
May 17 00:41:58 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
May 17 00:41:58 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'
# journalctl -xn
-- Logs begin at Sat 2012-12-08 23:44:06 CET, end at Fri 2013-05-17 00:47:43 CEST. --
May 17 00:47:33 <hostname> kernel: cfg80211: Calling CRDA to update world regulatory domain
May 17 00:47:36 <hostname> kernel: wlan0: authenticate with <network_2 mac address>
May 17 00:47:36 <hostname> kernel: wlan0: send auth to <network_2 mac address> (try 1/3)
May 17 00:47:36 <hostname> kernel: wlan0: authenticated
May 17 00:47:36 <hostname> kernel: wlan0: associate with <network_2 mac address> (try 1/3)
May 17 00:47:36 <hostname> kernel: wlan0: RX AssocResp from <network_2 mac address> (capab=0x431 status=0 aid=3)
May 17 00:47:36 <hostname> kernel: wlan0: associated
May 17 00:47:36 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
More interestingly, dmesg seems to provide a reason for this behaviour:
# dmesg
[ 1438.732242] wlan0: authenticate with <network_2 mac address>
[ 1438.737594] wlan0: send auth to <network_2 mac address> (try 1/3)
[ 1438.740384] wlan0: authenticated
[ 1438.743113] wlan0: associate with <network_2 mac address> (try 1/3)
[ 1438.747226] wlan0: RX AssocResp from <network_2 mac address> (capab=0x431 status=0 aid=3)
[ 1438.767629] wlan0: associated
[ 1438.837011] wlan0: AP <network_2 mac address> changed bandwidth, new config is 2412 MHz, width 1 (2412/0 MHz)
[ 1438.837024] wlan0: AP <network_2 mac address> changed bandwidth in a way we can't support - disconnect
[ 1438.896427] cfg80211: Calling CRDA to update world regulatory domain
[ 1442.140427] wlan0: authenticate with <network_2 mac address>
[ 1442.145282] wlan0: send auth to <network_2 mac address> (try 1/3)
[ 1442.148090] wlan0: authenticated
[ 1442.151674] wlan0: associate with <network_2 mac address> (try 1/3)
[ 1442.155712] wlan0: RX AssocResp from <network_2 mac address> (capab=0x431 status=0 aid=3)
[ 1442.175911] wlan0: associated
[ 1442.214954] wlan0: AP <network_2 mac address> changed bandwidth, new config is 2412 MHz, width 1 (2412/0 MHz)
[ 1442.214967] wlan0: AP <network_2 mac address> changed bandwidth in a way we can't support - disconnect
[ 1442.258359] cfg80211: Calling CRDA to update world regulatory domain
I'm pretty sure everything should theoretically work fine, because it worked before the netctl update. I was even connected to this network today until i had to reboot!
Now here's what happens if I try to connect manually:
# netctl start <network_2>
Job for netctl@<network_2>.service failed. See 'systemctl status netctl@<network_2>.service' and 'journalctl -xn' for details.
# systemctl status netctl@<network_2>.service
netctl@<network_2>.service - Networking for netctl profile <network_2>
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
Active: failed (Result: exit-code) since Fri 2013-05-17 00:58:40 CEST; 2min 36s ago
Docs: man:netctl.profile(5)
Process: 7368 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
May 17 00:58:40 <hostname> network[7368]: Starting network profile '<network_2>'...
May 17 00:58:40 <hostname> network[7368]: The interface of network profile '<network_2>' is already up
May 17 00:58:40 <hostname> systemd[1]: netctl@<network_2>.service: main process exited, code=exited, status=1/FAILURE
May 17 00:58:40 <hostname> systemd[1]: Failed to start Networking for netctl profile <network_2>.
May 17 00:58:40 <hostname> systemd[1]: Unit netctl@<network_2>.service entered failed state.
After an # ip link set wlan0 down netctl still claims that its job failed:
# netctl start <network_2>
Job for netctl@<network_2>.service failed. See 'systemctl status netctl@<network_2>.service' and 'journalctl -xn' for details.
This time, the DHCP lease attempt seems to be failing:
# systemctl status netctl@<network_2>.service
netctl@<network_2>.service - Networking for netctl profile <network_2>
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
Active: failed (Result: exit-code) since Fri 2013-05-17 01:04:42 CEST; 1min 33s ago
Docs: man:netctl.profile(5)
Process: 8423 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
May 17 01:04:23 <hostname> systemd[1]: Starting Networking for netctl profile <network_2>...
May 17 01:04:23 <hostname> network[8423]: Starting network profile '<network_2>'...
May 17 01:04:31 <hostname> dhcpcd[8656]: version 5.6.8 starting
May 17 01:04:31 <hostname> dhcpcd[8656]: wlan0: carrier lost
May 17 01:04:31 <hostname> dhcpcd[8656]: wlan0: waiting for carrier
May 17 01:04:41 <hostname> dhcpcd[8656]: timed out
May 17 01:04:41 <hostname> network[8423]: DHCP IP lease attempt failed on interface 'wlan0'
May 17 01:04:42 <hostname> systemd[1]: netctl@<network_2>.service: main process exited, code=exited, status=1/FAILURE
May 17 01:04:42 <hostname> systemd[1]: Failed to start Networking for netctl profile <network_2>.
May 17 01:04:42 <hostname> systemd[1]: Unit netctl@<network_2>.service entered failed state.
I wasn't able to find out whether netctl needs a running dhcpcd or not, but after running a systemctl start dhcpcd.service, dmesg seems to give a little more information:
# dmesg
[ 2500.090650] wlan0: authenticate with <network_2 mac address>
[ 2500.109377] wlan0: send auth to <network_2 mac address> (try 1/3)
[ 2500.114053] wlan0: authenticated
[ 2500.115817] wlan0: associate with <network_2 mac address> (try 1/3)
[ 2500.121336] wlan0: RX AssocResp from <network_2 mac address> (capab=0x431 status=0 aid=3)
[ 2500.147262] wlan0: associated
[ 2500.303529] wlan0: AP <network_2 mac address> changed bandwidth, new config is 2412 MHz, width 1 (2412/0 MHz)
[ 2500.303542] wlan0: AP <network_2 mac address> changed bandwidth in a way we can't support - disconnect
[ 2500.327471] cfg80211: Calling CRDA to update world regulatory domain
[ 2769.285673] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 2769.285908] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[ 2769.488380] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Any pointers and solutions are greatly appreciated.
Thanks,
diiis
Last edited by diiis (2013-05-23 16:45:47)

@silverzhao I use a manual dhcpcd/wpa_supplicant way of setting up my wlan0 using http://git.r-36.net/conn and I have the same problem.
I have to kill my wireless and restart after seeing a message like:
May 20 10:12:33 x220 kernel: wlan0: AP a4:b1:e9:55:25:2f changed bandwidth, new config is 2462 MHz, width 2 (2452/0 MHz)

[SOLVED] AssaultCube not connecting to server

I guess the title says it all . I think there might be a update soon , according to this ..... http://forum.cubers.net/thread-1181.html Please let me know if you have the same problem , Thanks
Last edited by sliposk (2010-10-15 14:45:46)

It might be caused by an old version 1.1.0.1 of the game which is in Arch repositories and upstream version is 1.1.0.3. To solve it use ABS and bump pkgver or wait until it's updated in Arch Linux.
Last edited by Dogmeat (2010-10-14 16:38:38)

Playbook Magellan Compass - how to solve GPS not connecting to app

Hi
I had problems with Magellan Compass after not using it for a long time (it worked great when i first got my Playbook) and this is the advice I received from O2 Interactive (the developers)
"The GPS Sensor on the PlayBook will lose its association with the nearby satellites from inactive use. Restart the device outside, under a clear sky and wait about 5-10 minutes."
I tried this and it works a treat. By the way I did a full restart ie close down first just to be sure
So one of my favourite apps is now up and running again... I am very pleased !
Thanks O2 !

rossjackson01 wrote:
I have never been able to get Magellan to run whilst travelling. I start and then lose map location.
What level do you need to have for a map to work? Do I need to go to 'Corner'? My problem is that I wish to travel 6 months travelling Europe and and may well be going to 14 countries. I like the size of the Playbook. Using wifi out of my origianl country is inordfiantley expensive, So I would like to get it set before I go. UK, France, Belgium, Netherlands, Germany, Switzerland, Lichenstein, Luxemburg, Spain, Portugal, Austria and Italy. 'Corner' for all?
The user manual is particularly poor.
Help and information please.
Regards
Ross
Try OSMAND. It is free! The user interface is quite easy to get used to. Few words of caution;
- It is not as detailed as some other map apps, but it works. I use it in Canada; US. Used it successfully in Northern Ireland and the Irish Republic.
- The algorithms used to calculate the routes couid use some refining. It is a bit slow to realize that you want to deviate 'from the plan' and lazy to recalculate.
The program will get you there but not always the way you think is best. As usual, it is always handy to keep a good map around.

I have apple iPhone 4S upgraded to iOS 6.0.1 and everything was working fine suddenly my Wifi was not connecting and found the wifi on/off button is greyed out and to enable it I tried all resets but still my problem have not solved, still wifi is off

I have apple iPhone 4S upgraded to iOS 6.0.1 and everything was working fine suddenly my Wifi was not connecting and found the wifi on/off button is greyed out and to enable it I tried all resets but still my problem have not solved, still wifi is off

Same here.... No fix. Replacing is the option apparently and if you're out of warranty, you're SOL. That was as per the "Genius" at Apple.

SOLVED! HP Officejet 6500A E710 will not stay connected to the network. scanner not connected

After 5 hours of live remote HP tech support, and 10 more hours of web searching, I am happy to say I have solved the wireless network connection issue with scanning and printing using the HP Officejet 6500A E710n-z. I notice that there are a lot of people with similar issues with no common, successful fix. Here is what worked for me.
Background Info:
Upgraded internet service from 9Mbps to 27Mbps...Provider brought out new Arris DG860 modem/router. Configured network and connected all clients (smart phones, PCs, Tablets, etc) successfully accept the printer. With this new router/modem the printer/scanner/fax would not connect to my PC at all (Windows 7 64-bit). The Officejet was always connected to the network, however, anytime I tried to print I would get an error "Unable to connect to the printer...", and when I made an attempt to scan.."Scanner not connected, make sure it is connected to the network..." blah blah blah.
Process:
After searching the web for solutions with no success, I finally made my first call to HP tech support. Tech tried numerous fixes: many network changes (channel, static IP, etc.), made changes to Windows system settings and registry, installed new software and drivers, ran the scan doctor, partial, semi, and full reset on the printer. He changed my wifi channel to 6 (or 11) from AUTO and whola. That seemed to fix the problem. After hanging up the phone 10 minutes later "No connection" errors again. Made a second call to HP Tech Support, and this new tech basically tried all the same fixes as the first tech. Worked again for 10-15 minutes then disconnected. Made third call to tech and this individual tried the same fixes as the previous two, but to no avail. He said he would have to direct me to a more Advanced Technician and would call back tomorrow. They called back the next day, and this new tech fixed the issue within 20 minutes.
Problem/Solution:
The fourth "more advanced" tech made one change in my network configuration settings. He changed my network mode from B/G/N to B/G and now the printer/scanner/fax stays connected and works like brand new. The only problem is that all my devices (including the Officejet) are 802.11N capable. Setting my network to the old B/G mixed mode slows my speed down just a bit. Using B/G/N mode or N, my download speed is 27 Mbps. On B/G mixed my speed is 25Mbps. Not too big of a deal, though. All the HP Support Techs were very nice and helpfull. They refunded my $25 Tech fee [fee charged when product is out of warranty] because the problem is not "technically" solved, even though it does work. Conclusio: This seems to be an issue with my the modem/router provided by my ISP. Could also be that it is an older Officejet and need to upgrade. To Fix Follow the Steps Below:
Step 1: Find your default gateway IP...usuall 192.168.0.1 or 192.168.1.1 or similar. Type this IP into your web address bar and hit enter.
Step 2: Enter the username and password. This is normally set at factory default --> username: admin ....passowrd: password .... or .... admin
Step 3: Go to the "Wireless Setup" tab and under the "Advanced Options" and "Wireless Network Settings" change the "Wireless Mode" to "B/G mixed".
Step 4: Click "Apply" then close the browser.
You may, or may not, lose your wifi connection for a short period while the new settings are applied and you may, or may not, have to power cycle your modem/router. That's it. Worked for me and I hope it works for you too. If you have any questions or comments please feel free to post.

OK, that all sounds right. Here are a few more router config ideas:
1. Make sure that 802.11g mode is available, along with others is OK, but 'g' must be present.
2. Change the channel to 11.
3. Use WPA or WPA/WPA2 encryption, not WPA2 only.
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

I upgraded to Maverick and now Time Machine will not connect to the external hard drive to back up files. The external hard drive is a Western Digital "My Book Live" 2 TB. How do I solve problem?

I upgraded to Maverick and now Time Machine will not connect to the external hard drive to back up files. The external hard drive is a Western Digital "My Book Live" 2 TB. How do I solve problem?

I also had problem accessing my WD MyBookLive after upgrading to Maverick.
To resolve the problem, I used Connect To Server (Cmd K) to specify the IP address.
Then I enter a user id and password I created in the MyBookLive.
You can also verify that you have admin access to the MyBookLive using Safari or Chrome.
Just enter the MyBookLive IP address as the URL.

HT4199 my iphone 4s. Wi-Fi not connected. Choose A network ... this prob solve ?

My iPhone 4s
Question: Wi-Fi not connected. Choose A network ...
                This prob solve ?
phone configuration:
capacity: 27.3 GB
version: 8.0.2(12A405)
Model: MD241LL/A
Serial Number: C2*******TD6
Wi-Fi Address: A8:FA:D8:2E:5E:50
IMEI: *****
ICCID: *****
Modem Firmware: 5.4.00
<Edited By Host>

Does the iOS device connect to other networks? If yes that tends to indicate a problem with your network.
Does the iOS device see the network?
Any error messages?
Do other devices now connect?
Did the iOS device connect before?
Try the following to rule out a software problem:
- Reset the iOS device. Nothing will be lost
Reset iOS device: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- Power off and then back on your router
.- Reset network settings: Settings>General>Reset>Reset Network Settings
- iOS: Troubleshooting Wi-Fi networks and connections
- Wi-Fi: Unable to connect to an 802.11n Wi-Fi network
- iOS: Recommended settings for Wi-Fi routers and access points
- Restore from backup. See:
iOS: How to back up
- Restore to factory settings/new iOS device.
If still problem and it does not connect to any networks make an appointment at the Genius Bar of an Apple store since it appears you have a hardware problem.
Apple Retail Store - Genius Bar
Also, I requested that your post be moved to the iPhone form. This is the iPod touch forum?

Iphone 6 automatically turn on even not connect to charger, why would this happen and how to solve it?

iphone 6 automatically turn on even not connect to charger, why would this happen and how to solve it?

I'm not an apple expert or anything, but after hearing this from a coworker (and doing a quick google search) many of the generic chargers do not work in the 5s (especially after the most recent update.) I'm thinking this may be the problem in your case...the charger is not working so the phone just needs a good charge from either an apple certified charger or a generic that will actually work with the phone. I've read some people are able to pull the cable out, turn it around and then plug it back in facing the opposite direction to get it to work. Many have reported, however, that even when this remedies the cable issue, its still won't charge the phone while it is completely dead (which is likely the case since it won't power on at all.) So if you haven't fixed your problem by now, go buy a new charger and see what happens. You might be able to go into and apple store and borrow a charger there for a few minutes to see if this actually IS the problem. That way you don't waste your money before buying.

After update to be iOS 6.0.1, Wi-Fi is not connected automatically. I have to reconnect or join my known network manually all the time. How can I solve this problem? It is so tedious.

After update to be iOS 6.0.1, Wi-Fi is not connected automatically. I have to reconnect or join my known network manually all the time. How can I solve this problem? It is so tedious.

Same here... on my girlfriend's iPod touch (4th gen).
It's very annoying... really!

HT4970 I bought a printer Polaroid POGO, MINI PRINTER. I can not connect it via Bluetooth with my iPhone 4. Is there an app to solve this problem, because I'm Judicial Medical Expert, and I need this tool for quick things. grateful

I bought a printer Polaroid POGO, MINI PRINTER. I can not connect it via Bluetooth with my iPhone 4. Is there an app to solve this problem, because I'm Judicial Medical Expert, and I need this tool for quick things. grateful
Max Cavichini
Medical Legal Expert
Problem ipad and i phone

This has never been a feature of iphone,ipod touch or ipad.

Hi i got a mac mini but when i connect it to my smartax mt882 modem via ethernet it says device not connected can anyone solve this issue it work fine with the usb connection but the ethernet is giving me problems plz help

hi i got a mac mini but when i connect it to my smartax mt882 modem via ethernet it says device not connected can anyone solve this issue it work fine with the usb connection but the ethernet is giving me problems plz help

Hello, give this a try...
Make a New Location, Using network locations in Mac OS X ...
http://support.apple.com/kb/HT2712
10.5, 10.6, 10.7 & 10.8…
System Preferences>Network, top of window>Locations>Edit Locations, little plus icon, give it a name.
10.5.x/10.6.x/10.7.x/10.8.x instructions...
System Preferences>Network, click on the little gear at the bottom next to the + & - icons, (unlock lock first if locked), choose Set Service Order.
The interface that connects to the Internet should be dragged to the top of the list.
For 10.5/10.6/10.7/10.8, System Preferences>Network, unlock the lock if need be, highlight the Interface you use to connect to Internet, click on the advanced button, click on the DNS tab, click on the little plus icon, then add these numbers...
208.67.222.222
208.67.220.220
(There may be better or faster DNS numbers in your area, but these should be a good test).
Click OK.

[SOLVED]netctl not connected

Similar Messages

Maybe you are looking for