Remote Desktop Service suddenly stopped working and displays error

Hi Folks,
I can RDP to my TS server from within the local Network, but from the internet, I get the following error messages.

I am not sure what it could be and could only suspect that my ISP has done something to the public IP address, though a ping to that server (FQDN)  still returns the correct IP.

Please see attached screenshot.
Thank you
Gospodin RasputinIT ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

can you connect to the public IP with telnet or any other similar app (netcat etc.) on port 3389?
Kennyboy5IT Support AnalystCommented:
Do you have a vpn running before RDPing?


a quick test you can do is try to telnet the public IP address of your terminal server on TCP port 3389.

If you are able to telnet on this TCP port then you ISP hasent blocked the connect and we can troubleshoot other aspect.

Also check if the windows firewall is not active.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

What AV are you running?  I know by default Kaspersky allows RDP from the local network but will block from any other network.
Gospodin RasputinIT  ManagerAuthor Commented:
A telnet to the TCP port fails

I get the following error  message when I telnet. "Connection closed by Remote Host"

I am using Sophos anti-virus and it has always worked until lastw weekend
The error indicate that the connection to that IP has been blocked for port 3389 which should not have been done without letting you know.

You need to speak to your ISP and have it allowed.
Can be like netballi said, but I doubt it's blocked by the ISP. This means that the connection attempt reaches the machine (otherwise the error will be unable to connect), but is then actively refused by the windows machine itself.
See the antivirus settings, chances are that some update or upgrade of it blocks the port. Also look at the windows update list in installed programs & features control panel, are there any updates installed at the same date, or later after your RDP connection stopped working?
Gospodin RasputinIT  ManagerAuthor Commented:
Thanks to everyone.
The problem was that the domain had been transferred to another ISP who incorrectly amended the DNS records with the wrong IP.

So when I telneted, I was actually telnetting to the incorrect IP. A telnet to the correct IP works. I shall share the  points thus.
Gospodin RasputinIT  ManagerAuthor Commented:
The error was caused by a change in DNS settings at the ISP, but the comments provided by the Experts helped me troubleshoot.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server Apps

From novice to tech pro — start learning today.