VNC - Too many authentication failures
Clash Royale CLAN TAG#URR8PPP
I've been trying to Google, but all of the issues refers connection from PC to remote VNC server.
So. I have an issue with VNC communication from Android to Linux. I have installed a TightVNC Server on latest Ubuntu version which works fine if I connect to it from PC with RealVNC Viewer on port 5901.
I downloaded a VNC Viewer by RealVNC for Android and if I try to connect to my remote host it says "Too many authentication failures" even on first try.
I also tried a couple different VNC Viewers, but result is exactly same.
What would be the reason and how I am able to fix it? Some people were speaking about that the client can be unsecure, but I'm not sure what difference there would be with PC and Android version of VNC.
From PC to remote: Works
From Android to remote: Doesn't work
About half-year ago on my different server I had no similar issues. It was working fine, no matter what device I used to connect VNC if I knew IP, port and password.
ubuntu authentication vnc android
asked Nov 6 '16 at 3:37
Weird E.Weird E.
1117
add a comment |
I've been trying to Google, but all of the issues refers connection from PC to remote VNC server.
So. I have an issue with VNC communication from Android to Linux. I have installed a TightVNC Server on latest Ubuntu version which works fine if I connect to it from PC with RealVNC Viewer on port 5901.
I downloaded a VNC Viewer by RealVNC for Android and if I try to connect to my remote host it says "Too many authentication failures" even on first try.
I also tried a couple different VNC Viewers, but result is exactly same.
What would be the reason and how I am able to fix it? Some people were speaking about that the client can be unsecure, but I'm not sure what difference there would be with PC and Android version of VNC.
From PC to remote: Works
From Android to remote: Doesn't work
About half-year ago on my different server I had no similar issues. It was working fine, no matter what device I used to connect VNC if I knew IP, port and password.
ubuntu authentication vnc android
asked Nov 6 '16 at 3:37
Weird E.Weird E.
1117
It is always better to SSH tunnel your VNC connection. VNC will lock (i.e. "too many authentication failures") after a couple of failed attempts, and, since there are a lot of people scanning ports out there, it will always happen sooner or after. Running VNC on localhost and then doingssh -Lis better (and can be safer if you use pubkey authentication for the SSH connection).
– grochmal
Nov 6 '16 at 4:18
@grochmal thank you for information. I will Google for more about SSH tunnel since I don't know how do I use it with VNC. I just wanted to comment that it doesn't make that on my PC. I can still connect there with PC and I didn't made any failed logins and login credentials has been verified to be correct. Also my server has been rent a couple days ago so I don't think about someone else trying to connect there.
– Weird E.
Nov 6 '16 at 5:21
add a comment |
I've been trying to Google, but all of the issues refers connection from PC to remote VNC server.
So. I have an issue with VNC communication from Android to Linux. I have installed a TightVNC Server on latest Ubuntu version which works fine if I connect to it from PC with RealVNC Viewer on port 5901.
I downloaded a VNC Viewer by RealVNC for Android and if I try to connect to my remote host it says "Too many authentication failures" even on first try.
I also tried a couple different VNC Viewers, but result is exactly same.
What would be the reason and how I am able to fix it? Some people were speaking about that the client can be unsecure, but I'm not sure what difference there would be with PC and Android version of VNC.
From PC to remote: Works
From Android to remote: Doesn't work
About half-year ago on my different server I had no similar issues. It was working fine, no matter what device I used to connect VNC if I knew IP, port and password.
ubuntu authentication vnc android
asked Nov 6 '16 at 3:37
Weird E.Weird E.
1117
I've been trying to Google, but all of the issues refers connection from PC to remote VNC server.
So. I have an issue with VNC communication from Android to Linux. I have installed a TightVNC Server on latest Ubuntu version which works fine if I connect to it from PC with RealVNC Viewer on port 5901.
I downloaded a VNC Viewer by RealVNC for Android and if I try to connect to my remote host it says "Too many authentication failures" even on first try.
I also tried a couple different VNC Viewers, but result is exactly same.
What would be the reason and how I am able to fix it? Some people were speaking about that the client can be unsecure, but I'm not sure what difference there would be with PC and Android version of VNC.
From PC to remote: Works
From Android to remote: Doesn't work
About half-year ago on my different server I had no similar issues. It was working fine, no matter what device I used to connect VNC if I knew IP, port and password.
ubuntu authentication vnc android
ubuntu authentication vnc android
asked Nov 6 '16 at 3:37
Weird E.Weird E.
1117
asked Nov 6 '16 at 3:37
Weird E.Weird E.
1117
asked Nov 6 '16 at 3:37
Weird E.Weird E.
1117
asked Nov 6 '16 at 3:37
Weird E.Weird E.
1117
asked Nov 6 '16 at 3:37
Weird E.Weird E.
1117
1117
It is always better to SSH tunnel your VNC connection. VNC will lock (i.e. "too many authentication failures") after a couple of failed attempts, and, since there are a lot of people scanning ports out there, it will always happen sooner or after. Running VNC on localhost and then doingssh -Lis better (and can be safer if you use pubkey authentication for the SSH connection).
– grochmal
Nov 6 '16 at 4:18
@grochmal thank you for information. I will Google for more about SSH tunnel since I don't know how do I use it with VNC. I just wanted to comment that it doesn't make that on my PC. I can still connect there with PC and I didn't made any failed logins and login credentials has been verified to be correct. Also my server has been rent a couple days ago so I don't think about someone else trying to connect there.
– Weird E.
Nov 6 '16 at 5:21
add a comment |
It is always better to SSH tunnel your VNC connection. VNC will lock (i.e. "too many authentication failures") after a couple of failed attempts, and, since there are a lot of people scanning ports out there, it will always happen sooner or after. Running VNC on localhost and then doingssh -Lis better (and can be safer if you use pubkey authentication for the SSH connection).
– grochmal
Nov 6 '16 at 4:18
@grochmal thank you for information. I will Google for more about SSH tunnel since I don't know how do I use it with VNC. I just wanted to comment that it doesn't make that on my PC. I can still connect there with PC and I didn't made any failed logins and login credentials has been verified to be correct. Also my server has been rent a couple days ago so I don't think about someone else trying to connect there.
– Weird E.
Nov 6 '16 at 5:21
It is always better to SSH tunnel your VNC connection. VNC will lock (i.e. "too many authentication failures") after a couple of failed attempts, and, since there are a lot of people scanning ports out there, it will always happen sooner or after. Running VNC on localhost and then doing
ssh -L is better (and can be safer if you use pubkey authentication for the SSH connection).– grochmal
Nov 6 '16 at 4:18
It is always better to SSH tunnel your VNC connection. VNC will lock (i.e. "too many authentication failures") after a couple of failed attempts, and, since there are a lot of people scanning ports out there, it will always happen sooner or after. Running VNC on localhost and then doing
ssh -L is better (and can be safer if you use pubkey authentication for the SSH connection).– grochmal
Nov 6 '16 at 4:18
@grochmal thank you for information. I will Google for more about SSH tunnel since I don't know how do I use it with VNC. I just wanted to comment that it doesn't make that on my PC. I can still connect there with PC and I didn't made any failed logins and login credentials has been verified to be correct. Also my server has been rent a couple days ago so I don't think about someone else trying to connect there.
– Weird E.
Nov 6 '16 at 5:21
@grochmal thank you for information. I will Google for more about SSH tunnel since I don't know how do I use it with VNC. I just wanted to comment that it doesn't make that on my PC. I can still connect there with PC and I didn't made any failed logins and login credentials has been verified to be correct. Also my server has been rent a couple days ago so I don't think about someone else trying to connect there.
– Weird E.
Nov 6 '16 at 5:21
add a comment |
1 Answer
1
active
oldest
votes
When I get this error message I usually log into the server and restart the vncserver and it works again
$ vncserver -kill :1
$ vncserver
answered Feb 7 at 19:42
GiorgosKGiorgosK
1011
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f321372%2fvnc-too-many-authentication-failures%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
When I get this error message I usually log into the server and restart the vncserver and it works again
$ vncserver -kill :1
$ vncserver
answered Feb 7 at 19:42
GiorgosKGiorgosK
1011
add a comment |
When I get this error message I usually log into the server and restart the vncserver and it works again
$ vncserver -kill :1
$ vncserver
answered Feb 7 at 19:42
GiorgosKGiorgosK
1011
add a comment |
When I get this error message I usually log into the server and restart the vncserver and it works again
$ vncserver -kill :1
$ vncserver
answered Feb 7 at 19:42
GiorgosKGiorgosK
1011
When I get this error message I usually log into the server and restart the vncserver and it works again
$ vncserver -kill :1
$ vncserver
answered Feb 7 at 19:42
GiorgosKGiorgosK
1011
answered Feb 7 at 19:42
GiorgosKGiorgosK
1011
answered Feb 7 at 19:42
GiorgosKGiorgosK
1011
answered Feb 7 at 19:42
GiorgosKGiorgosK
1011
1011
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f321372%2fvnc-too-many-authentication-failures%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It is always better to SSH tunnel your VNC connection. VNC will lock (i.e. "too many authentication failures") after a couple of failed attempts, and, since there are a lot of people scanning ports out there, it will always happen sooner or after. Running VNC on localhost and then doing
ssh -Lis better (and can be safer if you use pubkey authentication for the SSH connection).– grochmal
Nov 6 '16 at 4:18
@grochmal thank you for information. I will Google for more about SSH tunnel since I don't know how do I use it with VNC. I just wanted to comment that it doesn't make that on my PC. I can still connect there with PC and I didn't made any failed logins and login credentials has been verified to be correct. Also my server has been rent a couple days ago so I don't think about someone else trying to connect there.
– Weird E.
Nov 6 '16 at 5:21