other problem want to help

[last night]

sorry this is second topic i complain

i reboot my server "box" but when i try to long in by secureCRT or putty
told me “ verify that user name and password are correct “
i can login from the box "server" locally,but can't remotely login form another machine
also when I checked the sshd_config, I could see remote user login is permitted


thank you

[BjornR1989]

NEVER log in as root, it's a security risk !
Log in as a regular user, then use sudo.

If you try to connect and any SSH client such as Putty tells you the login is wrong, it just is.
If you aren't asked to provide logon details, then open port 22 on your firewall.

[last night]

(07-06-2010, 07:18 PM)BjornR1989 Wrote:  NEVER log in as root, it's a security risk !
Log in as a regular user, then use sudo.

If you try to connect and any SSH client such as Putty tells you the login is wrong, it just is.
If you aren't asked to provide logon details, then open port 22 on your firewall.

thank you for help , so if i open ports 22 everything gonna be fine ?

let me test and give to you update

please could you tell me what's sudo ?

---

the problem not from port 22 is already open

---

the problem is not from port 22 i'ts already open

[BjornR1989]

There are some things that need to be in order.
- Running a correctly configured ssh daemon
The code below can be used on a Fedora system to check whether the daemon is running:

Code:

service sshd status

It might return something like this

Code:

[root@DDBS-2U1 ~]# service sshd status
openssh-daemon (pid  1530) is running...

- Port 22 (or whatever port sshd is listening on) needs to be open and accepting packets.

This is what i get when i check what is active on port 22:

Code:

[root@DDBS-2U1 ~]# lsof -i :22
COMMAND  PID  USER   FD   TYPE   DEVICE SIZE/OFF NODE NAME
sshd    1530  root    3u  IPv4    13221      0t0  TCP *:ssh (LISTEN)
sshd    1548  root    3r  IPv4 11099536      0t0  TCP DDBS-2U1.auto.intranet.ddbs.net:ssh->DDBS-ATX1.auto.intranet.ddbs.net:49705 (ESTABLISHED)
sshd    1552 bjorn    3u  IPv4 11099536      0t0  TCP DDBS-2U1.auto.intranet.ddbs.net:ssh->DDBS-ATX1.auto.intranet.ddbs.net:49705 (ESTABLISHED)

- SELinux must not interfere with this remote access, by default it doesn't.

From Wikipedia:
The sudo command is a program for some Unix and Unix-like computer operating systems that allows users to run programs with the security privileges of another user (normally the superuser, or root). It is an abbreviation for "super user do" (as in, do a command with another user's privileges). By default, sudo will prompt for a user password but it may be configured to require the root password, or require it only once per pseudo terminal, or no password at all. Sudo is able to log each command run and in some cases has completely supplanted the superuser login for administrative tasks, most notably in Ubuntu Linux and Apple's Mac OS X.

More info on http://en.wikipedia.org/wiki/Sudo