TeamViewer Wake on LAN Help

[kwilliamnrys]

Hi all, 

 

I have been having trouble setting up Wake on Lan via public address on TeamViewer, especially in terms of port forwarding. I know that Wake on Lan for my computer is working since I tried another piece of software on my phone to wake my computer while on the same network and it was fine. I am pretty sure that it is the port forwarding is at fault since using http://www.portchecktool.com/ shows that Port 9 is not open. I attached a screenshot of my router's gateway (Fios Gateway G1100). I am not sure how to fill this out, but what I did is the static IP of my PC, UDP Port 9 to 9, and forward to the same port as incoming port  Did I do it right? There is not a lot of information about my router. I also made sure that I set a dynamic DNS just in case my public IP is dynamic.

 

Thanks

[Redportal]

Although it's probably not a best practice,  providing this is a home environment (I will assume it is) I would simply disable the firewall for a short period of time to make sure it works, if it does then great continue with port forwarding, if not you may need to dig a little deeper first.

 

Under specify IP, you need to enter the IP address of the computer you wish to use Wake on Lan with, however I'm not sure if this will work.

If you click 'Specify IP' does it give you any other options such as MAC address?

 

Also keep in mind some port checking tools will show the port as closed simply because there is nothing running over that port, it may in fact be open.

[Bittenfleax]

Use WireShark to ensure that the WoL packet is getting received externally.

 

The IP box is your computers IP address.

 

[Blake]

Try port 7 not 9.

[Bittenfleax]

10 hours ago, Blake said:

Try port 7 not 9.

WoL is default on Port 9 though? Is it different for Teamviewer?

[Blake]

7 hours ago, Bittenfleax said:

WoL is default on Port 9 though? Is it different for Teamviewer?

" Since the magic packet is only scanned for the string above, and not actually parsed by a full protocol stack, it may be sent as any network- and transport-layer protocol, although it is typically sent as a UDP datagram to port 0,^[6] 7 or 9, or directly over Ethernet as EtherType 0x0842 " Wikipedia.

 

I always knew it in port 9, but looks like port 0 might work also.

[kwilliamnrys]

7 hours ago, Redportal said:

Although it's probably not a best practice,  providing this is a home environment (I will assume it is) I would simply disable the firewall for a short period of time to make sure it works, if it does then great continue with port forwarding, if not you may need to dig a little deeper first.

 

Under specify IP, you need to enter the IP address of the computer you wish to use Wake on Lan with, however I'm not sure if this will work.

If you click 'Specify IP' does it give you any other options such as MAC address?

 

Also keep in mind some port checking tools will show the port as closed simply because there is nothing running over that port, it may in fact be open.

 

Sorry, I lost you. What firewall? Windows Firewall? How does that affect WoL?

 

I know what to enter under Specify IP, but for the other portions. I am not exactly sure. And no, it does not allow MAC addresses.

 

Lastly, even if the port may have been actually open, I tried setting it up with Teamviewer and turning my PC on with my iPhone and no success

[kwilliamnrys]

On 11/14/2016 at 9:09 AM, Bittenfleax said:

Use WireShark to ensure that the WoL packet is getting received externally.

 

The IP box is your computers IP address.

 

 

Yeah I know that, but do you know what I should put for the other options?

[kwilliamnrys]

1 hour ago, Blake said:

" Since the magic packet is only scanned for the string above, and not actually parsed by a full protocol stack, it may be sent as any network- and transport-layer protocol, although it is typically sent as a UDP datagram to port 0,^[6] 7 or 9, or directly over Ethernet as EtherType 0x0842 " Wikipedia.

 

I always knew it in port 9, but looks like port 0 might work also.

 

So I could try any of those ports?

[Blake]

2 minutes ago, kwilliamnrys said:

So I could try any of those ports?

yes. also might be an idea to setup port mirroring on the switch you connecting your system with, connect wireshark on another system to the mirrored port and compare the magic packets for external v internal.

[kwilliamnrys]

7 minutes ago, Blake said:

yes. also might be an idea to setup port mirroring on the switch you connecting your system with, connect wireshark on another system to the mirrored port and compare the magic packets for external v internal.

 I have no idea of what that is. Any tutorials?

[Bittenfleax]

13 hours ago, Blake said:

" Since the magic packet is only scanned for the string above, and not actually parsed by a full protocol stack, it may be sent as any network- and transport-layer protocol, although it is typically sent as a UDP datagram to port 0,^[6] 7 or 9, or directly over Ethernet as EtherType 0x0842 " Wikipedia.

 

I always knew it in port 9, but looks like port 0 might work also.

I thought it was Port 9 because everyone knew it as that port and manufactures default to that?! I learn something new every day