Limited network connectivity after reboot

I have a Windows Server 2008 sp2, and every time it does a reboot, I lose the network connection.  the system tray will either have a red x or it will say limited network connectivity.  If I run a repair it says the network cable is unplugged. 
The only way I have found to resolve this is is to go into manage network connections, and disable the network adapter, and then enabling the network adapter.  This server worked fine for about three years, before the problem started occurring. 
Any ideas would be appreciated.

I found a newer network driver, and will install probably on Monday.  This is the server that runs all our backups, so I have to wait to install the driver until the next backup job finishes.  The only warning I am getting is:
Broadcom NetXtreme Gigabit Ethernet #2: The network link is down.  Check to make sure the network cable is properly connected.
If updating the driver does not help then it might something wrong with the NIC. You can try replacing it and see if that helps.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Similar Messages

  • Loss of network connectivity after reboot

    I'm new to Macs, so please excuse any ignorance. I'm trying to finally get my G5 on my wireless network. I have an airport card installed and I can successfully connect to my wireless after I enter the network name and WEP key.
    However, if I reboot the computer, it seems to forget all this information. If I want to get back online, I have to enter the network and WEP info again, as if it was a new network every time. Needless to say, this is very annoying.
    If anyone has any ideas what I may be doing wrong, I would be very appreciative. I had always heard Macs were insanely user friendly, so I'm shocked at how much trouble I'm having. I have to think that I'm just doing something wrong. Please help!

    In network preferences, add your network's name to your list of 'preferred networks', and set it to automatically connect to servers in your preferred list.

  • My Mac Pro loses network connection after wake from sleep since Yosemite upgrade.

    Mac Pro loses network connection after wake from sleep since Yosemite upgrade. Any one have this issue as well. And is there a work around?

    Wi-Fi?
    Wi-FI connection drops
    Wi-Fi Problems in OS X Yosemite
    Wi-Fi Problems in OS X Yosemite (2)
    Wireless Diagnostics
    Also try turning off Bluetooth.
    Troubleshooting Wi-Fi issues in OS X
    Wireless Connection Problems - Fix
    Wireless Connection Problems - Fix (2)
    Wireless Connection Problems - Fix (3)
    Wireless Connection Problems - Fix (4)

  • Apple TV2 can't find my network connection after recent update?

    Why can't my Apple TV2 can't find my network connection after recent update?

    I had to update the software on my Airport Extreme then reset my apple tv and that resolved the issue for me.

  • I loose my home network connectivity after my iMac is awaken. This began after I upgraded to Lion. Is there a fix to this problem?

    I loose my home network connectivity after my iMac is awaken. This began after I upgraded to Lion. Is there a fix to this problem?

    see if this article helps: http://osxdaily.com/2011/11/06/lion-wi-fi-problems-solution-mac/?utm_source=feed burner&utm_medium=feed&utm_campaign=Feed%3A+osxdaily+%28OS+X+Daily%29&utm_conten t=FaceBook

  • FP1600 loses network connection after a few hours

    My FP1600 loses its network connection after a few hours. It is part number 185690C-01, with firmware 4.11. I am running FieldPoint Explorer version 3.0.1 and LabView 6.1 from Windows XP Professional. I set it up, and everything runs fine for 4 hours or more. I do not have the network watchdog enabled, and the FP1600 is in constant communication with the host computer in any case. Sometime in the middle of the night the communication is lost. The FP1600 link light
    is on, and it is still receiving packets, but it will not respond to a ping or any other communications. Only a power cycle brings it back. The FP1600 is sitting right next to the host computer, both attached to the same network switch. There is no interruptio
    n of network services to the two.

    Hi Heinz,
    We are also trying to troubleshoot this same problem (Intermitten network connection loss with FP1600 Ethernet Module - Error code "33163", Error Message - "FP1600 Connection to module has been lost."). We have checked other possible causes for this sort of behaviour. Including independent assessment of netowork availability at the time of error reporting, connecting dedicated power supply to the FP1600 module, temperature of cabinet housing the module (which is between 10 and 50 deg C), disconnecting sensors connected to various I/O modules connected to this module, increasing duration of parameter "time out" (the time module will wait before reporting an error if it can not access network). However, none of the above resolved the intermittent and random network loss errors.
    The MAX version is 3.0.2, and the firmware on the module is 4.17, Labview version is 7.0 and the Operating System is windows NT.
    I was wondering is there any information about this problem from any user or NI recently. The only solution looking in to this discussion forum seems to be replacing the module.
    MehulMessage Edited by MPatel on 02-28-2005 08:16 PM

  • 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

  • Lost network connection after SW update

    First time poster, relative newbie to Mac. I blindly updated to 10.4.11 and then found that my Mini had no network connection, yet my Ministack external FW HD and WinXP (thru BootCamp) will still connect wirelessly to my Westel router which has not been touched throughout this ordeal. My network is still shown and even offered to me for use during boot, but fails to connect. I have thrown every switch I can find in sys prefs to no avail. I have been asked for a WEP password, but security is switched off (in prefs and router), and I never used a PW before. I've spent hours Googling this topic, but can't find an exact match to my situation. I don't have the Mac knowledge to undo the update, or even know if it can be done. I can't understand how the bootable external HD can share the connection, but the "host" computer can't use it. Gotta be a setting wrong somewhere, eh? Please help.

    A warm welcome to the forums!
    Tons of similar posts, but not too many with the same cause fix.
    If you haven't done regular maintenence like Disk validate/repair, Permissions fixes, etc, ete.
    Then you Might give a try with Applejack...
    http://www.versiontracker.com/dyn/moreinfo/macosx/19596
    After installing, reboot holding down CMD+s, then when the prompt shows, type in...
    applejack AUTO
    Then let it do all 5 of it's things.
    At least it'll eliminate some questions if it doesn't fix it.
    The 5 things it does are...
    Correct any Disk problems.
    Repair Permissions.
    Clear out Cache Files.
    Repair/check several plist files.
    Dump the VM files for a fresh start.

  • Can not setup network connection after netctl 1.10 update

    I'm using netctl's ifplugd service to automatically manage my network connections (LAN), however after latest update to netctl (1.10) I can not connect to other machines or internet anymore and I must downgrade to netctl 1.9.
    Related netctl service:
    [email protected]
    My network connection profile: /etc/netctl/mynetwork
    Description='A basic static ethernet connection'
    Interface=enp2s0
    Connection=ethernet
    IP=static
    Address=('192.168.1.1/24')
    #Routes=('192.168.0.0/24 via 192.168.1.2')
    Gateway='192.168.1.254'
    DNS=('192.168.1.254')
    ## For IPv6 autoconfiguration
    #IP6=stateless
    ## For IPv6 static address configuration
    #IP6=static
    #Address6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
    #Routes6=('abcd::1234')
    #Gateway6='1234:0:123::abcd'
    Related bits from journald:
    Jan 23 01:13:36 arch ifplugd[251]: ifplugd 0.28 initializing.
    Jan 23 01:13:36 arch ifplugd[251]: Using interface enp2s0/00:23:54:2C:CE:94 with driver <ATL1E> (version: 1.0.0.7-NAPI)
    Jan 23 01:13:36 arch ifplugd[251]: Using detection mode: SIOCETHTOOL
    Jan 23 01:13:36 arch ifplugd[251]: Initialization complete, link beat not detected.
    Jan 23 01:13:36 arch kernel: IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
    Jan 23 01:13:36 arch acpid[246]: starting up with netlink and the input layer
    Jan 23 01:13:36 arch acpid[246]: 1 rule loaded
    Jan 23 01:13:36 arch acpid[246]: waiting for events: event logging is off
    Jan 23 01:13:37 arch kernel: floppy0: no floppy controllers found
    Jan 23 01:13:37 arch kernel: ATL1E 0000:02:00.0 enp2s0: NIC Link is Up <100 Mbps Full Duplex>
    Jan 23 01:13:37 arch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
    Jan 23 01:13:37 arch acpid[246]: client connected from 256[0:0]
    Jan 23 01:13:37 arch acpid[246]: 1 client rule loaded
    Jan 23 01:13:38 arch ifplugd[251]: Link beat detected.
    Jan 23 01:13:39 arch ifplugd[251]: Executing '/etc/ifplugd/netctl.action enp2s0 up'.
    Jan 23 01:13:39 arch ifplugd[251]: client: <3>Could not start any suitable profile
    Jan 23 01:13:39 arch ifplugd[251]: Program execution failed, return value is 1.

    This problem hit me too. I have a static IP address set up on a server, I upgraded netctl to 1.10 and it took me a couple of hours to work out why, after the upgrade, my network would not work. The messages were not helpful as I performed netctl starts, stops and status, or ip link commands. In the end I got the server back up by using ifconfig, ip addr add, ip route add etc. Then I found this forum entry (Thank you siavashserver and jouke!).
    While the solution can be found in the netctl manual, it is a little obscure. I think this deserves the status of a bug. I don't think a simple upgrade should allow a whole class of users (everybody with a static ip address) to lose network connectivity without warning.
    Even the (upgraded?) /etc/netctl/examples/ethernet-static file fails to include ExcludeAuto=no, so the documentation (at least in this regard) is faulty.
    When I performed the upgrade I was warned
    New optional dependencies for netctl
        openvswitch: for Open vSwitch connections
        ppp: for PPP connections
    Is it possible to add a message there saying Warning! If you have a static ip address, this upgrade will destroy your network connectivity next time you reboot unless you add ExcludeAuto=no to your network profile?
    jouke wrote:Add ExcludeAuto=no to your profile. As there is no way to check a statically configured IP address for correctness, they are excluded from automatic profile selection by default starting netctl 1.10. I am sorry for the inconvenience. From netctl 1.10 onwards, the behavior of netctl-ifplugd@ is documented in the man pages. For more information on ExcludeAuto= and Priority=, consult netctl.profile(5).

  • No network connection after windows 10 install

    No internet connection after windows 10 install- laptop wont recognize any wi-fi networks- repair option on MY ATT has no option for windows 10 system

    Hi,
    Sorry about that. One other thing to try is to try this in the command prompt:
    Start - All Programs - Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt. [For Windows 8 or 10: <Windows Logo> + x - Command Prompt(Admin)]
    Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
    Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log
    Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log
    Reboot the machine
    If still having issues, you may need to uninstall your network adapter and install it again.
    -ATTU-verseCare

  • No network connection after install on a VirtualBox VM

    Hey guys, I am a relative newb to Arch, and linux in general for that matter. I'm working on a project with pogo plugs and Arch seems to be the best linux solution for those at the moment so I figured it would do me some good to get it running on my desktop so I can become more familiar with it.
    I'm attempting to install it on a VirtualBox vm following the beginners install guide. I get all the way through the install and reboot into my shiny new OS, but have run into the issue where I can't do any further package updates as I have lost my network connection. The beginners guide specifies a way to configure this so it it is persistent once the install is done.
    I can issue the systemctl enable "dhcpcd@<interface>.service" command with my interface as eth0 (verified by ip link) "[email protected]", but once I reboot into the fresh install ip link tells me my interface is actually enp0s3. If I rerun the dhcp enable command again with enp0s3 as the interface it executes without error, but I still do not have network.
    I tried using ifplugd during the install process during one of my go-arounds, but ifplugd was not able to install as none of the files appear to be available, perhaps that server is down?
    Can anyone shed some light on what I might be doing wrong? I'm guessing it's something very simple that I am missing, hopefully someone here can catch it.

    I was stuck at this problem, as in topic header. I looked at this post, thought that finally I found the solution(was referring to one more post). Then I tried following steps as mentioned in #3. OMG, I tried it for more than hour, couldn't get it working. Then i get one hint, i.e, the interface name is not enps03 but its enp0s3 ... Okay, again i tried, but still it did not work... this time i was little more cautious, so after few attempts, looked at my command, i had been typing [email protected], I don't know why such confusing naming conventions are followed, there are two files under /lib/systemd/system/ that are like dhcpd.* .. but this one particular file is dhcpcd@.*... well.. that's it. I just had to laugh at myself.

  • Automatic re-mount of networked volumes after reboot

    Hello.
    Does anyone know if its at all possible to automatically re-connect network volumes after a reboot? Or if there's an app out there to do just that?
    I really don't want to have every network volume (I have LOTS) in the dock...

    Yes this works, but I have been unable to find out how to do this without opening the root of the volumes after the reboot. I tried "Hide Item" in the Login Items control panel, but to no avail.
    Anyone have any ideas?

  • [SOLVED] Losing network connection after suspend

    Lately I'm having this peculiar problem.  When resuming after suspend (specifically, pm-suspend), I have no network connection.  I first noticed this on March 31st.  The only thing that changed was that I upgraded these packages:
    openssl-1.0.1-2-x86_64.pkg.tar.xz
    xf86-video-ati-6.14.4-2-x86_64.pkg.tar.xz
    lib32-libdrm-2.4.33-1-x86_64.pkg.tar.xz
    libnotify-0.7.5-1-x86_64.pkg.tar.xz
    xz-5.0.3-2-x86_64.pkg.tar.xz
    vim-taglist-45-5-any.pkg.tar.xz
    But I'm pretty sure I would have suspended and resumed successfully at least once after that upgrade.
    Can anyone suggest what I should look at to try to diagnose this?
    Thanks
    Last edited by ibrunton (2012-04-06 11:26:03)

    Same issue here. Looks like dhcpcd crashes during or after running /usr/lib/dhcpcd/dhcpcd-run-hooks on resume from suspend. I'll try downgrading until this is fixed.
    $ uname -s -v -r -m
    Linux 3.2.13-1-ARCH #1 SMP PREEMPT Sat Mar 24 09:10:39 CET 2012 x86_64
    $ pacman -Qi dhcpcd
    Name : dhcpcd
    Version : 5.5.5-1
    URL : http://roy.marples.name/dhcpcd/
    Licenses : BSD
    Groups : base
    Provides : None
    Depends On : glibc sh
    Optional Deps : None
    Required By : networkmanager
    Conflicts With : None
    Replaces : None
    Installed Size : 256.00 KiB
    Packager : Ronald van Haren <[email protected]>
    Architecture : x86_64
    Build Date : Fri Mar 23 17:25:47 2012
    Install Date : Thu Mar 29 23:36:13 2012
    Install Reason : Explicitly installed
    Install Script : No
    Description : RFC2131 compliant DHCP client daemon
    # dhcpcd -d -B eth0
    dhcpcd[1865]: version 5.5.5 starting
    dhcpcd[1865]: eth0: using hwaddr bc:ae:c5:75:36:8e
    dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
    dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
    dhcpcd[1865]: eth0: sending IPv6 Router Solicitation
    dhcpcd[1865]: eth0: reading lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
    dhcpcd[1865]: eth0: rebinding lease of 192.168.1.100
    dhcpcd[1865]: eth0: sending REQUEST (xid 0x36169f23), next in 3.93 seconds
    dhcpcd[1865]: eth0: acknowledged 192.168.1.100 from 192.168.1.1
    dhcpcd[1865]: eth0: checking for 192.168.1.100
    dhcpcd[1865]: eth0: sending ARP probe (1 of 3), next in 2.00 seconds
    dhcpcd[1865]: eth0: sending ARP probe (2 of 3), next in 1.81 seconds
    dhcpcd[1865]: eth0: sending IPv6 Router Solicitation
    dhcpcd[1865]: eth0: sending ARP probe (3 of 3), next in 2.00 seconds
    dhcpcd[1865]: eth0: leased 192.168.1.100 for 3600 seconds
    dhcpcd[1865]: eth0: adding IP address 192.168.1.100/24
    dhcpcd[1865]: eth0: adding route to 192.168.1.0/24
    dhcpcd[1865]: eth0: adding default route via 192.168.1.1
    dhcpcd[1865]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
    dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
    dhcpcd[1865]: eth0: sending ARP announce (1 of 2), next in 2.00 seconds
    dhcpcd[1865]: eth0: sending IPv6 Router Solicitation
    dhcpcd[1865]: eth0: sending ARP announce (2 of 2)
    dhcpcd[1865]: eth0: sending IPv6 Router Solicitation
    dhcpcd[1865]: eth0: no IPv6 Routers available
    dhcpcd[1865]: eth0: carrier lost
    dhcpcd[1865]: eth0: deleting default route via 192.168.1.1
    dhcpcd[1865]: eth0: deleting route to 192.168.1.0/24
    dhcpcd[1865]: eth0: deleting IP address 192.168.1.100/24
    dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
    dhcpcd[1865]: eth0: carrier acquired
    dhcpcd[1865]: eth0: using hwaddr bc:ae:c5:75:36:8e
    dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
    *** glibc detected *** dhcpcd: double free or corruption (fasttop): 0x0000000000ac2860 ***
    ======= Backtrace: =========
    /lib/libc.so.6(+0x78a56)[0x7f9b6a794a56]
    dhcpcd[0x40cdd0]
    dhcpcd[0x40e597]
    dhcpcd[0x4093f0]
    dhcpcd[0x411ba7]
    dhcpcd[0x411563]
    dhcpcd[0x40768f]
    dhcpcd[0x40aa6b]
    dhcpcd[0x4028a8]
    /lib/libc.so.6(__libc_start_main+0xf5)[0x7f9b6a73d455]
    dhcpcd[0x402d1d]
    ======= Memory map: ========
    00400000-00419000 r-xp 00000000 fe:02 4590719 /sbin/dhcpcd
    00619000-0061a000 r--p 00019000 fe:02 4590719 /sbin/dhcpcd
    0061a000-0061b000 rw-p 0001a000 fe:02 4590719 /sbin/dhcpcd
    0061b000-0061c000 rw-p 00000000 00:00 0
    00ac1000-00ae3000 rw-p 00000000 00:00 0 [heap]
    7f9b6a2eb000-7f9b6a300000 r-xp 00000000 fe:02 1063993 /usr/lib/libgcc_s.so.1
    7f9b6a300000-7f9b6a4ff000 ---p 00015000 fe:02 1063993 /usr/lib/libgcc_s.so.1
    7f9b6a4ff000-7f9b6a500000 rw-p 00014000 fe:02 1063993 /usr/lib/libgcc_s.so.1
    7f9b6a500000-7f9b6a517000 r-xp 00000000 fe:02 3014810 /lib/libpthread-2.15.so
    7f9b6a517000-7f9b6a716000 ---p 00017000 fe:02 3014810 /lib/libpthread-2.15.so
    7f9b6a716000-7f9b6a717000 r--p 00016000 fe:02 3014810 /lib/libpthread-2.15.so
    7f9b6a717000-7f9b6a718000 rw-p 00017000 fe:02 3014810 /lib/libpthread-2.15.so
    7f9b6a718000-7f9b6a71c000 rw-p 00000000 00:00 0
    7f9b6a71c000-7f9b6a8b3000 r-xp 00000000 fe:02 3018245 /lib/libc-2.15.so
    7f9b6a8b3000-7f9b6aab3000 ---p 00197000 fe:02 3018245 /lib/libc-2.15.so
    7f9b6aab3000-7f9b6aab7000 r--p 00197000 fe:02 3018245 /lib/libc-2.15.so
    7f9b6aab7000-7f9b6aab9000 rw-p 0019b000 fe:02 3018245 /lib/libc-2.15.so
    7f9b6aab9000-7f9b6aabd000 rw-p 00000000 00:00 0
    7f9b6aabd000-7f9b6aac4000 r-xp 00000000 fe:02 3014856 /lib/librt-2.15.so
    7f9b6aac4000-7f9b6acc3000 ---p 00007000 fe:02 3014856 /lib/librt-2.15.so
    7f9b6acc3000-7f9b6acc4000 r--p 00006000 fe:02 3014856 /lib/librt-2.15.so
    7f9b6acc4000-7f9b6acc5000 rw-p 00007000 fe:02 3014856 /lib/librt-2.15.so
    7f9b6acc5000-7f9b6ace6000 r-xp 00000000 fe:02 3018769 /lib/ld-2.15.so
    7f9b6aea5000-7f9b6aea9000 rw-p 00000000 00:00 0
    7f9b6aee4000-7f9b6aee6000 rw-p 00000000 00:00 0
    7f9b6aee6000-7f9b6aee7000 r--p 00021000 fe:02 3018769 /lib/ld-2.15.so
    7f9b6aee7000-7f9b6aee8000 rw-p 00022000 fe:02 3018769 /lib/ld-2.15.so
    7f9b6aee8000-7f9b6aee9000 rw-p 00000000 00:00 0
    7ffff8b93000-7ffff8bb4000 rw-p 00000000 00:00 0 [stack]
    7ffff8bc9000-7ffff8bca000 r-xp 00000000 00:00 0 [vdso]
    ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]

  • 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

  • 2008 r2 hyper-v guest with static IP always looses network connectivity after every restart - no problem with DHCP

    Hello,
    We are running 2008 R2 domain with one physical DC and other running in VM on Hyper-V host (2008 R2 Standard). The host has 4 NICs and is configured to use one physical NIC for itself (management) and the hyper-v guest is configured to use another dedicated/physical
    NIC (through microsoft virtual switch) just for itself.
    I noticed that after setting the hyper-v guest with a static IP address all works fine only until guest restart. When the guest boots up the IP address is still configured correctly in IPv4 properties, but there is no network connectivity at all and in fact
    the guest shows running APIPA config in ipconfig /all output. That situation continues until I remove the virtual NIC from hyper-v guest, remove the virtual switch from dedicated NIC on host and then reconfigure it (using same settings as they were). very
    annoying.
    For time being I switched the virtual DC (problematic hyper-v guest) to a DHCP IP and configured DHCP server (running on physical DC machine, not on hyper-v host) to store a reservation for the hyper-v guest so it always gets the same "static"
    IP configuration.
    Is there some kind of a problem/bug with using static IP on (2008 R2) hyper-v guests? is there a hotfix for static IP config in hyper-v guest environment?
    both 2008 R2 OSes (host and guest) are up to date with all updates (synced with Microsoft, not WSUS).

    OK, I'm not at the office now, but took my time to test out the restart scenarios on problematic virtual guest remotely.
    No dice, same as it was, everything works fine after guest has IP configured in DHCP mode (IP reservation of 192.168.1.5 for specific MAC address) and it doesn't work after restart in static IP mode (same address, works before restart of guest).
    I also took "arp -a" outputs at each step from host server and that was always saying there is only a single host (192.168.1.5 = VDC = problematic virtual guest) assigned to that IP address and always with same MAC, so that pretty much rules out
    ARP/MAC troubles and no issues with switches/routers getting spoofed. Problem is most likely with the virtual guest (WS2008R2) or within the host running same OS.
    Here are outputs:
    A) VDC has IP configured in DHCP mode - always same, survives through restart (all works)
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . : CD.lan
    Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter
    Physical Address. . . . . . . . . : 00-15-5D-01-D3-00
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::b9af:6679:3142:8799%13(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Thursday, January 30, 2014 5:34:48 PM
    Lease Expires . . . . . . . . . . : Friday, February 07, 2014 5:35:26 PM
    Default Gateway . . . . . . . . . : 192.168.1.254
    DHCP Server . . . . . . . . . . . : 192.168.4.5
    DHCPv6 IAID . . . . . . . . . . . : 268440925
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-6F-5F-C2-00-15-5D-01-D3-00
    DNS Servers . . . . . . . . . . . : 192.168.1.5
    192.168.4.5
    NetBIOS over Tcpip. . . . . . . . : Enabled
    ARP -a output from host server at that time:
    Interface: 192.168.1.4 --- 0xc
    Internet Address Physical Address Type
    192.168.1.5 00-15-5d-01-d3-00 dynamic
    B) VDC has IP configured in static mode - BEFORE RESTART (all works)
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter
    Physical Address. . . . . . . . . : 00-15-5D-01-D3-00
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::b9af:6679:3142:8799%13(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.254
    DHCPv6 IAID . . . . . . . . . . . : 268440925
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-6F-5F-C2-00-15-5D-01-D3-00
    DNS Servers . . . . . . . . . . . : 192.168.1.5
    192.168.4.5
    NetBIOS over Tcpip. . . . . . . . : Enabled
    ARP -a output from host server at that time:
    Interface: 192.168.1.4 --- 0xc
    Internet Address Physical Address Type
    192.168.1.5 00-15-5d-01-d3-00 dynamic
    C) VDC has the same IP configured in static mode - AFTER RESTART (no more network connectivity at all, LAN in Public zone)
    Windows IP Configuration
    Host Name . . . . . . . . . . . . : VDC
    Primary Dns Suffix . . . . . . . : CD.lan
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : CD.lan
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter
    Physical Address. . . . . . . . . : 00-15-5D-01-D3-00
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::b9af:6679:3142:8799%13(Preferred)
    Autoconfiguration IPv4 Address. . : 169.254.135.153(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.0.0
    Default Gateway . . . . . . . . . : 192.168.1.254
    DHCPv6 IAID . . . . . . . . . . . : 268440925
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-6F-5F-C2-00-15-5D-01-D3-00
    DNS Servers . . . . . . . . . . . : 192.168.1.5
    192.168.4.5
    NetBIOS over Tcpip. . . . . . . . : Enabled
    ARP -a output from host server at that time:
    Interface: 192.168.1.4 --- 0xc
    Internet Address Physical Address Type
    192.168.1.5 00-15-5d-01-d3-00 dynamic
    Throughout the testing, the hyper-v host IP configuration and IPconfig output was always staying same.
    The Network Connection #2 is the only one the host uses (not shared with hyper-v guests).
    The Network Connection #4 is assigned to Microsoft Virtual Switch hence why it doesn't show up in results, like below:
    Windows IP Configuration
    Host Name . . . . . . . . . . . . : HYPER-V
    Primary Dns Suffix . . . . . . . : CD.lan
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : CD.lan
    Ethernet adapter Local Area Connection 3:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331i Adapter #3
    Physical Address. . . . . . . . . : 9C-8E-99-52-15-91
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Ethernet adapter Local Area Connection 2:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331i Adapter #2
    Physical Address. . . . . . . . . : 9C-8E-99-52-15-90
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::dc78:8a3b:38a5:7af3%12(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.254
    DHCPv6 IAID . . . . . . . . . . . : 312250009
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-67-52-8F-9C-8E-99-52-15-93
    DNS Servers . . . . . . . . . . . : 192.168.4.5
    192.168.1.5
    NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Local Area Connection:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331i Adapter
    Physical Address. . . . . . . . . : 9C-8E-99-52-15-93
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    On Monday I will install more test guests in Hyper-V host (WS2008R2), in variety of flavors like 7x64, 8.1x64, ws2012r2, and see if they show similar problems with static IP configuration when utilizing a dedicated NIC from host server.
    Don't get me wrong, I can live with virtual DC running on DHCP IP reservation (which is based on MAC), because the virtual DC pretty much requires a physical PDC (hosting also DHCP in my network) to be present for safety reasons ... however I prefer a static
    IP configuration on all servers, hence my question and surprise why it doesn't work.

Maybe you are looking for