BH 905 odd problem (wired connection)

heres an odd one.....
the headset connects via bluetooth perfectly...
using the wired connection it doesnt....well not really
if i have the headset placed to my ears and pull out the connection
from the 3.5mm jack and device(n900) i hear a "click"/slight distortion...
like you would regularly hear IF it was properly connected....
using another wired headset....and connecting them to the n900 3.5mm jack
as works well....
using the wired connection of the BH 905's to connect to another device...they
too work well....
just not on the n900...
i should also say they used to work the wired way before but then just stopped...
suggestions/advice?
Solved!
Go to Solution.

seems it was a software issue that was never rectified...
solution 1. get a new wired connection similar to what nokia gave in the box (the wired part that fits into the headset and into the device)
solution 2. push the 3.5mm side into the device partly (like 1st/2nd black mark on the 3.5mm)..you will/should hear distortion in the headset...once u hear that push the jack fully in...should work...
NOTE: there will be no headset icon most times

Similar Messages

I'm having some odd problems staying connected to the Internet on my Macboo

I just got the computer earlier this year, in June, I think, and it has worked wonderfully until today, when my family got a new router to replace our defective one. Whenever I close and open my Macbook Pro or my sister closes/opens her Macbook, we have to enter the WEP key again, despite the fact that the computer seems to think that it's already connected to the network. The three little bar things are all black, but I can't access anything on the internet until I enter the WEP key. If I have to do this for a while, it's going to get really irritating. Can anyone help? Is it our computers or the router?

I just got the computer earlier this year, in June, I think, and it has worked wonderfully until today, when my family got a new router to replace our defective one.
Is it our computers or the router?
Pretty clearly it is the "new Router" unless you changed something on both computers as a part of installing the new router - did you?
Whenever I close and open my Macbook Pro or my sister closes/opens her Macbook, we have to enter the WEP key again
I think you are saying that the person who closed their MB has to log in again - but maybe you saying that both of you have to log in even when the other one closes their computer - is it only the person who closed their computer?
Do you get a prompt to enter the key again? is the key the same as it was on the old router?
LN

Wired Connection problem on Officejet Pro 8500 a909a

I am having what seems to be to be a strange problem.
I have lost connectivity to my printer (Officejet Pro 8500 a909a) through the network from my Windows 7 64bit computer. I found that it worked fine if I connect throught he USB port. Today, I have been trying to get back to being able to use it through the network.
I am able to get to the configuration on the printer through the network, at http://192.168.0.105 and that works fine.
I have downloaded the most recent software and when I run it, it doesn't detect the printer, even if I enter the ip address in the advanced search box.
I have downloaded the HP Print and Scan Doctor, and when it runs, I can see the printer, however i'm not sure why it shows 2 lines:
When I choose the last line and press next, all it does is goes to this page:
Your help is appreciated.

What operating system does the computer use?
What happens when you choose the network-wired option on that last screen? Since the printer is already installed, the software thinks you are wanting to install the printer again and presents the last screen.
Your printer is listed twice with two separate IP addresses. I suspect the issue may be that the IP address is changing to frequently for the detection protocol to keep up with it.
If the printer is on the network and you can access it by entering the printer's IP address in a web browser, you can try setting a static IP address for the wired connection. Click on the Printer Does Not Maintain Wireless Connection document from HP. The document is for wireless connections, but the same steps can be applied for a wired connection by substituting wired for any section that designates going to the wireless section of the printer.
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

Windows 8.1 wired connection problem

My computer with Windows 8.1 started to lose internet connection very often (about every minute). I tried to update drivers for network card, even bought new network card with no result. Also, tried to connect directly without router and connection
still drops. Network troubleshooting did not find any problems, no errors are displaying. What may be causing the problem?

Hi,
Wired connection, have you checked the cable? Please make sure that it's functioning fine.
You can also test the connection with another PC to find out whether the culprit is your own PC or the ISP.
Yolanda Zhu
TechNet Community Support

Problem - keep getting an intermittent connection (wired connection)

