Connecting with secure wireless

Hi, this is my 1st venture with an apple computer but I seem to have hit a wall already.
I am using a wireless G unbranded router that is secured by a 10 digit WEP passcode, it can also be set up to use WPA but I had trouble with the vista laptop that connects to the network using WPA, there is also an XP laptop which will connect using either. I believe the WEP is only 64 bit so I'll try upping it to 128 and see what happens. For information there are 3 laptops that need to connect all with different operating systems, OSX, XP & Vista.
The problem is my MBP doesn't like the secured connection, it will connect wirelessly if the connection is unsecured or it will connect via ethernet so I know it can communicate with the router.
If I secure the connection by WEP then it says connection failed or if I do it by WPA then it says connection timed out, at no time does it have trouble seeing the network.
Does anyone know what i need to do to get it working. I believe the WEP is only 64 bit so I'll try upping it to 128 and see what happens but does anyone else have any other ideas?
Many thanks
James

Right I am very pleased to say that I am typing this on my secured wireless connection, I could go on about how much I'm loving the laptop but I'm sure you already know.
I have noticed that when I reboot or put it to sleep that when it comes back on it won't connect again, it says that none of my prefered networks are available but when I click connect it remembers the key but states login failed. In order to connect I use the assist function then diagnostics, select airport, select my network, it then asks if my network is PPPoE or DHCP, I select DHCP, then it scans and states that the connection appears to be working correctly and I'm able to use the net.
I have to do this everytime, I have updated to the latest software available for everything but it's made no difference. Is there anything that I am doing wrong?
Thanks again

Similar Messages

T61 Wireless Connectivity Issue - can not connect with secure wireless sites

I have a T61 using Windows XP. The internal wireless card was factory installed and has not been upgraded.
My home Internet is Comcast high-speed.
When I take my laptop to a coffee shop, business or other location with a secure wireless network that requires a password, I have not been able to log on. I can see the wireless networks available and can click on the appropriate one, but I never get a window/pop-up box/screen in order to allow me to enter the wifi network's user name and password.
Is this a firewall issue, wireless card issue...or?
I can access unsecured wireless networks where a password is not needed.

Hi lisapapp!
One more thing to check: Is your Windows XP up to date? Older XP releases do not support the newer wireless encryption types which are now in common use (WPA, WPA2). Make sure you have SP3.
I don't work for Lenovo. I'm a crazy volunteer!

Mac mini not keeping connection with Cisco wireless access point

I am trying to get my wife's Mac Mini to keep it's connection with the wireless network at her school. They are using a Cisco access point (not sure of the model) which works fine with my G4 Powerbook and the numerous Macbooks being used there, but for some reason her Mac Mini drops the connection after 4 or 5 minutes, at which point she needs to log right off for it to reconnect (as opposed to just turning the card off and on again). I have already gone through the deletion of the Networkinterfaces.plist file, and recreation of the Airport card profile process, but this only kept the interface active for about 36 hours, then it was back to the same old problem. At this point I am thinking "flakey card"...before I ship it off to Apple, can anyone offer any other possible solutions?

After spending time on the phone with a Apple support technician, he indicated that the Iphone has a compatibility problem with the wep key encryption that the Cisco appliance uses. I find this disturbing being that Cisco is the biggest in network gear. What's UP Apple? We need SP1 for the IPHONE!!!

Having trouble with Airport connecting with Verizon wireless modem.

Having trouble with Airport connecting with Verizon wireless modem. Any ideas?

Haven't asked Verizon. I think it is in my settings for Airport. Need to know proper settings.

Mac mini issue:lost connectivity with the wireless keyboard

I lost connectivity with the wireless keyboard and I can't unlock the lock screen.What can i do?

Sometimes powering the keyboard off by holding in the power button on the right end of the battery box and then after ten of so seconds powering up again will reestablish the connection. Other than that forcing a reboot using the power switch on the mini should restore the connection unless thereis something else going on.
If this is a recurring problem try replacing the batteries with fresh ones. If this keyboard has been paired with another bluetooth device such as an iPad or another Mac, unpair it from the other device.

