LinuxQuestions.org - [SOLVED] puty control fails

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - puty control fails (https://www.linuxquestions.org/questions/linux-newbie-8/puty-control-fails-4175617655/)

puty control fails

Hi
I have given up on Debian and gone over to opensusse. I hope to install webmin there.
But my question is about putty, first off I was getting connection refused but now it just times out. Ive install ssh and configured it as far as I know on SusSE, the ip address is correct and I was previously able to ssh via putty into debian but not openSuSE any Ideas should I try opening ports in the firewall .....

Connecting from win10 to OpenSuSE Tplink-Archer vr2600 in operation.
--
Steve

Quote:

Originally Posted by oOBetaTestOo-Steve (Post 5780865)

Ive install ssh and configured it as far as I know on SusSE, the ip address is correct and I was previously able to ssh via putty into debian but not openSuSE

Would be nice to give us more details: how did you configure that?

Unless you have modified the configuration to use a different port, port 22 TCP must be open to inbound connections on your OpenSUSE host for that to work.

Hi
Getting an ifconfig pip[ed to a txt file is easy enough to prove how thew network or eth0 is st is no bother. But how to show how the firewall is set is different, I dont YET know how. As per everything else I assume port 22 is open inbound as ssh is indeed shown as installed.

eth0 Link encap:Ethernet HWaddr 00:18:FE:7A:86:FC
inet addr:192.168.2.104 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::218:feff:fe7a:86fc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:93 errors:0 dropped:0 overruns:0 frame:0
TX packets:92 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:9384 (9.1 Kb) TX bytes:14359 (14.0 Kb)
Interrupt:18

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Your advice further lady's and Jents

you gave almost no information, what you posted is more or less useless (=does not help to solve this issue).
Would be nice to tell us: 1. how did you configure sshd (at least what did you modify).
2. how did you try to log in exactly?
does ping/tracert work from windows to linux (with hostname/ip)?
Did you configure firewall at all?
Did you check if sshd really running? Did you check its log file too?
you can try to check with netstat and nmap too.

Quote:

Originally Posted by pan64 (Post 5780908)

you gave almost no information, what you posted is more or less useless (=does not help to solve this issue).
Would be nice to tell us: 1. how did you configure sshd (at least what did you modify).

Granted I gave little information I have been away from the keyboard all morning back at it now. I dont think I modified anything to do with ssh apart from install it.

Quote:

Originally Posted by pan64 (Post 5780908)

2. how did you try to log in exactly?

I load up putty and type in the ip address of the machine as I did with Debian and click open it worked in Debian but not in openSuSE

Quote:

Originally Posted by pan64 (Post 5780908)

does ping/tracert work from windows to linux (with hostname/ip)?

Yes that works out ping the ip 192.168.2.104 and it sent 4 lost o received 4

Quote:

Originally Posted by pan64 (Post 5780908)

Did you configure firewall at all?
Did you check if sshd really running? Did you check its log file too?
you can try to check with netstat and nmap too.

Away to see if ssh is running I have not changed the firewall yet either. thanks for the help Pan64

Reinstalled ssh
ran yast not yast2 went into settings firewall and allowed ssh.
Boom connected thanks to all for the help.
--
Steve