Access denied SSH from windows to linux via putty

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I have a fresh install of openSUSE (tumbleweed) that I am trying to access via ssh from my Windows 7 box on my local home network. I can ping the boxes from each other successfully. I have edited the /etc/ssh/sshd_config file on the openSUSE box and changed the port to 2223. I have added the line AllowUsers (mylogin) to ssh_config. PermitRootLogin is set to no. PasswordAuthentication is set to yes. I generated a public key on my windows machine and copied it to the openSUSE machine via a flash drive and added it to my .ssh/authorized_keys, but my understanding is this shouldn't be needed if I have PasswordAuthentication set to yes.



I have done these things after researching different solutions on the internet but I can't seem to find a solution to my problem: I can't login to my openSUSE box from Windows via Putty. I can connect to a session but I get 'Access Denied' everytime I attempt a login.



edit* I can login via ssh on my linux box from my linux box using



ssh openSUSEcomputername -p 2223









share|improve this question























  • Firewall/Apparmor problem? and/or windows firewall problem?
    – mdpc
    Aug 22 '16 at 21:18











  • Is something like iptables enabled by default while installing suse ?
    – MelBurslan
    Aug 22 '16 at 21:19










  • from windows, open up a command prompt and try running telnet suselinuxservername 2223 what do you see ?
    – MelBurslan
    Aug 22 '16 at 21:20











  • @MelBurslan the response to telnet is a blank screen that says SSH-2.0-OpenSSH_7.2 and has a blinking cursor on the next line. If I don't type anything I get Connection to host lost after a couple minutes.
    – doval
    Aug 22 '16 at 21:32











  • Then you don't have a firewall problem. Try shutting down sshd and starting in debug mode for one single instance with sshd -p 2223 -D -ddd -e and try logging in from your windows machine, while watching the log screen on your linux box. It may give you the indication why it is giving access denied message.
    – MelBurslan
    Aug 22 '16 at 22:50














up vote
1
down vote

favorite












I have a fresh install of openSUSE (tumbleweed) that I am trying to access via ssh from my Windows 7 box on my local home network. I can ping the boxes from each other successfully. I have edited the /etc/ssh/sshd_config file on the openSUSE box and changed the port to 2223. I have added the line AllowUsers (mylogin) to ssh_config. PermitRootLogin is set to no. PasswordAuthentication is set to yes. I generated a public key on my windows machine and copied it to the openSUSE machine via a flash drive and added it to my .ssh/authorized_keys, but my understanding is this shouldn't be needed if I have PasswordAuthentication set to yes.



I have done these things after researching different solutions on the internet but I can't seem to find a solution to my problem: I can't login to my openSUSE box from Windows via Putty. I can connect to a session but I get 'Access Denied' everytime I attempt a login.



edit* I can login via ssh on my linux box from my linux box using



ssh openSUSEcomputername -p 2223









share|improve this question























  • Firewall/Apparmor problem? and/or windows firewall problem?
    – mdpc
    Aug 22 '16 at 21:18











  • Is something like iptables enabled by default while installing suse ?
    – MelBurslan
    Aug 22 '16 at 21:19










  • from windows, open up a command prompt and try running telnet suselinuxservername 2223 what do you see ?
    – MelBurslan
    Aug 22 '16 at 21:20











  • @MelBurslan the response to telnet is a blank screen that says SSH-2.0-OpenSSH_7.2 and has a blinking cursor on the next line. If I don't type anything I get Connection to host lost after a couple minutes.
    – doval
    Aug 22 '16 at 21:32











  • Then you don't have a firewall problem. Try shutting down sshd and starting in debug mode for one single instance with sshd -p 2223 -D -ddd -e and try logging in from your windows machine, while watching the log screen on your linux box. It may give you the indication why it is giving access denied message.
    – MelBurslan
    Aug 22 '16 at 22:50












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I have a fresh install of openSUSE (tumbleweed) that I am trying to access via ssh from my Windows 7 box on my local home network. I can ping the boxes from each other successfully. I have edited the /etc/ssh/sshd_config file on the openSUSE box and changed the port to 2223. I have added the line AllowUsers (mylogin) to ssh_config. PermitRootLogin is set to no. PasswordAuthentication is set to yes. I generated a public key on my windows machine and copied it to the openSUSE machine via a flash drive and added it to my .ssh/authorized_keys, but my understanding is this shouldn't be needed if I have PasswordAuthentication set to yes.