For the last few months our internet connection has been completely intermittent. Some days it will work perfectly fine all day long, other days like today it will disconnect / reconnect every 30 seconds - 5 minutes. I tried doing Live Chat several times and most of the times I can't even get through their questions before my net disconnects. One time I did manage to let them take over control of my computer to "fix" the problems, and at that given moment it worked. But literally as soon as the person disconnected from my computer my net died again.
Part of our setup uses Vonage, which means if the internet does not work our phone doesn't work. I hardly think Vonage is the problem because it works perfectly fine other days. Same goes with the Verizon people saying gaming can effect it which shouldn't be a problem either. I've tried to use my cell to call them but as soon as I go downstairs to mess with the modem / router my phone loses service.
It seems like this is a day to day problem. Last night my internet was perfectly fine, today it keeps disconnecting. Power cycles fix the problem for a few seconds to a few minutes, and letting it reset itself does the same thing. As i'm typing this post my internet has disconnected several times. I can't seem to figure out the problem and need some advice.
Information:
Computer connection - Wired
OS - Windows XP
Modem - Actiontec GT704WG
Here is what the system log says:
(GMT-05:00)15:25:19 Fri Jul 03 2009 udhcpd: interface: br0, start : 4001a8c0 end : fe01a8c0
(GMT-05:00)15:25:23 Fri Jul 03 2009 syslog: No response for DNS request to server 71.242.0.12 yet.
(GMT-05:00)15:25:23 Fri Jul 03 2009 syslog: No response for DNS request to server 71.242.0.12 yet.
(GMT-05:00)15:25:25 Fri Jul 03 2009 syslog: No response for DNS request to server 71.252.0.12 yet.
(GMT-05:00)15:25:25 Fri Jul 03 2009 syslog: All DNS servers tried, no response.
(GMT-05:00)15:25:25 Fri Jul 03 2009 syslog: No response for DNS request to server 71.252.0.12 yet.
(GMT-05:00)15:25:25 Fri Jul 03 2009 syslog: All DNS servers tried, no response.
(GMT-05:00)15:25:25 Fri Jul 03 2009 syslog: failed dns request len=76,srcip=192.168.1.1, url=amedsatxb6130.amed.ds.army.mil
(GMT-05:00)15:25:25 Fri Jul 03 2009 syslog: failed dns request len=76,srcip=192.168.1.1, url=amedsatxb6130.amed.ds.army.mil
(GMT-05:00)15:25:26 Fri Jul 03 2009 syslog: failed dns request len=138,srcip=4.2.2.2, url=amedsatxb6130.amed.ds.army.mil
(GMT-05:00)15:25:30 Fri Jul 03 2009 syslog: No response for DNS request to server 71.242.0.12 yet.
(GMT-05:00)15:25:30 Fri Jul 03 2009 syslog: No response for DNS request to server 71.242.0.12 yet.
(GMT-05:00)15:25:32 Fri Jul 03 2009 syslog: failed dns request len=133,srcip=4.2.2.2, url=amedsatxb6130.ds.army.mil
(GMT-05:00)15:25:32 Fri Jul 03 2009 syslog: failed dns request len=133,srcip=4.2.2.2, url=amedsatxb6130.ds.army.mil
(GMT-05:00)15:25:32 Fri Jul 03 2009 syslog: No response for DNS request to server 71.252.0.12 yet.
(GMT-05:00)15:25:32 Fri Jul 03 2009 syslog: All DNS servers tried, no response.
(GMT-05:00)15:25:32 Fri Jul 03 2009 syslog: No response for DNS request to server 71.252.0.12 yet.
(GMT-05:00)15:25:32 Fri Jul 03 2009 syslog: All DNS servers tried, no response.
(GMT-05:00)15:25:32 Fri Jul 03 2009 syslog: failed dns request len=71,srcip=192.168.1.1, url=amedsatxb6130.ds.army.mil
(GMT-05:00)15:25:32 Fri Jul 03 2009 syslog: failed dns request len=71,srcip=192.168.1.1, url=amedsatxb6130.ds.army.mil
(GMT-05:00)15:26:13 Fri Jul 03 2009 syslog: No response for DNS request to server 71.242.0.12 yet.
(GMT-05:00)15:26:14 Fri Jul 03 2009 syslog: failed dns request len=138,srcip=4.2.2.2, url=amedsmapgr105.amed.ds.army.mil
(GMT-05:00)15:26:16 Fri Jul 03 2009 syslog: No response for DNS request to server 71.252.0.12 yet.
(GMT-05:00)15:26:16 Fri Jul 03 2009 syslog: All DNS servers tried, no response.
(GMT-05:00)15:26:16 Fri Jul 03 2009 syslog: failed dns request len=76,srcip=192.168.1.1, url=amedsmapgr105.amed.ds.army.mil
*All of that repeated SEVERAL times from 15:26 - 15:31*

