Network never connects after boot?

every time i reboot my pc i must do sudo dhcpcd eno1. but during the install of arch from the iso on a cd i already did [email protected] and setup my net, why does it not connect automatically, (its Ethernet btw) i cant put it in xinitrc or rc.lua because i have to sudo dhcpcd eno1 which means ill have to enter my password so that wont work unless i add nopassword in sudo file, which i dont want to do.
did i miss a step?

mariusmeyer wrote:
Hm, you may have "solved" the problem by this approach, in this case. However: don't you think it's a good idea to actually learn how to use systemd, instead of just trying lots of stuff in your xinitrc?
For example, systemctl enable foo.service means "from now on, start foo.service at every boot". Do you get why it doesn't make sense to do that every time you log into X?
Another example: what is the big difference between the dhcpcd@ service file and issuing "sudo dhcpcd foo" yourself? If you call dhcpcd directly in xinitrc, why would you need the .service for systemd?
As has been stated in an earlier post here, there is a known bug that might be affecting you.
Please, just feel free to do things you way, as Arch is very much about you making your own system. That being said, systemd is a tool. It makes sense to learn to use the tool if it is going to be a core component of the OS, right? if not for this case, then for the stuff that might happen down the road
Best regards,
because i already tried systemd enabling for 3 machines for wifi and wired, and it doesnt work...hence why i have this thread

