Link to home
Start Free TrialLog in
Avatar of Bigmerv307
Bigmerv307Flag for United States of America

asked on

Outdated TLS security

Good morning,
I receive this error when i try to remote into my office computer from home. " Can't connect securely to this page" This might be because the site uses outdated or unsafe TLS security settings.

My server is SBS 2003 R2. Remote access worked great until today.

Please help, very urgent.
Avatar of Kevin Brown-Goebeler
Kevin Brown-Goebeler
Flag of United States of America image

You must realize that SBS 2003 went off support back in July 2015. Why do you want to continue to use software that hasn't received a security update in nearly 4 years?  Its surprising you haven't had problems sooner.
You don't give any details on how you are accessing the machine. What browser are you using and version. Many browser makers have decided to prevent connections to sites using outdated SSL & TLS protocols. Today only TLS 1.2 & 1.3 are considered secure. What security protocols have you enabled on the server?
Avatar of Bigmerv307

ASKER

Trust me my friend, it is not by choice.  The company i work for, is not in a hurry to purchase i new server, i have been asking for years. i just try my best to keep it running and it has been great.

I really just need help getting RWW to work again. I would greatly appreciate it if someone could help. I think the issue is with TLS, but not sure, I am not strong in SSL or TLS or IIS department.

Thanks for your response
This message relates to your TLS settings.

You'll have to retire protocols SSL2, SSL3, TLSv1.0, TLSv1.1 which will leave TLSv1.2 + TLSv1.3 as only protocols enabled.

To expand Kevin's comment. Your code is old + you should update.

Because your code is so old, the required protocol support may be missing, so you may have to upgrade for any client to connect.
After digging through Microsoft's docs, your server version doesn't support any TLS protocol versions, so you must upgrade for modern clients to connect.
Windows Server 2008 SP2 is first version to add TLSv1.2 so is the absolute minimum version required for modern clients to connect.

https://blogs.msdn.microsoft.com/kaushal/2011/10/02/support-for-ssltls-protocols-on-windows provides history of when support was added.
I am very grateful for your answers.
Something must have happen overnight, i have had no issues until this morning.
Were there any automatic updates to your software? Have you checked the certs time stamp?
You can test your browser and web server protocol support at this site:

https://www.ssllabs.com

Post your results for protocols for each and we'll see if any match.
Thanks for the info. But i haven't done an update on this SBS 2003 in 2 years. I also can seem to get in contact with my SSL cert provider. So i went ahead and purchase remote access for everyone. That took care of remote access for the employees.
SSL Report: maringoodman.com
Assessed on:  Tue, 09 Apr 2019 17:12:11 UTC | Hide | Clear cache
Scan Another >>

       Server      Test time      Grade
1      2606:4700:30:0:0:0:6818:67ac
Ready
Tue, 09 Apr 2019 17:09:04 UTC
Duration: 41.713 sec      
A
2      2606:4700:30:0:0:0:6818:66ac
Ready
Tue, 09 Apr 2019 17:09:46 UTC
Duration: 41.863 sec      
A
3      104.24.103.172
Ready
Tue, 09 Apr 2019 17:10:28 UTC
Duration: 51.748 sec      
A
4      104.24.102.172
Ready
Tue, 09 Apr 2019 17:11:19 UTC
Duration: 51.632 sec      
A
SOLUTION
Avatar of Kevin Brown-Goebeler
Kevin Brown-Goebeler
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You also never stated the browser you are using to connect.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Great support, thank you guys. Greatly appreciated.
Good morning All,

So great news, All i did was rebooted my SBS 2003 R2 Server and the issue went away. Everything is back to normal. Remote access is working again.