SNR Margin (Downstream/Upstream):23/12
Attenuation (Downstream/Upstream):18/12
I think those are the numbers you are talking about. At this moment in time my internet is working fine today, but that doesn't mean by later today/tonight or tomorrow it will be acting the same. Since it's an ongoing problem I'd like to try and fix whatever may be causing it anyway.
I'll have to figure out how exactly our lines are configured before describing them, but i'll try and give you the entire setup of our network at least. So here it goes:
Our setup is in the basement:
Modem/Router - Actiontec GT704WG
No filter coming from main phone line to modem (Is this supposed to be filtered?)
Ethernet 1 -> Vonage -> Motorola VT2542-VD
-Phone line from Vonage goes to "Multi-line" box (I'm not sure if it is a filter itself..)
-From the multi-line 2 separate phone lines coming off with filters
-Those 2 connect into 2 possible filters, that connect into spiltters for the lines through the house.
House Phones:
-1st Floor - Kitchen phone is a regular phone (no filter)
-1st Floor - Living room has a 5.8GHz portable (no filter)
-1st Floor - Sun room has a portable set from the 5.8GHz
-2nd Floor - My room has a portable set from the 5.8GHz
-2nd Floor - Office has a regular phone (no filter)
-2nd Floor - Bedroom has 2 regular phones (no filters)
(I'm guessing the house phones don't need filters directly because they are already filtered?)
Ethernet 2 - My room, connection goes into a Linksys 10/100 5-port workgroup switch (model: EZXS55W). PS3, 360, and PC all wired connections to the switch.
Ethernet 3 - Brother's room, connection goes to his laptop (he doesn't use it wirelessly much in the house)
Ethernet 4 - Office room, connection goes to laptop (not used wirelessly either.)
Besides having an extremely complicated set of lines, I was wondering if the length of ALL the Ethernet and Phone lines matter? Also I read in the other topic that if they don't have Xbox / Playstation they should disable UPnP, and since I do, should i actually ENABLE it? I know that's un-related to my problem but if it makes online gaming connections better i'll do it. I used to have Static IP's for my PS3 / 360 / PC and "rules" setup that supposedly opened the Ports to make them better online but I didn't really notice any increased speeds when downloading off them or playing online.
If I need to provide more info please let me know. Or what should be the next step I take....

[Solved] Wired connection ok but wireless problem on Intel 5100