Loose wireless connection with security turned on

I am able to get a wireless connection when the wireless network has no security enabled. But when the security is turned on - using WEP or WPA (TKIP) - I can no longer get a connection. The error message says that the password is not correct (however it is).
Of note: I have another G4 (aluminum 1.33 GHz) running the same version of OS X that does not have a problem connecting with the security turned on.
I have the same problem at home or with other wireless networks that require passwords.
At home I have a linksys wireless router.
Thanks!
1 GHz PowerPC G4 Mac OS X (10.4.8)

i have a very similar situation to yours... my airport cannont get an IP address from any wireless network with security enabled. if it is completely open, it will lock in and get an IP address and everything is fine, but with ANY kind of security enabled, it wont get an IP and gives me the standard "169...." addresses. If i turn off security on a given base station, the machine will suddenly get an IP address, so I know this is a problem with the machine and not the router as other wifi devices connect to the router fine.
I've tried using standard WEP, WPA, and also MAC-address security and i get the same problem across all of them. Ive tried this with about 5 different routers, 3 linksys, 1 netgear and one dLink.

Using AEBS with non-wireless Mac mini to connect with modem wirelessly

Daughter has a Mac mini w/o wifi on 2nd floor and DSL wifi modem which must be located on 1st floor. Due to other old computer, modem is configured to 64-bit WEP for wireless. Want to add mini to her network. (I've discovered that 40-bit mode on AEBS is really 64-bit mode.)
I'm trying to use a new Airport Extreme Base station by connecting mini to AEBS via Ethernet cable. Then I'm hoping to configure AEBS to connect to the DSL modem wirelessly - don't know if that is possible. I tried setting AEBS to "join a wireless network". It finds the DSL network, so I enter the modem's password. I've then gone through a number of configurations on AEBS but each time, when AEBS restarts, it doesn't get out of yellow blinking light or (on one try if I recall correctly) I got the green light - but then Airport Utility is never able to find AEBS and I end up starting from scratch by resetting AEBS.
1) Can I even use AEBS to connect to a wireless network and have a Mac wired to it so the Mac can reach the Internet?
2) if yes, what wireless mode should I set AEBS to? What other settings do I need to get right?
Thanks

This is a "n" version of AEBS.
Please refer back to the previous posts. I was talking about an AirPort Express (AX) as the device that has this special feature.
Ironically, the less expensive AirPort Express will do what you want with a special feature that allows it to "join" a wireless network and then enable the Ethernet port.
If you have an AirPort Express 802.11n, I will post the steps for you if you want them.

Unable to connect with the wireless feature

I have the Linksys WRT54G version 8.0, it bridges with my DSL modem. I have 3 wired desktops and 1 wireless laptop (which does not connect without wired connection). According to the easylink advisor, we do not have an internet connection. But I have internet connection as long as all 4 computers are wired in. My problem now is we have a new ps3 and can not do the wireless connection. I have checked all settings on router page and still shows no connection. What am I doing wrong? How do I fix this? I can get on-line just can't use wireless. Can anyone help?
Thanks,
Sharon

