Hi! I'm a total FreeNAS noob, and I need help please.

[choochilla]

I stopped and restarted the service, but it was the same, so I rebooted the server and tried again, still no good.

I think I only have one account set up, but I'm not 100% sure. Is the root and admin account the same thing?

In the GUI there is the 'Admin Account' which is where the admin name and password was set up.
There are lots of built in users (under 'Users - View Users') but I did not do anything to those.
I have only done the initial setup, but when I got to the hard drive bit I had to stop there.

Maybe that's the problem?

 

[Whattteva]

Under Users page:
Look at your username (probably the one listed on the top).
Look at the columns that says "Disable password login" and "Lock user".
Make sure both of them are listed as "false".

Also, after getting your login denied, post the contents of /var/log/auth.log here.

 

[choochilla]

EDIT: Actually, I just remembered something else.
Post the contents of /var/log/auth.log here.

OK but how do I do that? Do I just type what you put into the 'Shell'
(similar to what I had to do with 'camcontrol devlist'?)
or do I have to access each folder in turn until I get to the auth.log file.

Please excuse my ignorance but I have never used FreeDBS, Linux or Unix before, so I don't know the procedures or the commands yet. Sorry.

 

[choochilla]

Under Users page:
Look at your username (probably the one listed on the top).
Look at the columns that says "Disable password login" and "Lock user".
Make sure both of them are listed as "false".

Yes the user is listed at the top of the list and the 'Disable password login' and the 'Lock user' boxes are both empty.

 

[Whattteva]

OK but how do I do that? Do I just type what you put into the 'Shell'
(similar to what I had to do with 'camcontrol devlist'?)
or do I have to access each folder in turn until I get to the auth.log file.

In the shell, you can type in:

Code:

cat /var/log/auth.log

If the output is too long that it scrolls the screen too fast, use:

Code:

cat /var/log/auth.log | more

This will allow you to scroll the screen using the arrow keys. Press "q" to get out of the scrolling mode and return to the normal shell mode.

Please excuse my ignorance but I have never used FreeDBS, Linux or Unix before, so I don't know the procedures or the commands yet. Sorry.

Nothing wrong with that. That's why we're here to help :).

 

[choochilla]

Thanks for your understanding, you guys are great!
I typed it in exactly as you suggested but the message it shows is 'cat: /var/log/auth.log: Permission denied'
Have I done something wrong?

 

[Whattteva]

That's strange, are you doing this from the Shell prompt in the web GUI?
You should not get a permission error as you're automatically logged in there as root.

 

[choochilla]

That's strange, are you doing this from the Shell prompt in the web GUI?
You should not get a permission error as you're automatically logged in there as root.

No - sorry, forgot to mention - the PuTTY program started working after I visited the Users page to check for the state of the 'Disable password login' and the 'Lock user' boxes.
The message was as it appears in the PuTTY interface.

Typing directly into the shell at the server itself I get a long list of stuff, far too much to type in (which is why I keep trying with PuTTY, so I can cut and paste it).
Typing it into the web GUI is the same, but how do I paste the results into a 'code' box for you to see it please?

Think I've found out - here goes -

Code:

[root@freenas ~]# cat /var/log/auth.log                                       
Sep 30 10:29:13 freenas newsyslog[1462]: logfile first created                 
Sep 30 10:29:21 freenas sshd[2151]: Server listening on :: port 22.           
Sep 30 10:29:21 freenas sshd[2151]: Server listening on 0.0.0.0 port 22.       
Sep 30 10:48:19 freenas sshd[2151]: Received SIGHUP; restarting.               
Sep 30 10:48:19 freenas sshd[3173]: Server listening on :: port 22.           
Sep 30 10:48:19 freenas sshd[3173]: Server listening on 0.0.0.0 port 22.       
Sep 30 10:48:28 freenas sshd[3173]: Received signal 15; terminating.           
Sep 30 10:48:32 freenas sshd[3622]: Server listening on :: port 22.           
Sep 30 10:48:32 freenas sshd[3622]: Server listening on 0.0.0.0 port 22.       
Sep 30 10:48:51 freenas sshd[3627]: Invalid user idi_admin from 192.168.1.37   
Sep 30 10:48:51 freenas sshd[3627]: input_userauth_request: invalid user idi_adm
in [preauth]                                                                   
Sep 30 10:48:57 freenas sshd[3627]: Failed password for invalid user idi_admin f
rom 192.168.1.37 port 50871 ssh2                                               
Sep 30 10:49:04 freenas sshd[3627]: Connection closed by 192.168.1.37 [preauth]
Sep 30 11:01:01 freenas sshd[4031]: Invalid user idi_admin from 192.168.1.37   
Sep 30 11:01:01 freenas sshd[4031]: input_userauth_request: invalid user idi_adm
in [preauth]                                                                   
Sep 30 11:01:07 freenas sshd[4031]: Failed password for invalid user idi_admin f
rom 192.168.1.37 port 50902 ssh2                                               
Sep 30 11:01:15 freenas sshd[4031]: Connection closed by 192.168.1.37 [preauth]
Sep 30 11:11:13 freenas sshd[4853]: Accepted password for idi_admin from 192.168
.1.37 port 50963 ssh2                                                         
[root@freenas ~]#        

Did it work? Can you see it?

 

[Whattteva]

Looks like it recorded 2 failed attempts and a successful attempt at the end.
I'm guessing that last success was when you logged in with PuTTY after you visited the Users page on the web GUI.

Well, since it worked, that should resolve your PuTTY issue, correct?

 

[choochilla]

Yes PuTTY now seems to be able to communicate with the server and is working correctly - thank you so much!
I couldn't have done it without you.

 

[choochilla]

Well it's almost 12:30 here in the UK so I'll be away from my home computer for the rest of the day. I'll maybe try something else tomorrow. Thanks again.