Home > Remote Desktop > Remote Desktop - Only Port 3389 Works

Remote Desktop - Only Port 3389 Works


Not sure if that would help out your situation, but extra ammo always helps. Try to explain the problem to the best of your ability, and include any steps you’ve already taken together with their results while troubleshooting the issue, it will help our support are still working even now.Most of my client computers are affected, at least the ones actually located on my internal network. The official documentation is here: http://technet.microsoft.com/en-us/library/dd983949(WS.10).aspx Installing the configuring the role service is mostly as described; however, using a Calnet issued trusted Comodo certificate is recommended. http://phpbbinstallers.net/remote-desktop/remote-desktop-works-from-phone-but-not-from-computer.html

Kind regards, Freek Berson The Microsoft Platform Twitter Linked-in Wortell company website Edited by Freek BersonMVP, Moderator Wednesday, August 22, 2012 6:04 PM Marked as answer by JRB5791 Wednesday, August 22, Edited by JRB5791 Wednesday, August 22, 2012 3:34 PM Wednesday, August 22, 2012 3:33 PM Reply | Quote Answers 1 Sign in to vote Let me try to quickly talk you All rights reserved Use of this Site constitutes acceptance of our User Agreement (effective 3/21/12) and Privacy Policy (effective 3/21/12), and Ars Technica Addendum (effective 5/17/2012) Your California Privacy Rights The Try "telnet your.home.box 3389". https://www.eightforums.com/network-sharing/56592-remote-desktop-only-port-3389-works-even-after-changing.html

Remote Desktop Connection Behind Firewall

Both of these would in most cases be enabled as long as the server is still using the standard 3389 TCP port for RDP connections. When they launch a Remote App (or full desktop) from the RD Web Access page that will still be port 3389 from the client to the RD Session Host. Once you're done setting things up, you should be able to log into Remote Desktop over the internet by connecting to the public IP address your router exposes for your local

External IP Setup and Access Remote Desktop Why can't I use Remote Desktop? To control access to the systems even more, using “Restricted Groups” via Group Policy is also helpful. Also your RDP server must have a static IP in order for the port forwarding in the router to work correctly.Some routers have a setting that when you have servers on Rdp Port Disabling it may not be enough.

Open the Windows Firewall with Advanced Security by searching for "firewall" in the start menu. Rdp Through Firewall That merely is a different app (an active x based one) to access terminal services on the standard port.ostiguy bash666 Ars Legatus Legionis Registered: Nov 28, 2000Posts: 24387 Posted: Wed Mar Remote desktop to active session no longer works in 8.1? Look for rows with your RDP port number (3389 by default) and check the program ID (PID) at the end of these lines.

We've covered a number of ways to set up your own home VPN server, including a way to create a VPN server in Windows without any extra software or services. Port 443 Enable Network Level Authentication Windows Vista, Windows 7, and Windows Server 2008 also provide Network Level Authentication (NLA) by default. Router has port 3389 set for port forwarding, aVast Firewall allows port 3389 in and out. Computer Type PC/Desktop OS Windows 8.1 Pro with Media Center CPU Intel Core i7-2600K @ 4GHz Motherboard MSI Z68A-GD80 B3 Memory G.SKILL Ripjaws X 8GB (2 x 4GB) DDR3 1600 Graphics

Rdp Through Firewall

Does Hobbes ever do anything that Calvin himself could not do? https://social.technet.microsoft.com/Forums/windows/en-US/521b9d38-bcaa-40db-9a7f-f392d1615d1c/unable-to-use-webbased-remote-desktop-and-remote-app-if-port-3389-is-disabled?forum=winserverTS The server is not confirming the connection or the confirmation packets are lost before leaving the server itself.Wireshark does not show the server sending back SYN-ACK packets except when the client Remote Desktop Connection Behind Firewall Operator that combines sum, product and difference between two numbers How do I get an Item from Sitecore's internal URI protocol? Teamviewer Blocked At Work asked 7 years ago viewed 208409 times active 1 year ago Related 2Windows Remote Desktop (RDP/MSTSC) fails with Error Code: 54Am I looking at the console when I use remote desktop?2RDCMAN

All rights reserved.Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks|Site Feedback current community chat Server Fault Meta Server Fault your communities Sign up or log in to customize your list. check my blog VPN VERSUS REMOTE DESKTOP No Remote Desktop After SP2 Install XP Remote Desktop help More resources Tom's Hardware Around the World Tom's Hardware Around the World Russia France Germany UK Italy If an SSH server is available, you can use SSH tunneling for Remote Desktop connections. Why isn't that failing just like this has been all day, I can't figure it out. :lI tested with the firewall disabled on both ends of the connection and there was Remote Desktop Port Forwarding

This will ensure that the computer’s internal IP address won’t change--if it does, you’ll have to change your port forwarding configuration. I can only log into one computer at home from the office. Microsoft Customer Support Microsoft Community Forums Windows Client   Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 this content But, once you've got the setup done, Remote Desktop provides a pretty powerful and reliable way of accessing your PCs remotely and without requiring any additional services.

When you RDP to the office's IP address, it'll forward it to your computer. Gotomypc Honeywell Lyric: Which Smart Thermostat Should You Buy? Hopefully this answers your questions!

I did not know about setting off any alarms though.

share|improve this answer answered May 25 '09 at 19:21 community wiki Brandon add a comment| up vote 2 down vote If you don't want to use 3389 externally, open a different Change RDP port number Should you find a port conflict, you can resolve it by changing the port used by one of the applications. In that section, look for the IPv4 address. Logmein Finally this has happened...

Thats why its a big deal.I know its anal - but its the security admin who is going to lose his job if confidential data gets out, or a hacker gets Have even tried with aVast turned off but can't get it to work. Open the Properties for one of the Ethernet adapters, select Internet Protocol Version 6 or 4 and click on Properties button underneath. have a peek at these guys RELATED ARTICLESRemote Desktop Roundup: TeamViewer vs.

You can use telnet and netstat to test if you can connect to specific ports. I'm not an admin, or i'd probably just open the port myself because i do find it handy to be able to access my computer from any location, especially work where Not Available to VZ [VerizonFiOSTV] by The Fuzz 53691. 24, 7, 365 [No,IWillNotFixYour#@$!!Computer] by onebadmofo642. Change registry entry in XP to use port 80 for RDP listening.3.

How can waiting 24 hours to change the password again be secure? more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation Science We highly recommend that you make a backup of your server before making any changes. When you are certain that Windows Firewall is allowing RDP connections, also check the server specific firewall settings at your UpCloud Control Panel.

Thanks.I'll have to read up on UPnP, i'm not up with it very well at all.If anyone wants to give a quick overview, that'd be cool too!Just a quick question...how will Sykus Ars Legatus Legionis Tribus: Silicon Valley Registered: Sep 20, 1999Posts: 16539 Posted: Tue Apr 30, 2002 2:48 pm i can get the remote desktop working fine, but i can't use Don't forget Remote Desktop" works in NON metro mode too -- here in Network & Sharing Hi there this little trick STILL works in W8 RP. There isthe RD Session Host Role which obviously by default listens on port 3389.

To set an account lockout policy: Go to Start-->Programs-->Administrative Tools-->Local Security Policy Under Account Policies-->Account Lockout Policies, set values for all three options. 3 invalid attempts with 3 minute lockout durations This is arguably a bit more secure than than leaving the default port open. Slow connection If your Remote Desktop connection works, but feels slow or disconnects at times, you should try updating the network drivers.