Forum Home
Press F1
Thread ID: 122209	2011-12-07 20:39:00	Port Forwards - I must be losing the plot here!	wratterus (105)	Press F1

Post ID	Timestamp	Content	User
1247644	2011-12-07 20:39:00	Bit of an odd one today… Customer just changed to Callplus and got sent a new router (Dynalink RTA1025W V6). Decided they wanted remote access set up – no trouble at all (or so I thought). Set up an IP reservation, forward port 3389 to that IP, check the firewall rule was enabled on the PC in question, should be all good. Nope. I’m using canyouseeme.org to check if the port is actually open or not, I’ve used that many times in the past with no issues. I also totally disabled the windows firewall on the PC in question, and tried another couple of ports, no joy. The router just didn’t seem to be forwarding the ports through to the PC. I re-flashed the latest firmware and reset to defaults, tried again, same thing. Tried their old D-Link router – same issue. Ports won’t forward. So at this point, I figure it’s got to be some odd issue with the PC. Maybe remnants of an old firewall or something. So I tried a brand new Windows 7 laptop, same issues! Double and triple checked all the settings and IP addresses, all correct. But the ports still won’t forward. At this stage, I think I’m starting to go a bit nuts – this is something I do on a daily basis, I’ve got remote connections setup here there and everywhere, with all manner of OS’s and modems – never had any issues. So I bring the modem back to the office – try it with my own PC. (and on a different ISP) I’ve got remote desktop setup on my own PC listening with port 3391, and there is a windows firewall rule setup to go along with that, so I forward port 3391 to my PC, and voila, it works straight away. So I try a different port – 3395 for example. Setup an identical rule on my PC for that port – no go. Wont forward. Disable the windows firewall totally – same thing – won’t forward. I then edited the rule for port 3391 that is working, changed to port 3395 – won’t work. But when I change that rule, port 3391 is blocked, so the rule is behaving properly. Now I really think I’m doing something stupid and missing something obvious – so I try two different modems – exactly the same thing happens. Port 3391 will forward to my PC fine, but not any other ports, even if the windows firewall is totally disabled on my PC, and if I setup an inbound rule for whatever port I’m forwarding. To make sure the firewall is disabling properly, I removed the rule for port 3391 all together, so ports 3391 and 3395 and forwarded to my PC, neither are working with the firewall enabled, and all the rules I've added removed. Turn off the windows firewall, port 3391 forwards, port 3395 doesn't. I’m feeling like a total muppet right at the moment, but this has got me stumped. Any ideas? :blush: Thanks	wratterus (105)
1247645	2011-12-07 20:57:00	Use teamviewer instead	Speedy Gonzales (78)
1247646	2011-12-07 23:49:00	A change in the RDC port no. requires a registry entry changes as well ?? Team veiwer can sometimes detect when its being used to commercial use, with popups saying, "commercial use detected" , "play fair" . Thats not a good look when it also shows on the customers/clients PC.	1101 (13337)
1247647	2011-12-08 00:08:00	try adding to the DMZ (temporarily) and see if that helps. If a clean PC on the DMZ isn't working then something is weirdly wrong!	The Error Guy (14052)
1247648	2011-12-08 07:19:00	Set up an IP reservation, forward port 3389 Every single time I've tried that method theres always been troubles of some kind. If I wanted to have remote desktop, using the inbuilt Windows, then I would set the IP address on the PC to static, completely ignoring the router reserving an IP. On my WHS you have a static IP, then to port forward ports (HTTPS) port 443 & (RWW) 4125 and for remote desktop (RDP) port 3389 to the static IP, Works perfectly. or as speedy suggested team Viewer, that does it all for you, no setting up port forwarding, IP reservation -- naught. With TV, you can set a own password etc, and set it to run automatically on startup if required. Thats how I have it setup on a Business I do all the IT work for, I can log into any one of their six PC, and server at any time. Sometime when they call,:badpc: its "sit back touch nothing" especially if its a simple 1-2 minute fix thats not worth traveling for. Payment -- Just make sure you have those nice choc biscuits next time I call for some real problems :D	wainuitech (129)
1247649	2011-12-08 08:36:00	A change in the RDC port no . requires a registry entry changes as well ?? Team veiwer can sometimes detect when its being used to commercial use, with popups saying, "commercial use detected" , "play fair" . Thats not a good look when it also shows on the customers/clients PC . This is correct but you can forward any external port to the internal port of RDP - 3389 on a PC . That way you don't have to worry about changing the actual RDP port on the PC in the registry . EG: Whenever I have a PC setup for remote desktop I setup port forwarding of port 43389 to port 3389 . You don't really want to forward the actual port 3389 as there are tons of bots on the internet scanning for open ports on 3389 and when they find one they will try and log in . I had a someone come in just last week as someone had logged into their machine via remote desktop and changed the password! When you want to connect to a remote desktop session using a different port forward rule, like the one above, you just add the port number to the end of your IP/domain address . EG: With port 43389 forwarded you would connect with myip . dyndns . org:43389 or 123 . 123 . 123 . 123:43389	CYaBro (73)
1