[trosco]

Hello, 

 

At my current job sometimes i have to work in remote places; i have quite a large library of resources on my home PC that would be great to be accessible remotely. 

I've configured a remote acces through windows and also have an Anydesk account configured (just context).

 

I've managed to wake up my PC through LAN by using Anydesk; however it only works if the other device is connected to the same local network (i mean wake up from shut-down state). To be able to WOL through the internet, I've followed some steps described in a few other websites (I can post them if needed) - basically: 

- enabled magic packet options in both  BIOS and network card properties (and it works, as I was able to start it with Anydesk) 

- configured port forwarding to forward port UDP 7 to my network card ip range - 192.168.1.255

- configured a dynamic DNS through my router, by using the free asus service

- succesfully tested the magic package via a testing tool, with the PC turned on and set the app to "listen" (I'll post a link to the tool if it's needed) - I used my DDNS address for host (ip) address; Port 7; MAC address - the one on the back of my router. 

 

Info on hardware:

- PC - Asrock X99 Extreme 4 motherboard with onboard Intel I218-V 

- router - ASUS RT-N18U

- if it matters, got a secondary network card, ASUS PCE-N53 on PCI-E card#2. In the process I didn't pay attention to it, presumed it has no interference. 

- router connected via ethernet cable to the PC

 

I am not an expert, not even too much of a tech-savvy, I've done my best to describe what I've done but some confusions may have occurred. I'll provide any other info or clarifications that are needed. 

 

Thank you and hope we can make this work! 

 

[Advertisements]

Verify that your DDNS is working:

 

Open an Elevated Command Prompt:

 

Win 7: Start, All Programs, Accessories then right click on Command Prompt and Run as Administrator
Win 8: http://www.eightforu...indows-8-a.html
win 10: http://www.howtogeek...-in-windows-10/

Type:

 

nslookup hostnameassignedbyDDNS

 

Does this return the IP address assigned to your router by your ISP?

 

tracert  -d  hostnameassignedbyDDNS

 

Does it complete or time out?  Is the last IP address that of your router?  Is there any difference between when the PC is on and when it's off?

 

Can you ping the port you are using?  I assume it's 7.

 

https://devconnected...ic-port-number/

[RKinner]

Verify that your DDNS is working:

 

Open an Elevated Command Prompt:

 

Win 7: Start, All Programs, Accessories then right click on Command Prompt and Run as Administrator
Win 8: http://www.eightforu...indows-8-a.html
win 10: http://www.howtogeek...-in-windows-10/

Type:

 

nslookup hostnameassignedbyDDNS

 

Does this return the IP address assigned to your router by your ISP?

 

tracert  -d  hostnameassignedbyDDNS

 

Does it complete or time out?  Is the last IP address that of your router?  Is there any difference between when the PC is on and when it's off?

 

Can you ping the port you are using?  I assume it's 7.

 

https://devconnected...ic-port-number/

[trosco]

Hi, 

 

 

 

Thank you for your reply. 

 

 

 

Does this return the IP address assigned to your router by your ISP?

I would say yes - it's the same IP I can find written on my router's Network Map under WAN IP (when I access my router setting). Also it's the IP that Google displays if I search "my ip". 

 

 

 

Does it complete or time out?  Is the last IP address that of your router?  Is there any difference between when the PC is on and when it's off?

It completes and yes, the last and only IP is the one that we mentioned above, when I do it from my PC. It just pings once that IP, then says completed. I tried if from my laptop (connected to my mobile network, so no link to my router), and it pings a bunch of addresses, last one being my router - last one before continuiting to ping forever apparently with "request timed out". This tracert from the laptop is the same no matter if the PC is on or off. 

 

Can you ping the port you are using?  I assume it's 7.

I couldn't get the telnet to work, I get and "is not recognised" error; tried to install it using the "sudo" command but that one's also not recognised. I tried both with the "$" sign and without (this part probably sounds funny but I didn't know if it's part of the command or not). Will try to get it working again this evening/tomorrow as I am in a bit of a hurry now. 

[RKinner]

Sorry about the telnet problem.  Apparently Microsoft stopped making it a part of the default installation of Win 10 somewhere among the many updates but it is still available just not with sudo which is a Unix command.

 

I just tested this (Option 1) and it works:

https://www.technipa...0-enable-telnet
if you don't know how to open Control Panel.

Just search for

control panel

and hit Enter

Once you get telnet installed it will have to reboot.  Make sure you use an elevated command prompt when you type the command.

 

You can test that it is working by just typing

telnet

when you hit Enter it should say:

 

Welcome to Microsoft Telnet

Escape Character is "CTRL+J"

Microsoft Telnet>

 

You can just type your IP Address a space then the port number since you already have telnet running.

 

A.B.C.D 7

 

To Exit Telnet type

q

 

 

FYI the "$" is just the prompt and is not part of a command.

 

The final option on the page, Ping Specific Port using Powershell, does work without needing to reboot.  To open Powershell press on the Windows Key and X at the same time.  You will see a menu.  Choose Windows PowerShell(Admin)

[trosco]

Thank you, I managed to install the Telnet client. I am running windows 7 by the way. 

 

I tried to ping the UDP port 9, that was the one I forwared following instructions online. I tried both by using my DDNS and my local area connection IP, and it said "could not open a connection to the host, on port 9 : Connect failed". 

However, I only "succeded" when using the elevated command prompt, the telnet window only says "invalid command" . I just wrote my local area connection IP and 9 ("a.b.c.d 9")

 

Also, Test-NetConnection doesn't work on powershell - it says "it's not recognized as the name of a cmdlet, function, script file, or operable program". "ObjectNotFound

 

If I should forward port no. 7 and retry, let me know! 

[RKinner]

Was assuming Windows 10 so that makes a difference.

 

That's probably why the powershell didn't work.

 

I'm looking at this:

 

https://www.howtogee...do-i-enable-it/

 

and they talk about ports 7 & 9.  From what I read 7 is the default but some systems use 9.  You mentioned 7 in your original post so that's what I was going for.

 

Now that I reread your original post I see you are expecting a UDP packet and not TCP.  Telnet uses TCP so that's not going to work for your application.  Sorry.

 

This should work and you can do it on your WOL PC.

https://check-host.net/

 

Put in the IP address followed by the : and 7 or 9 (Should look like this with your ip address instead of mine:  97.104.75.126:7) and then hit UDP port.

 

I tried it from mine.  And since I don't have any ports opened it says "Open or Filtered."  Not sure what it would say if I had connectivity.

[trosco]

You were right, I did say 7 in my initial post - I probably mixed them up during several tries. 

 

Yes - that link on HowToGeeks you sent me, was the original post I also followed. 

 

Since a lot of this is quite foreign knowledge to me, maybe it could be good to go over the basics a bit, to see if i understood this properly and that i'm using the proper ip's in the appropriate places.

1. I don't really understand what ip displays on check-host.net, at the top - is that my router's ip? It's the same when i go on that website from my laptop (connected to the same network); and it's the address associated to my DDNS (*)

 

1b. I tried the check-host, it says "open or filtered" if I use my DDNS or local computer IP. If I put it my router's ip, it says "connection refused". Why is that, shouldnt my DDNS lead to my router's ip? (*)

 

 

2. I managed to get WOL to work:

- I am using the free program from magicpacket.free.fr. If I use as my host name-my PC IP (works with 255 at the end); my PC MAC address; UDP port 9, it works

- now i have both 7 and 9 forwared to my PC ip, with 255 at the end 

- ! it doesn't work if i use my DDNS

 

3. Now, from what I understand, my router can be "interrogated" over the internet - and that's why the checkhost manages to reach it, even though it's refused. What should follow is - that my router redirects this interrogation package, received on a certain port, to the PC network card that's connected though cable to it. 

 

4. So now i'm not sure - let's say i would use this website to wol over the internet - https://www.depicus....ake-on-lan/woli- now the appropriate ip would be my router's ip, since "the internet" can only see that one when my pc's shut down.

Should i use my PC MAC address, my DDNS or router ip, 255.255.255.255 as subnet mask, and port 7 or 9? 

If i put in my local PC ip, it says "it's a private address range and doesn't work over the internet". If i use my DDNS, it manages to send the package, but remember that the DDNS doesnt work through that program from free.fr, maybe that's connected somehow. When I use my DDNS on this website, it says it sent the package to the ip that displays on the check-host site (*)

 

 

6. Or maybe it's the port forwarding - i'll describe what I did there too: 

