D
David Shorthouse
Hey folks,
I have a great Linksys NIC that allows for both wake-on-LAN via magic
packets (useless for my needs) or via ping / any other access (what I need).
Consequently, when I forward specific ports in my router (like VPN or Remote
Desktop), I can remotely fire up my suspended machine from the WAN side and
access it no sweat.
I just set-up a second machine behind the same router but it has a
Realtek onboard NIC. All I seem to be able to do is WOL via magic packets.
In other words, I cannot wake the machine up from the WAN side because I
don't know of any way to send the packet through the router. Simply
forwarding the same port any WOL utility uses doesn't solve the problem- the
MAC address of the machine I want to fire up is hidden from the WAN side.
Any ideas on how I can get this to work as efficiently as possible?
Dave
I have a great Linksys NIC that allows for both wake-on-LAN via magic
packets (useless for my needs) or via ping / any other access (what I need).
Consequently, when I forward specific ports in my router (like VPN or Remote
Desktop), I can remotely fire up my suspended machine from the WAN side and
access it no sweat.
I just set-up a second machine behind the same router but it has a
Realtek onboard NIC. All I seem to be able to do is WOL via magic packets.
In other words, I cannot wake the machine up from the WAN side because I
don't know of any way to send the packet through the router. Simply
forwarding the same port any WOL utility uses doesn't solve the problem- the
MAC address of the machine I want to fire up is hidden from the WAN side.
Any ideas on how I can get this to work as efficiently as possible?
Dave