You need to do Port Forwarding on your Linksys Router...
Open an Internet Explorer browser page.In the address bar type - 192.168.1.1
Leave username blank & in password use admin in lower case...
Click on "Applications and Gaming" tab and then click on "Port Range Forwarding" subtab...
1) On the first line in Application box type in ABC, in the start box type in 80 and End box type in 80, leave the protocol as both and under ip address type in 192.168.1.20 and check the enable box...
2) On the second line in Application box type in DEF, in the start box type in 443 and End box type in 443, leave the protocol as both and under ip address type in 192.168.1.20 and check the enable box...
3) On the first line in Application box type in GHI, in the start box type in 5223 and End box type in 5223, leave the protocol as both and under ip address type in 192.168.1.20 and check the enable box...
4) On the first line in Application box type in JKL, in the start box type in 3478 and End box type in 3479, leave the protocol as both and under ip address type in 192.168.1.20 and check the enable box...
5) On the first line in Application box type in MNO, in the start box type in 3658 and End box type in 3658, leave the protocol as both and under ip address type in 192.168.1.20 and check the enable box...
6) On the first line in Application box type in PQR, in the start box type in 10070 and End box type in 10080, leave the protocol as both and under ip address type in 192.168.1.20 and check the enable box and click on Save Settings
7) Now assign the given ip address on your PlayStation
ip address :- 192.168.1.20, subnet mask :- 255.255.255.0, default gateway :- 192.168.1.1...
8) Also assign the dns addresses on the PlayStation
Primary dns :- 4.2.2.2...Secondary dns :- 192.168.1.1
9) Turn off your modem, router, and PlayStation...Wait for a minute...
10) Plug the modem power first, wait for another minute and plug the router power cable, wait another minute and turn on the PlayStation and test it...
As your PlayStation is Wireless make sure you are connected to your Wireless Network...

Network Manager fails to connect with Sierra Wireless 3G/4G modem