Here is how i solved the problem :
1 - get back to the wiki doing everything in order
2 - added dbus in attition to hal in the deamon line in rc.conf
3 - put wicd at the end of the deamon line
4 - then configured wicd for my wireless network at boot : no more dbus error, and connection perfectly ok
Thx very much for the superb wiki, certainly my fault if i messed up but i still have to learn
Hi
I've got a problem with the wireless connection on my toshiba R10
my wired connection is working flawlessly but i can't use my wifi card. I'm using arch 2009.8 i686
Here is what i've done following the wiki :
1 : installed ifplugd for the RJ45 connection + added the deamon on my rc.conf
2 : installed wireless-tools
3 : installed the driver intel 5100
# pacman -S iwlwifi-5000-ucode
set up my mod_autolog yes
here is my ifconfig -a
[me@arch ~]$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:1C:7E:83:EB:B4
inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21c:7eff:fe83:ebb4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:603 errors:0 dropped:0 overruns:0 frame:0
TX packets:610 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:329491 (321.7 Kb) TX bytes:84091 (82.1 Kb)
Memory:ffcc0000-ffce0000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:66 errors:0 dropped:0 overruns:0 frame:0
TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4400 (4.2 Kb) TX bytes:4400 (4.2 Kb)
wlan0 Link encap:Ethernet HWaddr 00:22:FB:04:1A:72
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wmaster0 Link encap:UNSPEC HWaddr 00-22-FB-04-1A-72-00-00-00-00-00-00-00-00-00-00
UP RUNNING MTU:0 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
I have a dbus error : « Could not connect to wicd's D-Bus interface. Check the wicd log for error messages. »
so i modified my configuration file following this topic on the french forum http://forums.archlinux.fr/topic3967.html (same error message)
here is my rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="fr_FR.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Europe/Paris"
KEYMAP="fr-pc"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="arch"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp" )
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng hal network ifplugd netfs slim crond alsa fam)
i tried to start wicd manually but it stay busy infinitely :
here is my /etc/wicd/manager-setting.conf
GNU nano 2.0.9 Fichier : /etc/wicd/manager-settings.conf
[Settings]
wireless_interface = wlan0
pref_width = 450
window_width = 530
prefer_wired = False
flush_tool = 0
use_global_dns = False
global_dns_dom = None
always_show_wired_interface = True
sudo_app = 0
global_dns_1 = None
global_dns_2 = None
global_dns_3 = None
backend = external
link_detect_tool = 0
dhcp_client = 0
window_height = 529
wired_connect_mode = 1
debug_mode = 0
sudo_app = 0
global_dns_1 = None
global_dns_2 = None
global_dns_3 = None
backend = external
link_detect_tool = 0
dhcp_client = 0
window_height = 529
wired_connect_mode = 1
debug_mode = 0
pref_height = 450
wired_interface = eth0
signal_display_type = 1
global_search_dom = None
auto_reconnect = True
wpa_driver = wext
and what i get ont the graphical interface : no wireless network found
here is my "ps aux | grep dbus"
[root@arch ~]# ps aux | grep dbus
dbus 1373 0.0 0.0 2252 940 ? Ss 14:27 0:00 /usr/bin/dbus-daemon --system
me 1703 0.0 0.0 3156 696 ? S 14:27 0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
me 1704 0.0 0.0 2264 972 ? Ss 14:27 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
root 2794 0.0 0.0 3892 872 pts/1 S+ 15:11 0:00 grep dbus
in the preference settings of wicd, it's correct : eth0 as wired connection and wlan0 as wireless
here is my "iwlist wlan0"
[root@arch ~]# iwlist wlan0 scanning
wlan0 No scan results
i've tried a lspci -vv :
[me@arch ~]$ lspci -vv
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
Subsystem: Toshiba America Info Systems Device 0001
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 0
Capabilities: <access denied>
Kernel driver in use: agpgart-intel
Kernel modules: intel-agp
00:03.0 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller (rev 07)
Subsystem: Toshiba America Info Systems Device 0001
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at ffcff000 (64-bit, non-prefetchable) [size=16]
Capabilities: <access denied>
Kernel driver in use: heci
Kernel modules: heci
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
Subsystem: Toshiba America Info Systems Device 0001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 28
Region 0: Memory at ffcc0000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at ffcfe000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at cf80 [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
Subsystem: Toshiba America Info Systems Device 0001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Capabilities: <access denied>
Kernel modules: iTCO_wdt
01:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
Subsystem: Intel Corporation Device 1301
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 29
Region 0: Memory at ff900000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlagn
Kernel modules: iwlagn
I suspect that something is wrong between iwlagn and iwlwifi-5000 which can cause this problem.
I have to say that I'm quite lost here, i hope someone will have an idea
thank you very much
Last edited by Janarto (2009-08-30 02:46:18)

Stab in the dark...the hal daemon should start dbus, but sometimes I've been encouraged to add the dbus DAEMON explicitly (before hal).
I don't really understand dbus too intimately, but I've come across situations where although dbus is running, I can't talk to it because the DBUS_SESSION_BUS_{ADDRESS,PID,WINDOWID} variables weren't visible in the environment I was working in. For instance, if dbus is started by xinitrc, and then some system-level daemon tries to talk to dbus, usually it fails for me, and I have to use some workaround.
Now I would expect wicd to be set up so that the ordinary user doesn't encounter any problems of this sort. On the other hand, the error you're getting does say that it's dbus communication which is failing. Perhaps you could try shutting down hald and dbus, open a terminal, su -, /etc/rc.d/dbus start, and then try from that command line to tell wicd to connect?

Problem w/ WRT54G connecting with ADSL modem...no Internet even when 'wired' connected

Hi ladies/gents,
need help...not sure what to do...
i have ADSL modem, and i have a cable running from the modem to the "internet" port of my Linksys router. i have another cable from Port 1 (or whichever) to my laptop. modem works/is connected, router works/is connected, cables are good.
YET, i am getting NO internet...forget wireless here...i am just talking about the simple wired connection here and it is not giving me any Internet. If i disconnect the modem cable from the Internet port and connect directly to laptop, then Internet works fine....frustrating.
i do know that the ISP says that they use Automatic DHCP (or something like that)
Any ideas!?

This is not really a fix, however, what I found out from having the same problem (Limited or no connectivity) is for some reason my verizon modem (Westell 6100) and the router (Wrt54g) had the same IP address. I changed the router IP address several time and it would alway end up with the same problem.
What I ended up doing (mind you its for no other reason than I wanted to connect to the internet and was sick of the problem) was connect my modem to the #1 port of the router and use the other three ports for my computers thinking that if they had the same IP address maybe it would work that way. I know very little about how this stuff work but it did fix my problem. I have been hooked up that way for months and haven't lost speed or connection since. I hope this helps and maybe someday someone who know why it works will tell me so I will know.
Good Luck !!
SRV2121

QuickVPN problem - Wireless no connect, wired connect

I'm trying to connect to an RVS4000 at the office using QuickVPN on a laptop.
My home router is a WRV54G. After spending way too much time trying to get this thing to work using the wireless connection to the laptop I tried installing the client on my desktop and it worked. I then tried connecting the laptop to the wired connection and it worked also. It appears as though the wireless connection is the problem. I installed the newest version of the client I could find to another laptop and had the same problem on the wireless. Yet I can connect using TheGreenbow on another laptop to another VPN over this same wireless connection.
Wasting way too much time on this one... Any Ideas?

Do you mean you cant connect to the quick vpn using your wireless computer? And then if you connect the wireless laptop directly(hardwired) to the router , you can connect to the quick vpn? Have you tried other wireless computer to check if you can connect to your quick vpn?

I have a windows 8 computer. I can't connect my ipad when I have a wired connection. I have to unplug it and connect wireless. Is anyone else having this problem?

I have a windows 8 computer. I can't connect my Ipad to Itunes wirelessly when my computer is a wired connection. I have to disconnect my ethernet cable from the computer and connect as a wifi connection.Then the Ipad shows up in Itunes.Any sugestions?

I'd start with the following user tip:
iTunes for Windows 10.7.0.21: "iTunes has stopped working" error messages when playing videos, video podcasts, movies and TV shows

Home Sharing problem between Mini Server and ATV2 using wired Connection

I am HomeSharing my Itunes Library in a Mac Mini Server late 2010 running Lion Client with an ATV2 Through a Wired Gigabit Switch. With out Success. It only works with the Wireless Connection. Which takes out the point of the Gigabit wired Connection of the Mini server with the rest of the network.
The complete Configuration is
The Mini Server provides Content to a Mac Mini Core Duo, ATV 1 and ATV 2 all through the Gigabit Switch.
The Wireless Network Provides content to three Ipads.
Huawai Modem (Firewall and DHCP), Time Capsule (4rd Generation) in Bridge Mode but Brodcasting Wireless Network, TP-Link 8 port Gigabit Switch.
Any help is greatly appreciated.
Luis

Hi Allan!
I suggest you replace your switch for a router. The purpose of a router is to connect two networks. In your case it would connect your local computer network (Macs, server and PC) to the Internet. Having your DSL on a switch with the rest of your machines means that only one at a time should be able to connect to the Internet.
Hope this helps! bill
1 GHz Powerbook G4 Mac OS X (10.4.8)

Wired connection doesn't work if cable is not plugged in at boot time

Hey all,
I started using arch a few days ago and I simply love it, but I have a problem. The wired connection doesn't work if the cable is not plugged in at boot time, or if it was plugged in at boot time, then plugged out and in again. Switching it off and on again via the gui has the same effect. I am using NetworkManager with dhcpcd, NetworkManager is started via systemd, dhcpcd is not, I let NetworkManager do that. When I started investigating this problem there were some remnants of netctl, but now NetworkManager is the only networking-related service started at boot time. When the cable is plugged back in, NM-applet shows that it's connected, and an IP address is assigned, but the connection doesn't work.
Here's some information regarding the system:
It's a lenovo G50-70 laptop, it uses the r8169 driver for ethernet. (I dualboot it with windows 8.1, but arch is default and all this stuff happens also if i only use arch)
The router is a Linksys EA2700/N600
journalctl -u NetworkManager
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> NetworkManager (version 0.9.10.1) is starting...
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> WEXT support is enabled
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkMan
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/Bokros
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/1. vezetékes kapcsolat
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/UPC1838142
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> monitoring kernel firmware directory '/usr/lib/firmware'.
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:02:00.0/iee
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC20
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> WiFi hardware radio set enabled
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> WWAN hardware radio set enabled
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wifi.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wwan.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-adsl.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WiFi enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WWAN enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WiMAX enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Networking is enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): link connected
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): carrier is ON
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): carrier is OFF
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): new Ethernet device (driver: 'r8169' ifindex: 2)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): exported as /org/freedesktop/NetworkManager/Devices/1
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
aug 26 19:14:36 arch_daboka systemd[1]: Started Network Manager.
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): preparing device
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): using nl80211 for WiFi device control
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): driver supports Access Point (AP) mode
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): exported as /org/freedesktop/NetworkManager/Devices/2
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): preparing device
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> use BlueZ version 5
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> wpa_supplicant started
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0) supports 4 scan SSIDs
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: starting -> ready
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: ready -> disconnected
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0) supports 4 scan SSIDs
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: disconnected -> inactive
aug 26 19:14:42 arch_daboka NetworkManager[527]: <info> startup complete
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Auto-activating connection 'Bokros'.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) starting connection 'Bokros'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTING
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0/wireless): connection 'Bokros' has security, and secrets exist. No new sec
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'ssid' value 'Bokros'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'scan_ssid' value '1'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'psk' value '<omitted>'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: set interface ap_scan to 1
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: inactive -> authenticating
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: authenticating -> associated
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: associated -> 4-way handshake
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: 4-way handshake -> completed
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireles
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) scheduled.
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) started...
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: config -> ip-config (reason 'none') [50 70 0]
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> dhcpcd started with pid 3599
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) complete.
aug 26 19:15:01 arch_daboka dhcpcd[3599]: version 6.4.3 starting
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: version 6.4.3 starting
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
aug 26 19:15:01 arch_daboka dhcpcd[3599]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:01 arch_daboka dhcpcd[3599]: wlp2s0: IAID 65:59:c9:b5
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: IAID 65:59:c9:b5
aug 26 19:15:01 arch_daboka dhcpcd[3599]: wlp2s0: soliciting an IPv6 router
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: soliciting an IPv6 router
aug 26 19:15:02 arch_daboka dhcpcd[3599]: wlp2s0: rebinding lease of 192.168.1.137
aug 26 19:15:02 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: rebinding lease of 192.168.1.137
aug 26 19:15:07 arch_daboka dhcpcd[3599]: wlp2s0: leased 192.168.1.137 for 86400 seconds
aug 26 19:15:07 arch_daboka dhcpcd[3599]: wlp2s0: adding route to 192.168.1.0/24
aug 26 19:15:07 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: leased 192.168.1.137 for 86400 seconds
aug 26 19:15:07 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: adding route to 192.168.1.0/24
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): DHCPv4 state changed preinit -> reboot
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> address 192.168.1.137
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> plen 24 (255.255.255.0)
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> gateway 192.168.1.1
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> server identifier 192.168.1.1
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> lease time 86400
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> hostname 'arch_daboka'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> nameserver '192.168.1.1'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> domain name 'chello.hu'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Commit) started...
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Commit) complete.
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_GLOBAL
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Policy set 'Bokros' (wlp2s0) as default for IPv4 routing and DNS.
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Writing DNS information to /usr/bin/resolvconf
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) successful, device activated.
aug 26 19:15:14 arch_daboka dhcpcd[3599]: wlp2s0: no IPv6 Routers available
aug 26 19:15:14 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: no IPv6 Routers available
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): link connected
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 4
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Auto-activating connection '1. vezetékes kapcsolat'.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) starting connection '1. vezetékes kapcsolat'
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) scheduled...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) started...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) scheduled...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) complete.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) starting...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: prepare -> config (reason 'none') [40 50 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) successful.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) scheduled.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) complete.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) started...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: config -> ip-config (reason 'none') [50 70 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> dhcpcd started with pid 4322
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) complete.
aug 26 19:15:34 arch_daboka dhcpcd[4322]: version 6.4.3 starting
aug 26 19:15:34 arch_daboka dhcpcd[4322]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: IAID 44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: version 6.4.3 starting
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: IAID 44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): DHCPv4 state changed nbi -> preinit
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: soliciting an IPv6 router
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: soliciting an IPv6 router
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: rebinding lease of 192.168.1.138
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: rebinding lease of 192.168.1.138
aug 26 19:15:39 arch_daboka dhcpcd[4322]: enp1s0: leased 192.168.1.138 for 86400 seconds
aug 26 19:15:39 arch_daboka dhcpcd[4322]: enp1s0: adding route to 192.168.1.0/24
aug 26 19:15:39 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: leased 192.168.1.138 for 86400 seconds
aug 26 19:15:39 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: adding route to 192.168.1.0/24
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): DHCPv4 state changed preinit -> reboot
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> address 192.168.1.138
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> plen 24 (255.255.255.0)
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> gateway 192.168.1.1
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> server identifier 192.168.1.1
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> lease time 86400
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> hostname 'arch_daboka'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> nameserver '192.168.1.1'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> domain name 'chello.hu'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Commit) started...
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Commit) complete.
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_GLOBAL
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Policy set '1. vezetékes kapcsolat' (enp1s0) as default for IPv4 routing and DNS.
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Writing DNS information to /usr/bin/resolvconf
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) successful, device activated.
aug 26 19:15:47 arch_daboka dhcpcd[4322]: enp1s0: no IPv6 Routers available
aug 26 19:15:47 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: no IPv6 Routers available
ping -c 10 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=4.38 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.79 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=4.89 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=5.30 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.59 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.61 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=4.37 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=2.40 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=6.47 ms
--- 192.168.1.1 ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9014ms
rtt min/avg/max/mdev = 1.599/3.759/6.471/1.627 ms
ping -c 100 8.8.8.8 - it's not completely disconnected, but it's always 8 packets at once that are received
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=20 ttl=46 time=41.7 ms
64 bytes from 8.8.8.8: icmp_seq=21 ttl=46 time=40.0 ms
64 bytes from 8.8.8.8: icmp_seq=22 ttl=46 time=38.8 ms
64 bytes from 8.8.8.8: icmp_seq=23 ttl=46 time=39.3 ms
64 bytes from 8.8.8.8: icmp_seq=24 ttl=46 time=41.8 ms
64 bytes from 8.8.8.8: icmp_seq=25 ttl=46 time=38.4 ms
64 bytes from 8.8.8.8: icmp_seq=26 ttl=46 time=38.4 ms
64 bytes from 8.8.8.8: icmp_seq=27 ttl=46 time=38.0 ms
64 bytes from 8.8.8.8: icmp_seq=56 ttl=46 time=43.4 ms
64 bytes from 8.8.8.8: icmp_seq=57 ttl=46 time=49.8 ms
64 bytes from 8.8.8.8: icmp_seq=58 ttl=46 time=40.2 ms
64 bytes from 8.8.8.8: icmp_seq=59 ttl=46 time=44.3 ms
64 bytes from 8.8.8.8: icmp_seq=60 ttl=46 time=38.5 ms
64 bytes from 8.8.8.8: icmp_seq=61 ttl=46 time=43.4 ms
64 bytes from 8.8.8.8: icmp_seq=62 ttl=46 time=39.2 ms
64 bytes from 8.8.8.8: icmp_seq=63 ttl=46 time=40.5 ms
64 bytes from 8.8.8.8: icmp_seq=92 ttl=46 time=38.3 ms
64 bytes from 8.8.8.8: icmp_seq=93 ttl=46 time=43.7 ms
64 bytes from 8.8.8.8: icmp_seq=94 ttl=46 time=42.3 ms
64 bytes from 8.8.8.8: icmp_seq=95 ttl=46 time=46.6 ms
64 bytes from 8.8.8.8: icmp_seq=96 ttl=46 time=44.9 ms
64 bytes from 8.8.8.8: icmp_seq=97 ttl=46 time=42.9 ms
64 bytes from 8.8.8.8: icmp_seq=98 ttl=46 time=41.7 ms
64 bytes from 8.8.8.8: icmp_seq=99 ttl=46 time=37.8 ms
--- 8.8.8.8 ping statistics ---
100 packets transmitted, 24 received, 76% packet loss, time 99062ms
rtt min/avg/max/mdev = 37.886/41.455/49.829/3.000 ms
cat /etc/dhcpcd.conf - I tried clientid instead of duid and disabling IPv6, but neither of those helped.
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Inform the DHCP server of our hostname for DDNS.
hostname
# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
duid
# Persist interface configuration when dhcpcd exits.
persistent
# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
# Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private
# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
#noipv4ll
#Disable IPv6
#noipv6rs
#noipv6
cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=keyfile
dhcp=dhcpcd
## Set static hostname
#[keyfile]
#hostname=foobar
## HTTP-based connectivity check
#[connectivity]
#uri=http://nmcheck.gnome.org/check_network_status.txt
I couldn't find anything else to append, but if there are other log or conf files or anything else, which would help solving the problem, I should put here, please tell me.

