Skip to main content
20 events
when toggle format what by license comment
Dec 7, 2018 at 23:47 history edited Rui F Ribeiro CC BY-SA 4.0
deleted 213 characters in body
Aug 23, 2016 at 6:40 answer added doval timeline score: 1
Aug 23, 2016 at 6:40 comment added doval ugh I knew it was something simple... when I was logging in i used (username)@(servername). after disabling PAM 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!!
Aug 23, 2016 at 4:02 comment added Rui F Ribeiro It is the latest putty version?
Aug 23, 2016 at 3:40 comment added doval @MelBurslan forgot to tag you on that last update
Aug 23, 2016 at 3:36 comment added doval I researched the pam configuration file a bit, i don't know how to post the info in a comment. I also checked /etc/passwd and /etc/shadow and the user exists in those files, I don't know if other information is missing or not as I don't have experience with these files.
Aug 23, 2016 at 3:35 comment added doval @steeldriver I put the AllowUsers line in /etc/ssh/sshd_config. I just verified that, was a typo in the post. I tried logging in before I added that line with the same results. I added that line to see if it would resolve my issue, but it didn't.
Aug 23, 2016 at 2:46 comment added steeldriver Where exactly did you put the AllowUsers line? Your text says in ssh_config (client side) but AFAIK it is only valid in sshd_config (server side). In either case, have you tried removing or commenting that out, at least until you get a basic connection working?
Aug 22, 2016 at 23:40 comment added doval found another entriy.. 'PAM: User not known to the underlying authentication module for illegal user (me)@(computer) from (Ip address)'
Aug 22, 2016 at 23:26 comment added doval I stopped the service and started it with those parameters. I attempted a connection. The login failed and the entry in the sshd output that stood out was 'Failed keyboard-interactive/pam for invalid user (me)@(computer) from (ipaddress) port (port) ssh2'
Aug 22, 2016 at 23:04 comment added MelBurslan find the location of your ssh executable. Probably it will be something like /usr/sbin/sshd and replace sshd portion of the command above with that absolute path
Aug 22, 2016 at 22:59 comment added doval @MelBurslan I tried that command and I get the response 'sshd re-exec requires execution with an absolute path'. I am not sure what that means. I looked it up and I didn't find an answer that makes sense to me. Can you elaborate on what I'm not doing right or doing wrong?
Aug 22, 2016 at 22:50 comment added MelBurslan 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.
Aug 22, 2016 at 21:32 comment added doval @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.
Aug 22, 2016 at 21:20 comment added MelBurslan from windows, open up a command prompt and try running telnet suselinuxservername 2223 what do you see ?
Aug 22, 2016 at 21:19 comment added MelBurslan Is something like iptables enabled by default while installing suse ?
Aug 22, 2016 at 21:18 comment added mdpc Firewall/Apparmor problem? and/or windows firewall problem?
Aug 22, 2016 at 21:18 history edited doval CC BY-SA 3.0
added 110 characters in body
Aug 22, 2016 at 21:14 review First posts
Aug 22, 2016 at 21:22
Aug 22, 2016 at 21:11 history asked doval CC BY-SA 3.0