Hi,
I have three Asus Laptops running with Arch (Asus N56VZ, Asus F3JC, Asus UL80VS). All laptops work with Cinnamon Desktop. Everything works fine except 3G Modem in Network Manager. I have two USB modems: Sierra Wireless AirCard 310U and Sierra Wireless AirCard 320U.
Modems had worked fine in end of year 2012, when NetworkManager version was 0.9.6.4 and ModemManager 0.6.0.0. After update (NM >0.8.X.X, MM >0.7.X. - when the ModemManager.service appeared) until now, I can't connect to the internet on all Asus laptops. Since 2013 I have to use wvdial, because in wvdial modems works fine. It is Arch problem, because in Linux Mint 15 I can connect with NetworkManager.
Sierra AirCard 310U - When I'm connecting to the internet, modem reboots itself.
Sierra AirCard 320U - When I'm connecting to the internet, Network Manager can't obtain DHCP address.
I would be grateful for any help.
Sierra Wireless AirCard 310U (USB 3G Modem) log:
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) starting connection 'Orange PL'
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled...
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started...
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete.
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Simple connect started...
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Simple connect state (3/8): Enable
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <warn> (ttyUSB2): port attributes not fully set
aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '0', MNC: '0', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:41:39 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '260', MNC: '3', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:41:40 AsusN56VZ kernel: usb 3-2: USB disconnect, device number 3
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ ModemManager[308]: mm_serial_port_close: assertion `priv->open_count > 0' failed
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (4/8): Wait to get fully enabled
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (5/8): Register
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> (tty/ttyUSB2): released by modem /sys/devices/pci0000:00/0000:00:14.0/usb3/3-2
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (6/8): Bearer
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB0: Sierra USB modem converter now disconnected from ttyUSB0
aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.0: device disconnected
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: Sierra USB modem converter now disconnected from ttyUSB1
aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.1: device disconnected
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: Sierra USB modem converter now disconnected from ttyUSB2
aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.3: device disconnected
aug 22 13:41:40 AsusN56VZ kernel: sierra_net 3-2:1.7 wwp0s20u2i7: unregister 'sierra_net' usb-0000:00:14.0-2, Sierra Wireless USB-to-WWAN Modem
aug 22 13:41:40 AsusN56VZ kernel: ModemManager[308]: segfault at 28 ip 0000000000433350 sp 00007ffff409e088 error 4 in ModemManager[400000+e0000]
aug 22 13:41:40 AsusN56VZ systemd[1]: ModemManager.service: main process exited, code=dumped, status=11/SEGV
aug 22 13:41:40 AsusN56VZ systemd[1]: Unit ModemManager.service entered failed state.
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> ModemManager disappeared from bus
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): device state change: prepare -> unmanaged (reason 'removed') [40 10 36]
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): deactivating device (reason 'removed') [36]
aug 22 13:41:40 AsusN56VZ laptop-mode[2414]: Laptop mode
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): cleaning up...
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): taking down device.
aug 22 13:41:40 AsusN56VZ laptop-mode[2415]: enabled, not active
aug 22 13:41:40 AsusN56VZ systemd-coredump[2336]: Process 308 (ModemManager) dumped core.
aug 22 13:41:40 AsusN56VZ systemd[1]: Starting Modem Manager...
aug 22 13:41:40 AsusN56VZ systemd[1]: ModemManager.service holdoff time over, scheduling restart.
aug 22 13:41:40 AsusN56VZ systemd[1]: Stopping Modem Manager...
aug 22 13:41:40 AsusN56VZ systemd[1]: Starting Modem Manager...
aug 22 13:41:43 AsusN56VZ kernel: sierra_net 3-2:1.7 (unregistered net_device): usb_control_msg failed, status -19
Sierra Wireless AirCard 320U (3G/4G Modem) log:
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) starting connection 'Orange PL'
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) scheduled...
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) started...
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) complete.
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Simple connect started...
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Simple connect state (3/8): Enable
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (disabled -> enabling)
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <warn> (ttyUSB3): port attributes not fully set
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <warn> (ttyUSB4): port attributes not fully set
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (unknown -> registering)
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (registering -> home)
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP location updated (MCC: '0', MNC: '0', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP location updated (MCC: '260', MNC: '3', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (enabling -> registered)
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (4/8): Wait to get fully enabled
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (5/8): Register
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (6/8): Bearer
aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> WWAN now enabled by management service
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (7/8): Connect
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (registered -> connecting)
aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: signal quality updated (40)
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: access technology changed (unknown -> hsdpa, hsupa)
aug 22 13:48:09 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (connecting -> connected)
aug 22 13:48:09 AsusN56VZ ModemManager[314]: <info> Simple connect state (8/8): All done
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) scheduled...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) starting...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: prepare -> config (reason 'none') [40 50 0]
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): bringing up device.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) successful.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) scheduled.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) complete.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) started...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: config -> ip-config (reason 'none') [50 70 0]
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (wwp0s20u2i7) Beginning DHCPv4 transaction (timeout in 45 seconds)
aug 22 13:48:09 AsusN56VZ kernel: IPv6: ADDRCONF(NETDEV_UP): wwp0s20u2i7: link is not ready
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> dhclient started with pid 2351
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) complete.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) started...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) complete.
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Internet Systems Consortium DHCP Client 4.2.5-P1
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Copyright 2004-2013 Internet Systems Consortium.
aug 22 13:48:09 AsusN56VZ dhclient[2351]: All rights reserved.
aug 22 13:48:09 AsusN56VZ dhclient[2351]: For info, please visit https://www.isc.org/software/dhcp/
aug 22 13:48:09 AsusN56VZ dhclient[2351]:
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (wwp0s20u2i7): DHCPv4 state changed nbi -> preinit
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Listening on LPF/wwp0s20u2i7/8e:1d:fe:e0:02:07
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Sending on LPF/wwp0s20u2i7/8e:1d:fe:e0:02:07
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Sending on Socket/fallback
aug 22 13:48:09 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 5
aug 22 13:48:14 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 5
aug 22 13:48:19 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
aug 22 13:48:26 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
aug 22 13:48:33 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
aug 22 13:48:36 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: signal quality updated (40)
aug 22 13:48:40 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 10
aug 22 13:48:50 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 17
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <warn> (wwp0s20u2i7): DHCPv4 request timed out.
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (wwp0s20u2i7): canceled DHCP transaction, DHCP client pid 2351
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) started...
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <warn> Activation (ttyUSB3) failed for connection 'Orange PL'
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) complete.
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: failed -> disconnected (reason 'none') [120 30 0]
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): deactivating device (reason 'none') [0]
aug 22 13:48:54 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (connected -> disconnecting)
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'connected' --> 'disconnecting' (reason: user-requested)
Last edited by Shocker (2013-09-14 20:08:08)

Shocker wrote:I don't think it's kernel problem, because Linux Mint 15 have kernel 3.8 and there is everything fine. Maybe systemd (Fedora & Arch have systemd, but Mint sysvinit..), maybe version of dhcpcd, I have no idea...
To test, I downgraded my kernel
~ ᐅ uname -r
3.9.5-301.fc19.x86_64.debug
And now I see in messages
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) starting connection 'Telstra'
Sep 15 09:46:17 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) scheduled...
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) started...
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) complete.
Sep 15 09:46:17 localhost modem-manager[757]: <info> (ttyUSB2) opening serial port...
Sep 15 09:46:17 localhost modem-manager[757]: <warn> (ttyUSB2): port attributes not fully set
Sep 15 09:46:17 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled -> enabling)
Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <info> (ttyUSB2) opening serial port...
Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <warn> (ttyUSB2): port attributes not fully set
Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled -> enabling)
Sep 15 09:46:18 localhost dbus-daemon[618]: modem-manager[757]: <info> (ttyUSB2): using PDU mode for SMS
Sep 15 09:46:18 localhost modem-manager[757]: <info> (ttyUSB2): using PDU mode for SMS
Sep 15 09:46:18 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabling -> enabled)
Sep 15 09:46:18 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabling -> enabled)
Sep 15 09:46:18 localhost NetworkManager[724]: <info> WWAN now enabled by management service
Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabled -> registered)
Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabled -> registered)
Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (registered -> connecting)
Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (registered -> connecting)
Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (connecting -> connected)
Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (connecting -> connected)
Sep 15 09:46:19 localhost kernel: [ 5056.773068] IPv6: ADDRCONF(NETDEV_UP): wwp0s29u1u1i7: link is not ready
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) scheduled...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) starting...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: prepare -> config (reason 'none') [40 50 0]
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): bringing up device.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) successful.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) complete.
Sep 15 09:46:19 localhost avahi-daemon[607]: Registering new address record for fe80::c0c3:a2ff:fe4a:207 on wwp0s29u1u1i7.*.
Sep 15 09:46:19 localhost kernel: [ 5056.876750] IPv6: ADDRCONF(NETDEV_CHANGE): wwp0s29u1u1i7: link becomes ready
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) started...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: config -> ip-config (reason 'none') [50 70 0]
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Beginning DHCPv4 transaction (timeout in 45 seconds)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> dhclient started with pid 10376
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) complete.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) started...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Sep 15 09:46:19 localhost dhclient[10376]: Internet Systems Consortium DHCP Client 4.2.5
Sep 15 09:46:19 localhost dhclient[10376]: Copyright 2004-2013 Internet Systems Consortium.
Sep 15 09:46:19 localhost dhclient[10376]: All rights reserved.
Sep 15 09:46:19 localhost dhclient[10376]: For info, please visit https://www.isc.org/software/dhcp/
Sep 15 09:46:19 localhost dhclient[10376]:
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed nbi -> preinit
Sep 15 09:46:19 localhost dhclient[10376]: Listening on LPF/wwp0s29u1u1i7/c2:c3:a2:4a:02:07
Sep 15 09:46:19 localhost dhclient[10376]: Sending on LPF/wwp0s29u1u1i7/c2:c3:a2:4a:02:07
Sep 15 09:46:19 localhost dhclient[10376]: Sending on Socket/fallback
Sep 15 09:46:19 localhost dhclient[10376]: DHCPREQUEST on wwp0s29u1u1i7 to 255.255.255.255 port 67 (xid=0x6e8c90b2)
Sep 15 09:46:19 localhost dhclient[10376]: DHCPNAK from 10.102.67.253 (xid=0x6e8c90b2)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed preinit -> expire
Sep 15 09:46:19 localhost dhclient[10376]: DHCPDISCOVER on wwp0s29u1u1i7 to 255.255.255.255 port 67 interval 6 (xid=0xae2cec8)
Sep 15 09:46:19 localhost dhclient[10376]: DHCPREQUEST on wwp0s29u1u1i7 to 255.255.255.255 port 67 (xid=0xae2cec8)
Sep 15 09:46:19 localhost dhclient[10376]: DHCPOFFER from 10.102.67.253
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed expire -> preinit
Sep 15 09:46:19 localhost dhclient[10376]: DHCPACK from 10.102.67.253 (xid=0xae2cec8)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed preinit -> bound
Sep 15 09:46:19 localhost NetworkManager[724]: <info> address 10.102.67.12
Sep 15 09:46:19 localhost NetworkManager[724]: <info> prefix 24 (255.255.255.0)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> gateway 10.102.67.12
Sep 15 09:46:19 localhost NetworkManager[724]: <info> nameserver '10.4.81.103'
Sep 15 09:46:19 localhost NetworkManager[724]: <info> nameserver '10.4.182.20'
Sep 15 09:46:19 localhost NetworkManager[724]: nm_ip4_config_add_wins: assertion `wins > 0' failed
Sep 15 09:46:19 localhost NetworkManager[724]: <info> wins '0.0.0.0'
Sep 15 09:46:19 localhost NetworkManager[724]: nm_ip4_config_add_wins: assertion `wins > 0' failed
Sep 15 09:46:19 localhost NetworkManager[724]: <info> wins '0.0.0.0'
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Commit) started...
Sep 15 09:46:19 localhost avahi-daemon[607]: Joining mDNS multicast group on interface wwp0s29u1u1i7.IPv4 with address 10.102.67.12.
Sep 15 09:46:19 localhost avahi-daemon[607]: New relevant interface wwp0s29u1u1i7.IPv4 for mDNS.
Sep 15 09:46:19 localhost avahi-daemon[607]: Registering new address record for 10.102.67.12 on wwp0s29u1u1i7.IPv4.
Sep 15 09:46:19 localhost dhclient[10376]: bound to 10.102.67.12 -- renewal in 97473 seconds.
Sep 15 09:46:20 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Sep 15 09:46:20 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Commit) complete.
Sep 15 09:46:20 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: secondaries -> activated (reason 'none') [90 100 0]
Sep 15 09:46:20 localhost NetworkManager[724]: <info> Policy set 'Telstra' (wwp0s29u1u1i7) as default for IPv4 routing and DNS.
Sep 15 09:46:20 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) successful, device activated.
I'm going to ask on #fedora and see how i can best diagnose what's going on. At least I now have it working, albeit on an older kernel.
Last edited by qnm (2013-09-14 23:48:05)

Wireless LAN cannot connect with the wireless router with Windows 8.1

Hi,
I currently have a Lenovo V570 laptop with Windows 8.1 running on it. I cannot seem to stay connected to a wireless wifi connection for more than 10 minutes without it going "limited" and a yellow caution exclamation icon hovering over my connected wifi icon.
When it goes limited, I cannot access the internet whatsoever and it's growing increasingly frustrating. I used to have success by disconnected and reconnecting which seemed to temporarily solve the issue, but now even that is not working.
I did not have this issue (I don't believe so) when I first installed Windows 8 on this laptop a few years ago. This is an issue I've been dealing with for over a year now and only within the past 4-6 months has it been really bad.
I found this support page here which provides solutions for my problem but after attempting all of them, unfortunately none of them worked. The only time I experience no issues is when I directly connect an ethernet cord from my laptop to the router.
The wireless problem exists for all wifi connections, whether it be my university wifi, home wifi, local, etc.
Can anybody please help me out? I'd be more than happy to provide additional info to get this problem fixed once and for all.

Hi,
I currently have a Lenovo V570 laptop with Windows 8.1 running on it. I cannot seem to stay connected to a wireless wifi connection for more than 10 minutes without it going "limited" and a yellow caution exclamation icon hovering over my connected wifi icon.
When it goes limited, I cannot access the internet whatsoever and it's growing increasingly frustrating. I used to have success by disconnected and reconnecting which seemed to temporarily solve the issue, but now even that is not working.
I did not have this issue (I don't believe so) when I first installed Windows 8 on this laptop a few years ago. This is an issue I've been dealing with for over a year now and only within the past 4-6 months has it been really bad.
I found this support page here which provides solutions for my problem but after attempting all of them, unfortunately none of them worked. The only time I experience no issues is when I directly connect an ethernet cord from my laptop to the router.
The wireless problem exists for all wifi connections, whether it be my university wifi, home wifi, local, etc.
Can anybody please help me out? I'd be more than happy to provide additional info to get this problem fixed once and for all.

TS1398 how do i configure so i phone connects with home wireless automatically? currently, it connects to prior owners wireless since disconnected.

how do i configure wifi so my Iphone connects w home wireless automatically?

Hi Tesserax
You could, but its benefits may depend on how you have it configured with the D-Link router. That is, do you have the TC directly connected to the D-Link by Ethernet or is it just wirelessly joining the D-Links' wireless network?
I have the TC connected via Ethernet cable.
I am assuming that you have the 802.11n AirPort Express Base Station (AXn) configured as a wireless client so that it can join the D-Link's wireless network for iTunes streaming ... correct? If so, then it would be performing like any other wireless client (desktop, laptop, printer, etc.) and will not interfere with the D-Link's wireless network.
I rechecked the AE and you are correct that the AE is set to join a wireless network.
With having so many devices running on the wireless network, would it make sense to have a few device on each wireless system?(D-Link, TC, and AE)
I know it sounds like overkill, but there is the possibility that all the devices could be running at once. I'm not sure if that would cause any conflicts.
Is there any advantage to turning on the wireless on TC just for the iPhones for example or is it better to keep things as they are?(It works but is it efficient?)
Please be aware I'm not fully knowledgeable with wireless routers and their capabilities.

Connecting with a Wireless Printer on Home Hub 3.

How do I get a XP Notebook to connect with the HP Photosmart 6510 connected wirelessly to my BT Home Hub 3.
My Network Places shows BT Home Hub 3.
Double click on HH3 and scrolling down to My Home Network.
You can see HPFE0AAB under wireless network, which is the HP Photosmart 6510.
According to the Photosmart it’s url is 192.168.7.71 and it is correctly connected to the hub.
The XP Notebook does have the relevant basic printing drivers installed for the Photosmart.
Perhaps I should add that I gave up trying to connect the Windows 8 Desktop to the printer wirelessly and used a USB instead. I’m not sure if the problem is with the set up of the Notebook or the Hub. I have tried turning off firewalls which so far seems to make no difference. I am running MSE on the Notebook and Defender on the Desk Top.
I've tried so many approaches I'mgoing round in circles.
Solved!
Go to Solution.

Here are the GENERAL steps on how to add a wireless printer on your wireless network.
As you have said that it is already connected and visible to the network it is a case of checking the settings below then if ok go to “adding printer to your networked computer” section
The wireless printer must have a static (i.e., manual) IP address assigned to it from your network IP address range. It cannot be DHCP enabled, otherwise every time DHCP assigns a new address, your printer port will stop working.
How to set a manual IP address on your printer:
When the printer is connected to the network the first time, the router will assign an IP address to it. To get the IP address that the printer was assigned, find the printer on your network and right click on it. It will bring up a properties box. The IP address for the printer will be found somewhere in there.
Using an Internet browser, type the IP address of the printer into the address line of the browser and press enter. It should bring up a printer configuration window.
Now, since each printer is different, I can't give you the exact steps, HOWEVER, here's what you are looking for:
Find a Network - TCP/IP configuration menu. Somewhere in that menu, it will give you the choice of setting a manual or static IP address versus a DHCP (Dynamic Host Control Protocol) assigned address.
You want to manually set the IP address to the address given on the configuration page. This would normally be 192.168.1.xx. The subnet mask will normally be 255.255.255.0 and the gateway will normally be the IP of the router, usually 192.168.1.254
Once the IP address is assigned permanently to the printer as a static address, you are now ready to add the printer to each computer on your network.
Add the Printer to Your Networked Computers
In Windows XP, follow these steps to add the wireless printer to your computer:
Go to Start, Printers and Faxes.
Double click on Add Printer
Click Next.
On the Local or Network Printer dialog box, choose Local Printer and UNCHECK the box that says "Automatically detect" the printer. Click Next.
On the Select a Printer Port window, choose to Create a New Port, and then under Type of Port, choose Standard TCP/IP port. Click Next.
Make sure the printer is On and Ready, and connected to the network. Click Next.
Type in the static IP address of the printer that you set in the steps above. Click Next.
It will then try to connect to that IP address. It you typed it wrong, or the printer is off, it will come back and give you an error.
If all is well, it should then ask you for the printer driver. Either set it to find the driver that you have previously installed or insert the CD for the printer, and find the Windows XP version of the driver.
Then choose the driver you want to install.
Click Next. It will install the driver and ask you to name the printer.
When it is done, click Finish. (You can choose to print a test page if you want).
Hope this helps.

Dropping wireless connection with Apple Wireless Keyboard

I've got a new bluetooth chip in my iMac from support at my location, a new wireless keyboard and I'm still having issues. Wireless connection dropped 6 times typing this one sentence. Aaargh. I've been busy with this ever since I bought the computer. On irregular intervals (absolutely no regularity whatsoever) the computer loses connection with my Apple Wireless Keyboard. So if I have a new iMac, with a new bluetooth chip and a new keyboard how come this issue is still an issue? It's driving me mad. And possibly the guys at the centre as well.

Hi mvoltage
Do you have any appliances with motors or other mobil telephone devices setup near the iMac?
Both motor flux fields and Cordless Phone Base Stations can and will interfere with the operation of the iMac's wifi and airport signals.
Dennis

Connecting to Secure Wireless

Hello Everyone! I have had my MacBook for about 8 months now, and it seems that whenever I try to connect to a wireless network that requires me to sign in on a web page (ie a bookstore or downtown wireless network) it rarely lets me open the web page to do all the log in. Usually it just says that I cannot connect to the internet, but it has worked in the past. So, I am just a little confused about how to troubleshoot this all.

You would want to connect the ethernet cable from your computer to one of the 3 LAN <-> ports on the Time Capsule.
I've had good luck by powering down both the computer and the Time Capsule, then connecting the cable and powering up the computer first for a few minutes, then the Time Capsule.
If the TC does not appear at first when you open AirPort Utility, leave the application open as sometimes the TC will just "appear" after a few minutes.

Why is my mac is not connecting with the wireless keyboard

For two days my iMac hasn't been connecting with the keyboard, I changed the batteries for the keyboard but it's still to working. Any suggestions?

If you're using IP addresses in the 192.168.x.x range they are not information that anyone here can use to "get at" your machines. So, please reply with the following information from one of your devices that works, and then it will be clear what IP addressing scheme you have that the mini needs to fit into:
ip address
subnet mask
default gateway
DNS server
DHCP server
if your access to the internet is via a router/gateway, those devices usually have a web interface for administration. It would be helpful to use it to find out the range of IP addresses that are being used for DHCP. Using the exact same IP configuration on one machine that another already uses causes IP address conflicts, and the last machine to try to use the conflicting address will have its address disabled, so that's why the last thing you tried didn't work.

Connecting with secure wireless

Similar Messages

Maybe you are looking for