Try to use dhclient perhaps? Might I also suggest letting systemd deal with the dhcp issue and not NM. That may seem incongruous but it is possible NM is mis-handling the dhcp hand-off to the network card. I'm no guru but I got thinking about this when I saw this in your output:
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
It is very possible that I'm mis-interpreting this information so please take it with a boulder of salt.

How do I disconnect from Wireless to use wired connection?

Hi - I'm new to this and I apologize if this question is ridiculously easy.
I am using a cable modem in which I have plugged my WRT160Nv2 wireless router. I am supporting three computers here in my home; my laptop (both wired and wireless), my daughters laptop (wireless only), and my desktop (wired only).
Everything works great and I have to give all the credit to CISCO and the excellent software which automatically solves every connection problem that comes up.
My laptop and desktop are connected to the wireless router via cable.
My question is strictly about my laptop. When I leave my office in the house and go into another room, I establish the wireless connection. Now I am back in my home office room, I want to use my wired connection. How do I do this? Do I need to disable my wireless connection so that my wired connection takes over? Again, I do have my laptop connected to the wireless router via cat5.
I want to do this strictly for the speed of the connection. I've read that a wired connection is double if not more in Mbps.
This laptop is running Win XP Pro, SP3.
I hope this furnishes enough info to assist in an answer.
Thanks in advance.
John
P.S.. I really do want to educate myself regarding the equipment I am using and not have to ask such basic questions. Are there any books or websites you can recommend that can start me out and go as technical as I choose to?

