Currently Being ModeratedMar 22, 2013 2:28 PM (in response to vallejogreg)
It's not logic. It's business overstep. Read carefully the following:
The best (And Apple's own) answer, with Snow Leopard onwards - if you want to network - is: "Never Sleep".
The process, sleep - wake - network leaves too many security vulnerablilities
A lot of guessing here with no viable proof. Good luck with whatever 'problems' you think you are dealing with. I know of no one else with your issues.
Currently Being ModeratedMar 22, 2013 2:29 PM (in response to gphonei)
Hey look, Apple should have said that with OSX 10.6.8 on "you need 802.11n router with firmware update" if you want to network - Or they could put a dialog box suggesting such when you set up your network.
There was a day when apple machines lasted a long time. And DOS systems running windows had the bugs
Currently Being ModeratedMar 22, 2013 2:39 PM (in response to vallejogreg)
On wake from sleep, machine unable to connect to network (thru wifi). It's all ovet the internet, iterations of the same complaint. The problem lies in the fact that Apple made Bonjour open source; hoping that 3rd party vendors would adopt it. But they are not.
Apple is killing PC sales and routers are commodity items now, prices have little profit. There are few router vendors left that I trust. Ubnt.com, Netgear and Apple are it. No one else seems to be able to create stable dependable equipment/software anymore. People are complaining about this, because they are unable to reason about the technical issues, debug the problem, and then solve THAT PROBLEM. Instead, they just say "it used to work, and now it doesn't", so it must be Apple's fault. Certainly, there have been some OS-X bugs. Apple has been working on fixing those bugs.
Which would you rather do? Spend 10's of hours of your own time, fighting with a compatability issue, or spend $100 on an Airport Express, hook it up on the LAN port of you're existing router, and move on? I've been on here, forever, trying to get people to debug the problems they are having in logic stepwise processes. Noone has time to do that, yet they have time to "fight" with the problem and incessantly complain about it here, and on line, none of which will cause Apple to actualy understand the totality of the impact of the problem.
This causes problems with wifi and ethernet networked devices when the machine sleeps. Unfortunately the nomenclature is even confusing - with some techs calling peripherals "clients", and others, "servers" ... this is actually the case because when a computer sleeps, with Bonjour, the router becomes the server.
Hey look, the guy was dying, they overstepped. It's not gonna work. Too many vulnerabilities. Not enough goodwill. You know they're in trouble when they use terms like "magic packets"
You are making up reasoning here. They used technology that existed, to provide a new feature. It may not work if you don't have the correct equipment, because it needs to work on both ends of the network connection.
This doesn't seem to happen with a "wired" connection, so I really don't believe that it's a wake from sleep issue. It's more of a WiFi compatibility issue. My experience has shown that the tree brands of routers I listed above work flawlessly for all of my Macs. I did have small problems with the wake on WiFi before the 2nd update for MountainLion. But that is no longer a problem.
Currently Being ModeratedMar 22, 2013 3:02 PM (in response to vallejogreg)
Dude, seriously, what the **** are you rambling about? What you're saying is so wrong it's embarassing. Just stop now before you make yourself look any worse. Your problem has nothing to do with Bonjour Sleep Proxy server. The fact that Bonjour is open source has nothing to do with your problem. There are no vulnerabilities in Bonjour Sleep Proxy server. Apple didn't invent the term "magic packets". AMD invented the term and the technology in 1995.
So just forget about Bonjour Sleep Proxy. It's not your problem. Just because your Mac wakes up every 120 minutes to check for a Sleep Proxy server and failes to join your Wi-Fi network doesn't mean that it's causing the failure to join your Wi-Fi network. It's just experiencing the same failure that's already occuring for other reasons, it's not causing the failure.
Currently Being ModeratedMar 22, 2013 3:09 PM (in response to gphonei)
I agree with you completely actually. I should have bought a new Airport Router. In fact I should just buy new technology every 2-3 years. But I didn't, my router is from 2005 Airport 802.11g 6.3 firmware update. After all, whats $100 here or $100 there?
g - there are early adopters, and cautious deliberate adopters. But hey, I fixed my problem with wifi dropping. I am just posting here because there's a lot of folks out there posting the same problem and I found a working (free) solution
Currently Being ModeratedMar 22, 2013 3:20 PM (in response to Snoop Dogg)
"So just forget about Bonjour Sleep Proxy. It's not your problem. Just because your Mac wakes up every 120 minutes to check for a Sleep Proxy server and failes to join your Wi-Fi network doesn't mean that it's causing the failure to join your Wi-Fi network. It's just experiencing the same failure that's already occuring for other reasons, it's not causing the failure."
It wakes up,it looks for 802.11n router. Only finds 802.11g not running Bonjour. So it delists that Network location. That IS my guess. You're right, there's nothing wrong with Bonjour, the concept however Is problematic - it requires the latest in technology and frequent upgrades. Also has security vulnerabilities. probably wouldn't incorporate it into any critical industry function. Or, as apple suggests, "turn it off".
"The fact that Bonjour is open source has nothing to do with your problem."
It IS a problem if you didn't know to upgrade your hardware and, even more problematic, if other vendors don't adopt the standard.
Currently Being ModeratedMar 22, 2013 3:33 PM (in response to vallejogreg)
And your guess is wrong. Your Mac doesn't "delist that Network location". It just goes back to sleep because your router doesn't support sleep proxy. You don't think Apple tested this with older routers that don't support sleep proxy? You think everyone in the world that has a Mac with an older router can't join Wi-Fi networks?
Currently Being ModeratedMar 22, 2013 3:38 PM (in response to petermac87)
Just unchecked "wake for network access" in energy saver preferences. Works like a charm, and free. Not all of us have 100 bucks to toss around. Plus this stuff is really interesting. Apple overreached.
Currently Being ModeratedMar 22, 2013 3:42 PM (in response to Snoop Dogg)
"You think everyone in the world that has a Mac with an older router can't join Wi-Fi networks?"
Can join, yes. Can't join after sleep for more than 120 minutes.
Look Snoop. I've had macs since before they were called macs. Programmed computers as a kid. Your arguments are starting to sound suspiciously like they support my point. You should quit while ahead.
Currently Being ModeratedMar 23, 2013 11:05 AM (in response to gphonei)
"This doesn't seem to happen with a "wired" connection, so I really don't believe that it's a wake from sleep issue. It's more of a WiFi compatibility issue."
Actually, this has recently started to occur with my Ethernet connection. I gave up on WiFi quite a while ago and just ran an Ethernet cable. A week or two ago, when I woke my computer up, Thunderbird would show the message, "You are now offline; would you like to go online...?"
Currently Being ModeratedMar 23, 2013 12:15 PM (in response to goatcabin)
It DOES happen with a wired connection. My Mac Pro is connected via an Ethernet cable and experienced the same "not connected to the Internet" message my two MacBooks experienced.
But I haven't had any problems for over 5 months now, ever since I bought a new (ASUS) router.
I needed more RF power than the old Cisco (Lynksys) could give me. This was the only reason for buying the new router. After installing it, my "drop-outs" totally disappeared.
Once can only conclude that there are a number of issues going on here, including a software/firmware issue exclusive with the Lion OS. the combination of which is creating this issue.
There are many out there who have never seen, or who have finally resolved, this problem. I NOW appear to be a member of that group.
Currently Being ModeratedMar 23, 2013 1:20 PM (in response to goatcabin)
Can happen according to literature even with ethernet if it's on a network going into a wired router . You must have a really new router with 802.11n capability and Bonjour Sleep Proxy installed
Currently Being ModeratedMar 23, 2013 1:30 PM (in response to Big Red Dog)
Some of the new routers are fully compliant with Apple's requirement - 802.11n and Bonjour Sleep Protocol. Some of the router manufacturers didn't incorporate the software and firmware updates and some of us just are running old junk
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points