Windows Client - 5.3.0 | ...
Windows Client - 5.3.0 | won't authenticate login credentials
- Accueil
- Espace Client
- Community Forum
- Services
- Dynamic DNS Service
- Windows Client - 5.3.0 | won't authenticate login credentials
- Community Forum
- Windows Client - 5.3.0 | won't authenticate login credentials
Topic: Windows Client - 5.3.0 | won't authenticate login credentials
I've been using the Windows Client for the IP Address update for some time now. It's been a couple months since I've logged into the client to update IP's and generally, ensure all is well. As of 6/7/2018, I'm now no longer able to log into the Dynu.Client via my login credentials. It always throws a "invalid user name of password" error. These same credentials are used to log into the web portal, which is how I am able to post. I've also uninstalled and re-installed the latest from the web portal Control Panel, but no avail.Is there something that has changed recently preventing the client from working?Thanks in advance!-J
Reply with quote | Report
1. Make sure you are using the username instead of the email address.2. Check if you have assigned a Location name to your hostnames. Not using the correct location name or not using the location name at all may also cause an authentication error.
Reply with quote | Report
Re: Windows Client - 5.3.0 | won't authenticate login credentials
by Ptochos on vendredi 25 janvier 2019
by Ptochos on vendredi 25 janvier 2019
I'm using my username (not enail) and password. I can log into the Dynu website and do everything in the control panel, but the Dynu.Client continually responds "Unable to authenticate."I have updated the "update IP update password" to be the same as the site password (as it originally was), and uninstalled and reinstalled the Dynu.Client, but it still fails to authenticate.I can't be sure that it will update my IP anymore.What can I do?
Reply with quote | Report
Re: Windows Client - 5.3.0 | won't authenticate login credentials
by Ptochos on samedi 26 janvier 2019
by Ptochos on samedi 26 janvier 2019
Resolved: Enable TLS 1.0I disabled TLS 1.0 on my server for PCI compliance, and it broke the Dynu.Client
Reply with quote | Report
Author | Topic: Windows Client - 5.3.0 | won't authenticate login credentials |
---|---|
jgarcia69 Joined: 29/10/2016 |
Windows Client - 5.3.0 | won't authenticate login credentials jeudi 7 juin 2018 06:46
I've been using the Windows Client for the IP Address update for some time now. It's been a couple months since I've logged into the client to update IP's and generally, ensure all is well. As of 6/7/2018, I'm now no longer able to log into the Dynu.Client via my login credentials. It always throws a "invalid user name of password" error. These same credentials are used to log into the web portal, which is how I am able to post. I've also uninstalled and re-installed the latest from the web portal Control Panel, but no avail.Is there something that has changed recently preventing the client from working?Thanks in advance!-J
|
jdidi Joined: 23/06/2017 |
Windows Client - 5.3.0 | won't authenticate login credentials vendredi 15 juin 2018 21:39
1. Make sure you are using the username instead of the email address.2. Check if you have assigned a Location name to your hostnames. Not using the correct location name or not using the location name at all may also cause an authentication error.
|
Ptochos Joined: 04/12/2015 |
Windows Client - 5.3.0 | won't authenticate login credentials vendredi 25 janvier 2019 16:20
I'm using my username (not enail) and password. I can log into the Dynu website and do everything in the control panel, but the Dynu.Client continually responds "Unable to authenticate."I have updated the "update IP update password" to be the same as the site password (as it originally was), and uninstalled and reinstalled the Dynu.Client, but it still fails to authenticate.I can't be sure that it will update my IP anymore.What can I do?
|
Ptochos Joined: 04/12/2015 |
Windows Client - 5.3.0 | won't authenticate login credentials samedi 26 janvier 2019 09:35
Resolved: Enable TLS 1.0I disabled TLS 1.0 on my server for PCI compliance, and it broke the Dynu.Client
|
It is currently mercredi 30 octobre 2024 19:49 US Mountain Standard Time
mercredi 30 octobre 2024 19:49