I have done these things after researching different solutions on the internet but I can't seem to find a solution to my problem: I can't login to my openSUSE box from Windows via Putty. I can connect to a session but I get 'Access Denied' everytime I attempt a login.



edit* I can login via ssh on my linux box from my linux box using



ssh openSUSEcomputername -p 2223









share|improve this question















I have a fresh install of openSUSE (tumbleweed) that I am trying to access via ssh from my Windows 7 box on my local home network. I can ping the boxes from each other successfully. I have edited the /etc/ssh/sshd_config file on the openSUSE box and changed the port to 2223. I have added the line AllowUsers (mylogin) to ssh_config. PermitRootLogin is set to no. PasswordAuthentication is set to yes. I generated a public key on my windows machine and copied it to the openSUSE machine via a flash drive and added it to my .ssh/authorized_keys, but my understanding is this shouldn't be needed if I have PasswordAuthentication set to yes.



I have done these things after researching different solutions on the internet but I can't seem to find a solution to my problem: I can't login to my openSUSE box from Windows via Putty. I can connect to a session but I get 'Access Denied' everytime I attempt a login.



edit* I can login via ssh on my linux box from my linux box using



ssh openSUSEcomputername -p 2223






linux ssh windows opensuse putty






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 7 at 23:47









Rui F Ribeiro

38.7k1479128




38.7k1479128










asked Aug 22 '16 at 21:11









doval

1614




1614











  • Firewall/Apparmor problem? and/or windows firewall problem?
    – mdpc
    Aug 22 '16 at 21:18











  • Is something like iptables enabled by default while installing suse ?
    – MelBurslan
    Aug 22 '16 at 21:19










  • from windows, open up a command prompt and try running telnet suselinuxservername 2223 what do you see ?
    – MelBurslan
    Aug 22 '16 at 21:20











  • @MelBurslan the response to telnet is a blank screen that says SSH-2.0-OpenSSH_7.2 and has a blinking cursor on the next line. If I don't type anything I get Connection to host lost after a couple minutes.
    – doval
    Aug 22 '16 at 21:32











  • Then you don't have a firewall problem. Try shutting down sshd and starting in debug mode for one single instance with sshd -p 2223 -D -ddd -e and try logging in from your windows machine, while watching the log screen on your linux box. It may give you the indication why it is giving access denied message.
    – MelBurslan
    Aug 22 '16 at 22:50
















  • Firewall/Apparmor problem? and/or windows firewall problem?
    – mdpc
    Aug 22 '16 at 21:18











  • Is something like iptables enabled by default while installing suse ?
    – MelBurslan
    Aug 22 '16 at 21:19










  • from windows, open up a command prompt and try running telnet suselinuxservername 2223 what do you see ?
    – MelBurslan
    Aug 22 '16 at 21:20











  • @MelBurslan the response to telnet is a blank screen that says SSH-2.0-OpenSSH_7.2 and has a blinking cursor on the next line. If I don't type anything I get Connection to host lost after a couple minutes.
    – doval
    Aug 22 '16 at 21:32











  • Then you don't have a firewall problem. Try shutting down sshd and starting in debug mode for one single instance with sshd -p 2223 -D -ddd -e and try logging in from your windows machine, while watching the log screen on your linux box. It may give you the indication why it is giving access denied message.
    – MelBurslan
    Aug 22 '16 at 22:50















Firewall/Apparmor problem? and/or windows firewall problem?
– mdpc
Aug 22 '16 at 21:18





