Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards

About handofreason

  • Title

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Guys this was it. I had to go into the registry and change it from another port; The person who set this up probably changed this as a way to prevent any tampering. Well played other guy... well played. What threw me off is that all the inbound rules for the firewall were set to 3389. Everything was default except for this one thing. Thanks everyone! (The registry edit was HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\ and then PortNumber subkey. Double click that and chang HEX to Decimal and there's your port. Mine was set to some random number that had no inbound rules for it anyway)
  2. Yes the RDP service is running, but no I cannot connect locally. I can only ping it, but that's it. The RDC app just throws back the error that's in my OP. By the way I appreciate you taking the time to help me out.
  3. Yes I just pinged the default gateway, and yes it is working: Pinging with 32 bytes of data: Reply from bytes=32 time<1ms TTL=64 Reply from bytes=32 time<1ms TTL=64 Reply from bytes=32 time<1ms TTL=64 Reply from bytes=32 time<1ms TTL=64 Ping statistics for Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms I've done port forwarding before, usually for a torrent client so I'm open and connectable. On the router itself, I did two instances of port forwarding. One was IP specific: And the other was a universal protocol:
  4. DNS is set to openDNS servers on the server itself. On the router... I think they might be set to default or maybe Google. I'll have to check. How do I verify a working Default Gateway?
  5. LAN. The machine is literally next to me, connected to the same switch. Is there a possibility the switch is the culprit? ? I've created an inbound rule in Windows Firewall for that specific port, and also forwarded the port in the router for both TCP/UDP. Checking with the port checker still reports back that 3389 is closed, which confirms my earlier netstat test. I'm using Teamviewer now actually, but I'll try AnyDesk also just so I have an alternative for future reference. So the machine I'm trying to remote from is literally right next to it on the same switch. I can ping it just fine, and the router sees it (albeit with no PC name), and I can put port forwarding rules on the IP address within the router. Despite all that, RDC still won't connect to it, giving me the error that I mentioned above.
  6. Hey all, I've been combing Google and various forums for a few days now and nothing has worked. Hopefully you guys can help me out. I'm repurposing a Dell PowerEdge T130 on Windows Server 2012 R2 from my work, and I cannot connect to the machine to save my life. I've currently enabled/disabled everything I can think of right now just for the purposes of testing: Windows Firewall is turned off (domain, private, public) 3389 Port forwarded on the router and in the firewall inbound rules (even though it's now turned off) Put the IP address of the server in DMZ on the router Checked various registry settings as per recommended solutions related to this problem Turned off network authentication for users As far as I'm aware, this thing should be wide open and I cannot connect to it. For one thing, netstat -an still doesn't list 3389 as a listened port. On another machine in my network, trying to RDP into it gives a generic error as if I typed in a non-existent device: The thing is, I can ping the device no problem from this other computer. It shows up in the router and I can ping there no problem. It just refuses to connect via RDP and I have no idea why! EDIT: Also I have a feeling I'm missing something painfully obvious. So hopefully another set of eyes will see that and tell me what's wrong. SOLUTION: Thanks to everyone here for the troubleshooting. Turns out the default RDP port was changed in the registry so all of the normal inbound rules and solutions were ineffective. The registry key changed was HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\ then double-click on subkey:PortNumber and change from HEX to Decimal. There's your port number that everything else needs sync to.)