Welcome to the MacNN Forums.

Dave Hagan · Mar 8, 2004, 11:40 PM

When I wake my PowerBook from sleep at work, I connect instantly to the network (whether airport or ethernet) and can immediately use my laptop. However, anywhere else when I wake my PowerBook there's like a minute to 90 second delay before I can start doing things -- like launching new applications or using the Internet or network. I'm using DHCP in both places. It's a Ti867 with 768 MB RAM, running 10.3.2. I think this has happened pretty much since I got it a year ago. It's just a small annoyance. Any ideas?

Detrius · Mar 10, 2004, 09:56 PM

vague idea here, but maybe there is a difference between the DHCP servers. Also, my laptop is more inclined to join some networks than others.

More details?

Dave Hagan · Mar 10, 2004, 11:42 PM

On second thought, it just hangs for a good minute or so whenever I wake it up from sleep anywhere whether a network is available or not, except at work where it wakes automatically and is usable in about 2-3 seconds with Airport or Ethernet.

Could a configuration file nested and buried deep somewhere have a bias to the network at work? I should also note that open apps are immediately useable upon wake from sleep outside of work, so long as they don't require the network, which hasn't yet to wake up (unless, of course at work). If I open the PowerBook at home from sleep for example, and I try to open a new app, it just bounces in the dock for that minute too.

pjlennon · Dec 29, 2006, 03:17 PM

I'm having a similar issue with our Macs. My 10.4.x Macs are unable to get DHCP addresses quickly on our network. They take about 40 seconds from the time the NIC is activated (take TCP/IP for Built-in Ethernet from OFF to DHCP and hit "Apply") to the time they finally get a valid IP address and can resume TCPIC network activity. The XP boxes seem unaffected by this.

I was told to have spanning tree turned off on the switches, but my network folks say it's not on. and switching the Mac client Ethernet settings from "Automatic" to "Manual" with (100 or 1000baseT) and full-duplex does nothing to accelerate the 40 second (or so) delay it takes the Macs to get an IP. The problem in with getting an IP address happens either from the time they're booted or when they're woken from sleep (so, whenever the NIC is called upon after some time of inactivity). Manually assigning them their DHCP addresses doesn't seem to help.

It might be significant that we recently moved our switches from an Enterasys 6000 to a Cisco 4506, but I haven't been able to establish this. The Enterasys has a 10\100 card while the Cisco has a 10/100/1000.

Turning IPv6 doesn't seem to have helped either (I understand IPv6 is searched for first)

Any ideas?

skyman · Dec 29, 2006, 10:29 PM

The lease time for the IP address from your DHCP server may be the cause.

Also, is it a server or a router that is issuing your IP addresses?

My MBP connects to our network instantly, but then again the IP address has never expired.

pjlennon · Jan 3, 2007, 12:45 PM

Originally Posted by skyman

The lease time for the IP address from your DHCP server may be the cause.

Also, is it a server or a router that is issuing your IP addresses?

My MBP connects to our network instantly, but then again the IP address has never expired.

Thanks. Whatever our lease times happen to be, they're pretty long. I've had one for 1.5 yrs. I'll inquire as to whether the IP Addresses are being obtained from servers or routers. What difference would it make?