Windows by default uses the fastest connection possible. If you have a wireless and wired connection active at the same time it depends on how fast both connections are rated. Wireless connections tend to change depending on the distance. Wireless 802.11g goes up to 54 Mbit/s. Wireless 802.11n can go up to some 300 Mbit/s. Wired connections are usually either gigabit ethernet (1000 Mbit/s) or fastethernet (100 Mbit/s).
Thus, which is picked depends on your computer. You should check the connection status of both connections in the network connections control panel. It shows you the current wireless and wired speed (the latter won't change of course). Very often, the wired connection is preferred to the wireless connection. Now with 802.11n connections the wireless connection is preferred if your wired connection is only fastethernet.
As your WRT160Nv2 has only FastEthernet LAN ports you have to check how fast the wireless connection is. If you have a 802.11n wireless adapter in your laptop it may show up the wireless connection faster then 100 Mbit/s. Depending on the setting it may change occassionally between 54 Mbit/s and speeds higher then 100 Mbit/s which would lead Windows to swap connections. If you see that problem it is better to switch off the wireless in the laptop while you have a wired connection...
A wired connection is more reliable and stable then a wireless connection. With wireless you can have interference. Thus, even though a wired connection may be slower then a wireless one you may prefer to use the wired connection anyway. And some people prefer to turn off the wireless to avoid radiation.
To sum up: usually you don't have to switch off the wireless, unless you experience problems because of the mentioned changing speeds of the wireless connection. The computer will always only use one connection. Not both.

Apple Airprint to HP Officejet 6500A Plus via Wired Connection to Router

Hi There,
So I've done a considerable amount of research into this across the internet and this forum and I'm still struggling to find a satisfactory solution.
I have an HP Officejet 6500A Plus connected by ethernet into my BT Homehub 3.
It is my understanding that even though this is a wired connection, as long as my iOS device (iPad 2 or iPhone 5) is connected to the same router, I should still be able to see this Officejet over through the airprint facility.
Unfortunately this is not the case. I only get the "No Airprint Printers Found" message on both devices. The only way I have managed to get my Mac Pro (Mavericks) to connect was to mannualy add using the IP address for the printer.
Can anyone give any guidance as to what I might be doing wrong? The printer is definitely connecting to the internet as I can print from my iOS devices using HP ePrint app for iOS.
Some might say well what is the problem, just use the HP app but this is not point. I believe if something has been implemented to make things easier then use it. I chose this printer specifically for this functionality so it's a little frustrating to find it so difficult to achieve the desired results.
Hope it's something straightforward and someone can help.
Thanks,
Steve
This question was solved.
View Solution.

Further to this request, and reading many more similar issues, I think I may resolved this.
I am not 100% sure but I have read some threads suggesting there are issues around BT's Homehub 3 and bonjour so this may be an issue.
I have tried the following over the past couple of days...
1) Completely reset my router (wiped all settings and started again) - No luck!
2) Tried changing from WPA2 to just WPA security - No luck!
3) Tried forwarding the bonjour ports to the printer - No luck!
4) Switched off router, printer and all iOS devices then powered back router, printer and then iOS devices - Printer appears on iOS devices but when print was selected, iOS device repeatedly returned Printer Not Connected error.
Finally, what seems to have done it (at least for now) was...
1) Unplugged ethernet from the Officejet and set it up as Wireless connection.
2) Powered down router, printer and all iOS devices then powered back up in the order stated earlier.
3) So far I have tried printing an email and a web page from my iOS devices and both have been sucessful.
Incidentally I had been struggling also to airplay from my iPhone and iPad until I started messing around with settings above and now this issue also seems to be resolved.
Due to variety of combinations (different printers, routers etc) people will have, it seems to be quite difficult to find a solution which addresses an individual problem however I hope some of my experimenting and findings might help others in some way.

