That looks like you cant ssh to the server, log on to your server console and open
a terminal, run command 'ssh 270.0.0.1',to verify that the sshd is locally working
as expected.

Then from a client verify that you can connect to the server using ssh (putty.exe if
windows client) to iron out if its a firewall issue or not, if first test passed and
this test fails, a firewall is probably preventing access to port 22.

/Henrik

Hi Henrik,

When I run the command "ssh 270.0.0.1" , it shows that "name or service not known", what is the problem?

Thanks.

Oh, hold on a sec now, 270.0.0.1 is an invalid ip address, please make sure that
you have your network configuration setup correctly.


Regards,

Henrik Andersson

Hi Henrik,

You mean I should change the server "270.0.0.1" to my own IP address here? How to update and modify? Sorry, I am very new to this product.

Thanks.

Hi,

Yes, you should use ofcourse use your own ip addresses, you mentioned 270.0.0.1 in an earlier post and
i overlooked the fact that its just an invalid address in my answers back to you...

I'm not sure what you mean by how to update/modify ?

Do the tests i mentioned using the right server ipaddress to get further.

Regards,

Henrik Andersson

Hi Henrik,

Sorry for the mistake, it's "127.0.0.1".

When I key in "ssh 127.0.0.1" at the master workstation, it says" permission denied, pls try again", is it a password problem? How to change my password there?

If the server is not open, I can not connect at the client side. Pls help.

Thanks a lot.

Hi,

127.0.0.1 is localhost so you should try that on your server side. In order to be able to ssh into your server you need the openssh-server package and dependencies installed. Run the following and post output please:
if the openssh-server package is in the list, then the server package is installed. Next run:
as root or with sudo. If the sshd daemon reports running, then you need to check your firewall, if active with:
and if the daemon is listening with:
as root. If all this reports positive then your sshd_config should be checked. If any of the above checks out as negative then take it from there. When in doubt, post output of the commands.

Kind regards,

Eric

Hi Eric,
Thanks for the reply.
This is what I get from my workstation.
Rpm –qa / grep ssh: grep – 2.5.1-55.el5
Chkconfig –list sshd: sshd 0: off, 1ff, 2: on, 3: on, 4: on, 5: on, 6: off
Service sshd status: openssh-daemon (pid 4059) is running.

I couldn't use my laptop to access the main station, what I should put there?
server:??
user: admin
password: xxxxxx.

Thanks.

when I key in "netstat -tnlp", this is what I get:

Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:2208 0.0.0.0:* LISTEN 4039/hpiod
tcp 0 0 0.0.0.0:5989 0.0.0.0:* LISTEN 4739/cimserver
tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN 16867/python-thinli
tcp 0 0 0.0.0.0:904 0.0.0.0:* LISTEN 16736/python-thinli
tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 6238/vncserver-x11-
tcp 0 0 0.0.0.0:43501 0.0.0.0:* LISTEN 4024/socbu
tcp 0 0 0.0.0.0:9999 0.0.0.0:* LISTEN 10225/xoc_session_m
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 3716/portmap
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 4151/httpd
tcp 0 0 0.0.0.0:977 0.0.0.0:* LISTEN 3763/rpc.statd
tcp 0 0 0.0.0.0:1010 0.0.0.0:* LISTEN 16828/tlstunnel
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 4059/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 16629/cupsd
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN 4084/xinetd
tcp 0 0 0.0.0.0:27000 0.0.0.0:* LISTEN 4022/lmgrd
tcp 0 0 10.36.50.90:2809 0.0.0.0:* LISTEN 11115/Naming_Servic
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 4117/sendmail: acce
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 4151/httpd
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 4151/httpd
tcp 0 0 127.0.0.1:2207 0.0.0.0:* LISTEN 4044/python

Hi,

Sorry for the late reply but the latest time I'm swamped in work. Do you by any change have iptables running which might be blocking access? Run:
as root or with sudo and post output. And are you sure the user 'admin' is a valid user account on the server? Run on the server:
Kind regards,

Eric

Hi Eric，

When I run "iptables -L", I get so many information comes out, I am not sure which one I should focus on.

When I key in "id admin", it shows no such user, but when I installed " thinlinc" last time, it says user is "admin", so what I should do now? Change to another user? or find out the valid user account in the workstation? what code I should run?

Thanks.

This is what I get for "iptables -L":

Chain INPUT (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhere

Chain FORWARD (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain RH-Firewall-1-INPUT (2 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere icmp any
ACCEPT esp -- anywhere anywhere
ACCEPT ah -- anywhere anywhere
ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns
ACCEPT udp -- anywhere anywhere udp dpt:ipp
ACCEPT tcp -- anywhere anywhere tcp dpt:ipp
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:5900
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:5901
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:5902
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:5903
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:5904
REJECT all -- anywhere anywhere reject-with icmp-host-prohibited

Hi, again...

It says that the ThinLinc web adminsistration page username is admin, ThinLinc authenticates users
using PAM and in your case this is just local users of your ThinLinc server.


Kind Regards,

Henrik Andersson

Hi Henrik,

How to see my thinlinc server name in my workstation?

Thanks.

Hi,

The ThinLinc server name used in the client is the FQDN or ip address of your machine that
runs the ThinLinc server, by the look of the result from 'nestat -tnlp' in previous posts
it might be the address 10.36.50.90.


Regards,

Henrik