Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

No “Wake for network access” over wired LAN

Hello,



I could not get “Wake for network access” to work over wired LAN connection. If I have WiFi enabled as well, or WiFi is the only network interface enabled the “Wake for network access” works fine. However, my Mac Pro is not responding to when I am trying to reach it remotely if only the wired Lan connection is used.

Mac Pro 6-Core 3.33GHz 24GB RAM, latest updates, Snow Leopard, “Wake for network access” enabled in Energy Saver settings.

It seams to me, that it was working some time ago.

Can anyone suggest me places to look to, settings to check, commands to run ..... to get it working?

Mac Pro, Mac OS X (10.6.8), 6Core 3.33GHz 24GB 4x3TB HDD+SSD

Posted on Jun 30, 2011 11:53 AM

Reply
17 replies

Jun 30, 2011 1:23 PM in response to Grant Bennet-Alder

Thank you Grant Bennet-Alder for responding. I will try to describe it as step-by-step as possible.

- I have back to my mac enabled with screen and file sharing on my Mac Pro

- By default I use wired NIC to connect my MP to network with manual configuration. (I have tried enable DHCP for that interface, however, the result was the same)


If I need to reach files on my Mac Pro (while I am away from it) from my Macbook Pro, I open finder on my MBP where I see my Mac Pro. I click on it if I need to access files or use "Share screen..." button if I want to access MP screen. I have the same result if I try to enter vnc://xxx or afp://xxx

my MBP tries to reach MP and brings the message after some time: Connection failed to "xxxxx" Please make sure the screen sharing is enabled....."


I have no problems remotely accessing my MP if:

- it is not sleeping (i.e. I ask someone at home to touch its keyboard to wake it up)

- I have AirPort turned on on my Mac Pro

I could not access my Mac Pro if:

- it is sleeping and AirPort is off (the only wired NIC is used to connect to LAN)


It does not matter am I trying to get screen/file sharing on local network or via internet - the result is the same - if the only wired connection to network is used and MP sleeps - no access.

Jul 2, 2011 3:19 AM in response to Grant Bennet-Alder

Thank you, Grant Bennet Alder,

One of my Macs is Macbook Pro and it sometimes appears on a public or similar network, therefore I prefer, on MBP, to have firewall on. However, you are probably right and I do not need a firewall on my MacPro as Airport Extreme does the firewall job? Or Airport's protection is weak?


As regards my wake on network access issue, it seams that this is bug in 10.6.8 and I am not the only one having this problem after update. Let's hope Apple will fix it.

Jul 2, 2011 2:36 PM in response to Munas

When the Router gives you an address in the range of "private" IP Addresses using DHCP, you cannot be seen or addressed directly from the Internet. The Router acts as your agent in dealing with the Internet, and accepts packets from only those outsiders you have initiated conversations with. All other packets are discarded.


The addresses in this table cannot be accessed from the Internet. A Router must act on your behalf, and its Firewall protects you from bad guys trying to get on your Mac.

IANA-reserved private IPv4 network ranges

10.0.0.0 to

10.255.255.255


172.16.0.0 to

172.31.255.255


192.168.0.0 to

192.168.255.255


from: http://en.wikipedia.org/wiki/IP_address

No “Wake for network access” over wired LAN

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.