H.P.ENVY4500 WILL NOT PRINT UNLESS WIRED CONNECTION IN PLACE

Have just purchased H.P. ENVY 4500 and connected to computor using WiFi-no problem.After connction found it would not print from documents etc.Tried to install disc but this would not start so whent into H.P. website for installation.this installed but then said could not install over network.I'm not very techy so this has me baffled.Then decided to wired connection between printer and computer and this works ?? Wife has a laptop using WiFi and printer responds to this just using WiFi.WHY?? Very grateful if someone can give me some idea as what to do.Many thanks.

Hi @KIP7,
Welcome to the HP Forums!
I understand that your HP Envy 4500 will not print on a wireless network, and I am happy to help!
For further assistance I will need to know: If you are using a Windows or Mac Operating System, and the version number. To find the exact version, visit this link. Whatsmyos.
In the meantime, I would suggest to go through this printing guide. Print Jobs are Stuck in the Print Queue. As it addresses the fact that the printer will not print.
Hope this helps, and hope to hear from you soon!
RnRMusicMan
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to say “Thanks” for helping!

Can't connect by wired connection

I just moved into a new house, and ordered a fios connection through Surewest. I bought a LinkSys E3000 Wireless-N Router, and my iMac is connecting fine to the internet wirelessly...however I'm not getting anything when it's wired to the router.
In network settings it says "connected" in the ethernet section, yet if I turn "airport off" I can't load a single page (despite it saying the ethernet is "connected"). My router also shows that there's an active connection. So I connected the data cable directly from the port (the one that's inside the house, not on the router) to my computer, and I still had the same problem. I don't even know where to begin with, I'm not sure if it's a problem with my internet provider, my router, or my computer.

Hardwire the connection directly from your fios to the computer.
Go to the Network Pref Pane and go to Location > Edit.
Add a new location.
Click Apply at the bottom of the Network window.
Restart the computer.
Go back to the Network Pref Pane -- what is the IP address you have for your ethernet connection?
If you still don't have an internet connection and the IP address is valid (not 169 or 10 or 192) then power cycle your fios connection (if possible). I turn my modem off for at least 30 seconds if not 5 minutes.
If that doesn't take care of it, try your computer at a different hard wired connection (work, school, Apple Store, etc.). If it works some place else but not at home you may want to call Surewest to make sure they are not using provisioning / MAC Address filtering.
Hope that helps.

BH 905 odd problem (wired connection)

Similar Messages

Maybe you are looking for