Firewall/Apparmor problem? and/or windows firewall problem?
– mdpc
Aug 22 '16 at 21:18













Is something like iptables enabled by default while installing suse ?
– MelBurslan
Aug 22 '16 at 21:19




Is something like iptables enabled by default while installing suse ?
– MelBurslan
Aug 22 '16 at 21:19












from windows, open up a command prompt and try running telnet suselinuxservername 2223 what do you see ?
– MelBurslan
Aug 22 '16 at 21:20





from windows, open up a command prompt and try running telnet suselinuxservername 2223 what do you see ?
– MelBurslan
Aug 22 '16 at 21:20













@MelBurslan the response to telnet is a blank screen that says SSH-2.0-OpenSSH_7.2 and has a blinking cursor on the next line. If I don't type anything I get Connection to host lost after a couple minutes.
– doval
Aug 22 '16 at 21:32





@MelBurslan the response to telnet is a blank screen that says SSH-2.0-OpenSSH_7.2 and has a blinking cursor on the next line. If I don't type anything I get Connection to host lost after a couple minutes.
– doval
Aug 22 '16 at 21:32













Then you don't have a firewall problem. Try shutting down sshd and starting in debug mode for one single instance with sshd -p 2223 -D -ddd -e and try logging in from your windows machine, while watching the log screen on your linux box. It may give you the indication why it is giving access denied message.
– MelBurslan
Aug 22 '16 at 22:50




Then you don't have a firewall problem. Try shutting down sshd and starting in debug mode for one single instance with sshd -p 2223 -D -ddd -e and try logging in from your windows machine, while watching the log screen on your linux box. It may give you the indication why it is giving access denied message.
– MelBurslan
Aug 22 '16 at 22:50










1 Answer
1






active

oldest

votes

















up vote
1
down vote













ugh I knew it was something simple... when I was logging in i used (username)@(servername). after disabling UsePAM and testing connection I found that the login attempt was automatically appending the servername to the end of the login I entered, giving the wrong login. i logged in using just the username and was successful. renabled UsePAM parameter and was successful.. solved. thanks to all that responded!!






share|improve this answer




















    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',
    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
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f305129%2faccess-denied-ssh-from-windows-to-linux-via-putty%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








    up vote
    1
    down vote













    ugh I knew it was something simple... when I was logging in i used (username)@(servername). after disabling UsePAM and testing connection I found that the login attempt was automatically appending the servername to the end of the login I entered, giving the wrong login. i logged in using just the username and was successful. renabled UsePAM parameter and was successful.. solved. thanks to all that responded!!






    share|improve this answer
























      up vote
      1
      down vote













      ugh I knew it was something simple... when I was logging in i used (username)@(servername). after disabling UsePAM and testing connection I found that the login attempt was automatically appending the servername to the end of the login I entered, giving the wrong login. i logged in using just the username and was successful. renabled UsePAM parameter and was successful.. solved. thanks to all that responded!!






      share|improve this answer






















        up vote
        1
        down vote










        up vote
        1
        down vote









        ugh I knew it was something simple... when I was logging in i used (username)@(servername). after disabling UsePAM and testing connection I found that the login attempt was automatically appending the servername to the end of the login I entered, giving the wrong login. i logged in using just the username and was successful. renabled UsePAM parameter and was successful.. solved. thanks to all that responded!!






        share|improve this answer












        ugh I knew it was something simple... when I was logging in i used (username)@(servername). after disabling UsePAM and testing connection I found that the login attempt was automatically appending the servername to the end of the login I entered, giving the wrong login. i logged in using just the username and was successful. renabled UsePAM parameter and was successful.. solved. thanks to all that responded!!







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Aug 23 '16 at 6:40









        doval

        1614




        1614



























            draft saved

            draft discarded
















































            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f305129%2faccess-denied-ssh-from-windows-to-linux-via-putty%23new-answer', 'question_page');

            );

            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






            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?