Similar Messages

  • No network LAN-connection after iOS 5.1.1update

    Today i tried to solve a big issue after updating my AppleTV's to 5.1.1 (actual version: AppleTV3,1_5.1_10A406e_Restore.ipsw). After updating my Apple TV´s, they could not connect to  the Apple activation server. No Home Sharing was adjustable and also logging in iTunesStore was not possible. The update I have done via LAN cable, and I changed  nothing in my network configuration. The network (networkadress via DHCP) is indeed set up by default in the AppleTV automatically. Nevertheless, nothing went. Then I removed the network cable and made a reset of the AppleTV and tried to connect via Wi-Fi. With Wi-Fi, he finds the activation server and everything works as it should. Home Sharing, iTunes, streaming. However, once the network cable is plugged in and the Apple TV is restarted, it is again not possible to get access the iTunesStore. Home Sharing is not possible. The networkcable are fine. Both MacBook, as well as my TVs have internet connection over the same network cable. If I unplug the network cable from the AppleTV again, anything goes. Only via WLAN, but it's just too slow to stream data from my Mac. I have this "strange behavior" on 3 AppleTV 3.Gen., which are in the apartment. The previous iOS-Version on the same network cables, worked great. Can anyone reproduce the problem? Or have I now 3 bricked devices? I tried to downgrade over itunes. But this is not possible anymore. I installed 3 times the update. But nothing goes. Please can anybody help me.

    I found another link titled "Apple TV Death after update"  and found several links that have proven to work to restore to the previous version.  Here is my post:
    "I had originally replied to a post titled "No network LAN-connection after iOS 5.1.1 update". That has been my issue after updating to 5.1. Wirless worked for me but iTunes match and Podcasts were slow to respond. I finally downgraded to the previous version (5.0.2). So far, my ATV3 has been operating exactly as it did out of the box. No more activation failed message, and all components of ATV are functioning flawlessly on my whole home LAN network.
    I also wonder what Apple was thinking for releasing this update without adaquate testing. I can forgive them for Maps, but not this. ATV has been around long enough for all of the kinks to be worked out and any updates to just plain work. I did like the new menu displays in apps and how you could rearrange the program icons on the home screen.
    Perhaps they will get it right. Some day. But until they show proof that any future updates are correct and provide detailed instructions on how to revert back to a previous version, I will be very leary of updating. Spending a week reading message boards on how to do a simple resotre is not my idea of how to spend my weekends.
    As a side note, I am a PC, so to restore from an .ispw file located on your system, you must press the Alt & Shift keys togather, then click the Restore button, and a window will pop-up so you can select the location for the restore file."
    Directions to restore:
    "Yes you can. I am a PC. Download the .ipsw file and save to your desktop. Unplug the LAN, HDMI and power cable. Connect the usb cable from your laptop to the ATV. If iTunes does not automatically launch, start it. After iTunes is running, plug in the power cable to the ATV. iTunes will recognize the ATV and will open the restore window in iTunes.
    Press the Alt and Shift keys togather, then click on the Restore button. A file window will open so you can navigate to the desktop (or where ever you saved the file). Select the AppleTV3,1_5.-.2_9B830_Restore.ipsw file. iTunes will start the restore process.
    When you see the message that it has completed the restore, unplug the usb cable and power cable. Reconnect the LAN and HDMI cable then plug in the Power cable in that sequence.
    Follow the setup procedure again and all should be as it was before."

  • Peristent Network MIDI connection after restart?

    I am using MacOS X's native MIDI over IP tools to initiate a session between two machines for a fixed installation and am having some problems with a persistent connection between the two. Is there any way to have the virtual MIDI devices (the two computers) re-establish their connection after a restart? I've scoured the net, but can't find a way to make this happen.
    Please advise.
    Mac mini   Mac OS X (10.4.7)  

    OK, no problem as the instructions would still be the same.
    We're talking about two different names here. The "name" of the device can be whatever you want.
    But when you configure the Express to "join" a wireless network, you select the name of the wireless network that the router has created. In other words if the Belkin's wireless network name was Belkin Wireless, that will appear as a choice when you configure the Express to join that network. You will also be asked for the wireless password for that network.
    It's best to only work with the Expess when configuring it. Turn off and disconnect any other printers, etc. until after you have the Express configured.
    If you are still seeing a blinking amber light, open AirPort Utility, click Manual Setup, click on the amber dot and another window will open with a message explaining the error.
    What does the message say?
    If you need to reconfigure the Express again, here are the steps to join a wireless network:
    Connect the Express to your computer with an ethernet cable
    Open AirPort Utility, click Manual Setup
    Click the Wireless tab below the icons
    Wireless Mode would be "Join a wireless network"
    Wireless Network Name would be the name of the network created by the Belkin. Click the selection box to display the available network to be joined.
    Wireless Security would be the same setting as the Belkin network
    Wireless Password would be the password that you use to log onto the Belkin wireless network
    Wireless Password..same as above
    Click the Music Icon at the top
    Enable AirTunes
    Enter passwords if you wish
    Update to save changes.

  • Windows takes an obscenely long time to establish a network connection after booting

    Often, when I reboot my machine for whatever reason, it boots up normally, I log in, it shows my desktop, loads all the icons and then takes upwards of 5 minutes or longer for the networking icon in the taskbar so show that I have network access (shows that
    little blue ring).  Now, normally I wouldn't think this is much of a problem since I've found a blog at one point detailing how to change the address it's using for that confirmation.  However, in this case, I'm unable to use (m)any other windows
    services until it decides I'm connected.
    For instance, I'm unable to open the registry editor - I'll open the start menu, search for regedit and run it, but will no longer be able to use the search tool in the Start menu until the registry editor appears and that won't appear until the network
    configuration decides I'm connected.  If I open a browser (doesn't matter if it's Firefox, Chrome or IE), I'm unable to visit any sites - they say I'm not connected.  I'm unable to open the Network and Sharing center at all - if I try to left or
    right click the network icon in the taskbar, nothing happens.  If I try to visit the Network and Sharing center by typing the address in a folder window, it simply never loads until that icon shows I'm connected.
    In other words, my computer is pretty unusable until Windows decides I do have an internet connection.  A little about that - I've had this problem for about a month now and have experienced it while connected via wire to two different routers (Netgear,
    now Linksys E3000).  That doesn't seem to be the problem. My connection is perfectly fine at all other times except when my system boots (so it shouldn't be the wires) and I've both kept myself updated with all the latest Win7 patches and firmware for
    the netword card + other system components.  Oh, and no other computer on my network has this networking issue.
    My system is running Windows 7 Professional x64 SP1.
    Any thoughts?  Thanks in advance!

    Maybe try this, i am not sure that it will resolve the problem, but it is worth trying anyways.
    http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/eef49e64-157c-4082-8e80-52e48309691f
    Hi All,
    I've seen this problem multiple times, especially with Windows 7 64-bit versions and Enterprise edition.  The source of the problem appears to be the Bonjour service that is installed in the background and set to "Automatic" when installing certain 3rd
    party applications.  Apple applications like iTunes and Adobe applications like Acrobat Professional and Creative Suites have been known to cause this problem.  I've also seen virtualization software like VMWare and VirtualBox cause similar issues
    with network adapters.
    The solution in most of the cases I've come across has been to stop and disable the Bonjour service.  The Bonjour service also masquerades as a service with a name of the format "##Id_String1.6844F930_blahblahblah".  Here's how to disable this service
    in Windows 7:
    Right-Click on Computer > Select 'Manage'
    Expand the 'Services and Applications' section in the bottom of the Left-Nav dialog and Select 'Services'
    Sort the Services list by name and look for either "Bonjour" or the "##Id_String..." name mentioned above
    Right-Click on the service and select 'Properties'
    Click the 'Stop' button to stop the service
    Select 'Disabled' from the 'Startup type' drop down list
    Click 'Apply' and then 'OK'
    Reboot your machine and see if the "Multiple Networks" issue is resolved.  If so, you should have internet connectivity again.
    Hope this helps.
    cheers,
    Aaron

  • Windows 7 Pro not finding network connections after boot camp installation. Is there something special we have to do to get the network (wired and wireless) set up?

    Any suggestions for getting the network connections working on Windows 7 Pro running on a Mac Min with OSX Lion?

    tim-bob wrote:
    Any suggestions for getting the network connections working on Windows 7 Pro running on a Mac Min with OSX Lion?
    If you haven't yet installed the Windows Support Software, that's probably why, so install it now.

  • Wireless network never connects

    My macbook pro (bought july of 2011) just stoped connecting to wireless networks. I tested with other computer and the network is working normaly.
    What's wrong with my mac?

    My macbook pro (bought july of 2011) just stoped connecting to wireless networks. I tested with other computer and the network is working normaly.
    What's wrong with my mac?

  • No wireless connection after pacman update

    I dont get any connection whatsoever after a pacman -Syu . Im using wicd and iwconfig shows the device.
    Im only using wicd and the service should start and connect after booting but it dosnt. If I start the wicd-gtk, it dosnt show the connections. I tried to use wifi-menu but it throws a connection error (gives me the journal -xn)
    Any reason for whats causing this? Ill try to copy every command, but its hard since im posting from another pc.
    Thanks

    jasonwryan wrote:What error messages are in the journal? In wicd's log? What packages were in the upgrade?
    You need to try an narrow down the fault...
    For the packages, I did a full system upgrade. I cant remember how many or what packages were actually upgraded cause they were.. many.
    Im sorry admin! Let me try to copy as much as I can : the journal after using wifi-menu:
    Something interesting is that I see for a second that my wifi is on ( im usng xmonad and dzen ), then it goes off.
    -- Logs begin at Fri 2013-08-23 23:37:07 ART, end at Wed 2013-11-13 22:26:33 ART. --
    Nov 13 16:29:35 linx systemd[339]: Stopped target Default.
    -- Subject: Unit UNIT has finished shutting down
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- Documentation: [url]http://www.freedesktop.org/wiki/Software/systemd/catalog/9d1aaa27d60140bd96365438aad20286[/url]
    -- Unit UNIT has finished shutting down.
    Nov 13 16:29:35 linx systemd[339]: Starting Shutdown.
    -- Subject: Unit UNIT has begun with start-up
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- Unit UNIT has begun starting up.
    Nov 13 16:29:35 linx systemd[339]: Reached target Shutdown.
    -- Subject: Unit UNIT has finished start-up
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- Unit UNIT has finished starting up.
    -- The start-up result is done.
    Nov 13 16:29:35 linx systemd[339]: Starting Exit the Session...
    -- Subject: Unit UNIT has begun with start-up
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- Unit UNIT has begun starting up.
    -- Reboot --
    Nov 13 22:26:32 linx systemd[350]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
    Nov 13 22:26:32 linx systemd[350]: Mounted /sys/kernel/config.
    -- Subject: Unit UNIT has finished start-up
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- Unit UNIT has finished starting up.
    -- The start-up result is done.
    Nov 13 22:26:32 linx systemd[350]: Stopped target Sound Card.
    -- Subject: Unit UNIT has finished shutting down
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- Documentation: [url]http://www.freedesktop.org/wiki/Software/systemd/catalog/9d1aaa27d60140bd96365438aad20286[/url]
    -- Unit UNIT has finished shutting down.
    Nov 13 22:26:32 linx systemd[350]: Starting Default.
    -- Subject: Unit UNIT has begun with start-up
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- Unit UNIT has begun starting up.
    Nov 13 22:26:32 linx systemd[350]: Reached target Default.
    -- Subject: Unit UNIT has finished start-up
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- Unit UNIT has finished starting up.
    -- The start-up result is done.
    Nov 13 22:26:32 linx systemd[350]: Startup finished in 77ms.
    -- Subject: System start-up is now complete
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- All system services necessary queued for starting at boot have been
    -- successfully started. Note that this does not mean that the machine is
    -- now idle as services might still be busy with completing start-up.
    -- Kernel start-up required KERNEL_USEC microseconds.
    -- Initial RAM disk start-up required INITRD_USEC microseconds.
    -- Userspace start-up required 77128 microseconds.
    Last edited by jasonwryan (2013-11-14 01:55:31)

  • Can't connect to the internet right after boot up

    Hey guys, I have an interesting problem in which if I try to use internet right after boot up (via scripts) I can't resolve host names. However, if I try to use the internet right after boot up manually I can resolve host names. I had this problem with a script but I've since rewrote it to work around the problem; however I now seem to have this problem with openVPN and I need this to work. I'll use openVPN as my primary example but the situation was the same for my script.
    Basically, openVPN starts up via systemd and it can't resolve my server's host name. Even 18 hours later. I have 'resolv-retry infinite' in my conf file which as I understand says 'if you can't resolve the host name keep trying to resolve it indefinitely'. I left my computer on overnight and openVPN still could not connect to my server, despite me being able to ping it, have MySQL get data dumps and replicate from it and other software being able to resolve the server's host name. If I restart openVPN, then it works! I rebooted the computer and let it try for a few minutes to connect and it couldn't. I restarted openVPN manually and it resolved the server's host name, 5 minutes after the computer booted up even though it couldn't connect on it's own the previous night.
    Here's openVPN's status as of this post:
    [email protected] - OpenVPN connection to client
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled)
    Active: active (running) since Thu 2013-05-02 14:10:02 MDT; 58min ago
    Process: 248 ExecStart=/usr/sbin/openvpn --cd /etc/openvpn --config /etc/openvpn/%i.conf --daemon openvpn@%i (code=exited, status=0/SUCCESS)
    Main PID: 254 (openvpn)
    CGroup: name=systemd:/system/[email protected]/client
    ââ254 /usr/sbin/openvpn --cd /etc/openvpn --config /etc/openvpn/client.conf --daemon openvpn@client
    May 02 15:07:52 CCH001 openvpn@client[254]: RESOLVE: Cannot resolve host address: my.server.com: Name or service not known
    May 02 15:07:57 CCH001 openvpn@client[254]: RESOLVE: Cannot resolve host address: my.server.com: Name or service not known
    May 02 15:08:02 CCH001 openvpn@client[254]: RESOLVE: Cannot resolve host address: my.server.com: Name or service not known
    May 02 15:08:07 CCH001 openvpn@client[254]: RESOLVE: Cannot resolve host address: my.server.com: Name or service not known
    May 02 15:08:12 CCH001 openvpn@client[254]: RESOLVE: Cannot resolve host address: my.server.com: Name or service not known
    May 02 15:08:17 CCH001 openvpn@client[254]: RESOLVE: Cannot resolve host address: my.server.com: Name or service not known
    May 02 15:08:22 CCH001 openvpn@client[254]: RESOLVE: Cannot resolve host address: my.server.com: Name or service not known
    May 02 15:08:27 CCH001 openvpn@client[254]: RESOLVE: Cannot resolve host address: my.server.com: Name or service not known
    May 02 15:08:32 CCH001 openvpn@client[254]: RESOLVE: Cannot resolve host address: my.server.com: Name or service not known
    May 02 15:08:37 CCH001 openvpn@client[254]: RESOLVE: Cannot resolve host address: my.server.com: Name or service not known
    Here is my conf file:
    # Sample client-side OpenVPN 2.0 config file #
    # for connecting to multi-client server. #
    # This configuration can be used by multiple #
    # clients, however each client should have #
    # its own cert and key files. #
    # On Windows, you might want to rename this #
    # file so it has a .ovpn extension #
    # Specify that we are a client and that we
    # will be pulling certain config file directives
    # from the server.
    client
    # Use the same setting as you are using on
    # the server.
    # On most systems, the VPN will not function
    # unless you partially or fully disable
    # the firewall for the TUN/TAP interface.
    ;dev tap
    dev tun
    # Windows needs the TAP-Win32 adapter name
    # from the Network Connections panel
    # if you have more than one. On XP SP2,
    # you may need to disable the firewall
    # for the TAP adapter.
    ;dev-node MyTap
    # Are we connecting to a TCP or
    # UDP server? Use the same setting as
    # on the server.
    ;proto tcp
    proto udp
    # The hostname/IP and port of the server.
    # You can have multiple remote entries
    # to load balance between the servers.
    remote my.server.com 1194
    ;remote my-server-2 1194
    # Choose a random host from the remote
    # list for load-balancing. Otherwise
    # try hosts in the order specified.
    ;remote-random
    # Keep trying indefinitely to resolve the
    # host name of the OpenVPN server. Very useful
    # on machines which are not permanently connected
    # to the internet such as laptops.
    resolv-retry infinite
    # Most clients don't need to bind to
    # a specific local port number.
    nobind
    # Downgrade privileges after initialization (non-Windows only)
    user nobody
    group nobody
    # Try to preserve some state across restarts.
    persist-key
    persist-tun
    # If you are connecting through an
    # HTTP proxy to reach the actual OpenVPN
    # server, put the proxy server/IP and
    # port number here. See the man page
    # if your proxy server requires
    # authentication.
    ;http-proxy-retry # retry on connection failures
    ;http-proxy [proxy server] [proxy port #]
    # Wireless networks often produce a lot
    # of duplicate packets. Set this flag
    # to silence duplicate packet warnings.
    ;mute-replay-warnings
    # SSL/TLS parms.
    # See the server config file for more
    # description. It's best to use
    # a separate .crt/.key file pair
    # for each client. A single ca
    # file can be used for all clients.
    ca ca.crt
    cert host.crt
    key host.key
    # Verify server certificate by checking
    # that the certicate has the nsCertType
    # field set to "server". This is an
    # important precaution to protect against
    # a potential attack discussed here:
    # http://openvpn.net/howto.html#mitm
    # To use this feature, you will need to generate
    # your server certificates with the nsCertType
    # field set to "server". The build-key-server
    # script in the easy-rsa folder will do this.
    ns-cert-type server
    # If a tls-auth key is used on the server
    # then every client must also have the key.
    tls-auth ta.key 1
    # Select a cryptographic cipher.
    # If the cipher option is used on the server
    # then you must also specify it here.
    ;cipher x
    # Enable compression on the VPN link.
    # Don't enable this unless it is also
    # enabled in the server config file.
    comp-lzo
    # Set log file verbosity.
    verb 3
    # Silence repeating messages
    ;mute 20
    Anyone have any idea what could be going on? It seems to me that when a program starts up it takes a snap shot of the current network status and it then uses it, even if it's 10 minutes later and the network has been fully loaded/configured, the program uses that snap shot and can't connect to the DNS.
    Last edited by anEveryDayGuy (2013-05-02 21:20:47)

    'Requires=network.target' wasn't in it so I added it but nothing's changed. I've left it in because openVPN does require network.
    As I said, I had this problem with a script so I don't think it's anything specific to openVPN. I had a weird occurrence this morning however. When I started the computer up this morning  openVPN worked just fine. However when the computer rebooted openVPN couldn't resolve the host address again.

  • Airport connection not enabled after boot

    Hi, I have noticed recently that if I reboot the iMac, after shutting down or using Boot Camp for my Winslows apps, that Airport doesn't connect to my wireless network. It is easy to select the network to connect to, but I don't think I should have to do this every time. Does anyone have any ideas?

    bossman,
    Welcome to discussions.
    Why don't you use the Network System Preference to prioritise how you connect to your network, which network you connect to, and even get it to store the password in your Keychain.
    Fire up the Network System Preference. What is your Location at the top ?
    Then chose Network Status from the Show: popup menu underneath (should be the default anyway). What connection methods does it show ? Which one is at the top ? Which ones have green dots next to them ? and which have yellow dots ? And which have red dots ?
    Is AirPort even on ?

  • Start network connection during boot [KDE4]

    I want to able to connect to a network (with key) during boot.
    Right now, when my arch is booting, it is trying to connect to a dhcpcd during boot, but fails (after several seconds). Then knetworkmanager and even wicd doesn't seem to work correctly. Knetworkmanager (from KDEmod) seems like doesn't work at all.
    What can I do to make it connect during boot? (I usually connect only to one network).

    I got it working.. however, I am wondering if I have everything right in my rc.config file, in DAEMONS section (maybe I have there something extra, which I can turn off).
    #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=(wireless-wep)
    # 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 network netfs net-profiles hal !networkmanager crond alsa kdm)
    Which one do I need? network, netfs? net-profiles?
    Last edited by kdar (2009-12-16 02:17:01)

  • My IPhone 4 never connects to a Wi-Fi network. It's supposed to connect to "known" networks automatically. Other networks pop up but the join box never is active. My Wi-Fi and Ask to join networks are both "ON" but nothing seems to work. Would appreciate

    My iPhone 4 never connects to a Wi-Fi network even though it's supposed to connect to ?known? networks. My Wi-Fi and Ask to join boxes are both "ON." Other networks pop up but the "JOIN' boxes never work. Would appreciate some help on how to connect. Thanks

    Never has or this is a recent development?
    If no change after resetting network settings at Settings > General > Reset > Reset Network Settings, try restoring your iPhone with iTunes as a new iPhone or not from the backup.
    If no change after that, your iPhone has a hardware problem.

  • My i Phone drops WiFi connection after just a few minutes and wont reconnect unless I reset the network settings and reboot the  phone?

    My i Phone 4s has suddenly started to drop wifi connection after nealy months of near perfect connections?
    To restore a wifi connection I have to reset the network settings and restart the phone, this only fixes the issues for around 2-3 mins?
    Other quick fixes like switching wifi on and off/ switching to airoplane mode for a few secconds have no impact.
    This is really annoying as I am using my data allowence very quickly, and as the phone is continually searching for a wifi connection the battery time has reduced dramatically.
    I just wondered if any one else has the same issue, and any suggestions as to how I can fix this.
    Thanks in Advance

    Reboot.
    Restore (from backup)
    Restore (as new)
    Test after each step. If one of them doesn't fix the problem, make an appointment at the genius bar.

  • MBP takes long time to restore wired network connection after wake-up

    Hello...
    My Mid-2010 MBP (MacBookPro6,2) has been experiencing this problem recently -- Whenever I wake up the computer from sleep, it needs approximately 10 seconds to restore its wired network connection. I know there are other annoying connection issues with MBP's WiFi/AirPort out there, but I'm talking about the wired connection here.
    Maybe some don't even think this slowness is a problem at all, but this laptop used to be network-ready right after wake-up until 3~4 months ago. That was around the time when I upgraded to SSD and changed some settings via pmset, not sure if that's the culprit. It is now running OS X 10.8.5 and its pmset settings are:
    Battery Power:
    lidwake              1
    ttyskeepawake        1
    hibernatemode        3
    gpuswitch            2
    hibernatefile        /var/vm/sleepimage
    displaysleep         2
    sleep                15
    acwake               0
    halfdim              1
    sms                  0
    lessbright           1
    disksleep            10
    AC Power:
    lidwake              1
    ttyskeepawake        1
    hibernatemode        0
    gpuswitch            2
    hibernatefile        /var/vm/sleepimage
    womp                 1
    displaysleep         10
    networkoversleep     0
    sleep                60
    acwake               0
    halfdim              1
    sms                  0
    disksleep            0
    I'd appreciate help of any kind
    Thanks,
    zuoy

    Maybe try this, i am not sure that it will resolve the problem, but it is worth trying anyways.
    http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/eef49e64-157c-4082-8e80-52e48309691f
    Hi All,
    I've seen this problem multiple times, especially with Windows 7 64-bit versions and Enterprise edition.  The source of the problem appears to be the Bonjour service that is installed in the background and set to "Automatic" when installing certain 3rd
    party applications.  Apple applications like iTunes and Adobe applications like Acrobat Professional and Creative Suites have been known to cause this problem.  I've also seen virtualization software like VMWare and VirtualBox cause similar issues
    with network adapters.
    The solution in most of the cases I've come across has been to stop and disable the Bonjour service.  The Bonjour service also masquerades as a service with a name of the format "##Id_String1.6844F930_blahblahblah".  Here's how to disable this service
    in Windows 7:
    Right-Click on Computer > Select 'Manage'
    Expand the 'Services and Applications' section in the bottom of the Left-Nav dialog and Select 'Services'
    Sort the Services list by name and look for either "Bonjour" or the "##Id_String..." name mentioned above
    Right-Click on the service and select 'Properties'
    Click the 'Stop' button to stop the service
    Select 'Disabled' from the 'Startup type' drop down list
    Click 'Apply' and then 'OK'
    Reboot your machine and see if the "Multiple Networks" issue is resolved.  If so, you should have internet connectivity again.
    Hope this helps.
    cheers,
    Aaron

  • Network connection after waking from sleep

    Hi... More or less any time I allow my MacBook Pro to go to sleep, when I wake it up I am nearly always disconnected from my Airport connection (I connect to a NetGear wireless router via my internal Airport card). I go up to the menu bar and click on the now grey airport icon and I do still see my network in the list of available networks. I click on it, after several seconds a message comes up that says "there was an error joining the Airport network "network name""... But I then simply click on OK (rather than Try Again, I've learned that by trial and error) and the network reconnects just fine... Then when I let the machine sleep again at some later time, I do that all again... Any suggestions of what might be going on??? I do have "Use Interference Robustness" turned on (not that I know why exactly) but I've also had it off before and that seems not to matter... Any suggestions??? thanks... bob..
    FW800 G4 dual 1.25 Ghz and 17 inch MacBook Pro Mac OS X (10.4.8)

    I have "join preferred networks" selected, and mine os the only one on the list, and it still does not connect after waking from sleep. It is WEP security, not WPA2. I checked out the following article, but it was of no help:
    http://docs.info.apple.com/article.html?artnum=304482

  • ISE machine authentication - only plug in to the network after booting

    Hi experts.
    I have recently deployed ISE with machine authentication. 
    However, when the machine is already plugged in to the switch before booting, the machine does not authenticate automatically. It isn't until I log on, using a local computer account, that 802.1X authentication occurs. Using wireshark, I have verified again that this authentication is MACHINE authentication, not user-authentication.
    Is there a way to solve this problem, other than having my users unplug their computer and only plug in to the network after booting?
    Eric

    Hi Vattulu,
      The method of machine access restriction will be used, because there is no a plan to use anyconnect NAM on the client environment, since the prerequisite for EAP-chaining is to use anyconnect.
    Regards,
    Eric

Maybe you are looking for