- my router seems to support port forwarding, and i tried forwarding the ports by writing my local PC ip, but with 255 at the end, in the "local IP field". Protocol UDP. Now, it asks for "Port range" and "Local port" so i wrote 7 or 9 in both those fields, correspondingly. I can also leave Local port empty, so i tried port 7 only in Port range and it didnt work. 

 

My router also haz a DMZ tab, that "exposes one computer to the internet". Maybe we can use it to try out something. 

Edited by trosco, 22 May 2021 - 09:23 AM.

[RKinner]

1.  IP address it shows is what it thinks was the source of the packets it received from you.  Normally this would be your router's IP address but with DDNS it could be your fake IP address.

 

1b.  Don't think you have port forwarding correct.

 

2.  Using 255 at the end of the IP address indicates you want to broadcast to all devices on the local network,  Better would be to run ipconfig on your PC and get the actual IPv4 address assigned to the PC by your router.  This won't change that often.  (If it does there are ways to assign it a static address that doesn't change.)     I'm not really up on DDNS but I expect they have a DNS server/router somewhere which claims your PC's name and associates the IP address with the name.  If I were setting this up there would be a router at the given IP address which would use some version of NAT (Network Address Translate) to forward the traffic on to your router and there woudldalso be a proxy on your PC which would send all traffic to the DDNS server/router which  would then pretend to be the source of the packets.

 

3.  Suspect the port forwarding is not correct.

 

4.  It says on that site that it can use the IP address or the fqdn.  fqdn is fully qualified domain name.  What is your PC's name that the DDNS uses?  That's probably the fqdn.  Try using that and the port number that you know works,  The MAC is probably required by WOL so you will need that and the mask can stay then same.

 

5-

6.  Range is usually more than one port.  Local Port would probably be your 7 or 9 whichever works.  Can you leave Range blank and just put 7 or 9 in the Local Port?

 

 

Putting your PC in the DMZ exposes it to more risk so we want to avoid that if we can.

 

 

 

[trosco]

Hi,

 

Thank you for the clarifications, I've reviewed a bit and I confirm that port forwarding somehow is not working. I don't know what I've set up wrong, but I've looked into the following:

https://www.noip.com...rd-asus-router/< this is for my router brand and model, I've done it as it says here, even tried it with "both" 

check it with your check-host link, it says Connection refused, both on UDP and TCP. Tried the DDNS here. 

checked it with this - https://www.yougetsi...ols/open-ports/and it says "port is closed". Tried both DDNS and external IP address 

 

 

PS: I can't leave range uncompleted. Matter of fact, it only accepts digit values, so i can't even write something like "7000-8000" over there. For now I've opened port 7 on "Both" protocols as it says in the noip link (writing same value in both field).

 

Is there a chance that the router firmware could allow port forwarding but the actual machine wouldn't? I also read that ports can be closed by firewall, so i opened it but still tests as "closed". 

[trosco]

I actually cracked it! 

Cheated a bit by using teamviewer, but it works now. I will get a licence through my company, but it's great to know that I can have personal access from anywhere. 

Thank you for your help and I enjoyed learning a bit about networking too! Let me know if there's a review area, or a donation link that I can help you with if you'd like! 

 

PS: realised there's 3 different firewalls, 2 of which I had to create exceptions for - windows firewall and antivirus firewall. The 3rd, router firewall, had no need for the exception entry. 

PPS: one other way I didn't try and was on my list: to install alternative firmware for my router (Tomato / DD-WRT); 

[RKinner]

Sorry for the delay.

 

I am curious.  Once you got it to work did you try some of the tests I gave you?  Did they work?

 

 

No need for donations.  I'm just happy to have something to do.

[trosco]

I'm not sure if it's port status tests that you are referring to. 

 

check host says for udp port 9 (the one Teamviewer uses for wol) "Connection refused" 

yougetsignal.com says that port 9 (doesn't specify if udp/tcp) is closed.

 

I have port forwarding set up only for upd port 9 now. In the past if I set up port forwarding for udp 7, check host would say Connection Refused, now it says "open or filtered". 

 

Maybe it's still something related to firewall - although teamviewer started working after i allowed that port through both through windows firewall and Kasperski (my antivirus). So I guess that means that those 2 layers of firewall were all it took. No idea why using something like depicus still doesn't work.