653
edits
Changes
Jump to navigation
Jump to search
mLine 9:
Line 9: − + + + + − + + + Line 26:
Line 31: − + − + − + − This is the preferred method of connecting to SME, as you can connect from any machine with an SSH Client. SSH is similar in function to Telnet, with the main difference being that it is heavily encrypted. It has many other very useful features, such as tunneling, which are outside the scope of this section of the manual. − − Before a user can have shell access Admin must: − * enable ssh access at server-manager -> Security -> Remote Access − − chsh -s /bin/bash jim − − ====SSH With Passwords==== − ====Securing SSH With Public / Private Keys====+ − Line 51:
Line 47: + + + + + + + +
SME Server:Documentation:User Manual:Chapter1 (view source)
Revision as of 19:05, 30 June 2021
, 19:05, 30 June 2021→VPN Access
Users can reset their passwords at <b>www.yourserver.net/user-password</b>
Users can reset their passwords at <b>www.yourserver.net/user-password</b>
For windows clients, If the server is the domain PDC the user can reset his password after issuing a Ctrl+Alt+Del, Note that windows error messages may not explain clearly enough that the user password isn't sufficiently complex.
For windows clients, If the server is the domain PDC the user can reset his password after issuing a Ctrl+Alt+Del, Note that windows error messages may not explain clearly enough that the user password isn't [[SME_Server:Documentation:Administration_Manual:Chapter9#Changing_User_Passwords|sufficiently complex]].
====Admin/root passwords====
Unlike user passwords, the admin/root passwords can not be set via <b>www.yourserver.net/user-password</b>, nor can they be set on a windows client via Ctrl+Alt+Del. Admin/root passwords must be set via the server manager or via the console commands ''passwd'', either on the console directly or via SSH.
===VPN Access===
===VPN Access===
To configure VPN access the administrator must
{{WIP box}}
{{warning box|PPTP is UNSAFE and has been DEPRECATED. This section is in the process of being rewritten. Use VPN (qv) instead of PPTP}}
<!--To configure VPN access the administrator must
[[:SME_Server:Documentation:Administration_Manual:Chapter11#PPTP_.28VPN.29 | configure PPTP.]]
[[:SME_Server:Documentation:Administration_Manual:Chapter11#PPTP_.28VPN.29 | configure PPTP.]]
* When you then open up your Network Neighborhood window, you should see your server workgroup listed there. Alternatively, map a drive as required like:
* When you then open up your Network Neighborhood window, you should see your server workgroup listed there. Alternatively, map a drive as required like:
net use M: \\192.168.1.1\ibayname
net use M: \\192.168.1.1\ibayname -->
{{DrawBoxNote|content= When setting up VPN make sure your subnet is not the same as your VPN, for example your location "home" has a subnet of 192.168.1.0 and your "office" is 192.168.1.0 will not allow you to VPN, you will either need to change your "home" subnet to be different or set up your server to be a unique subnet.}}
{{Note box|When setting up VPN make sure your subnet is not the same as your VPN, for example your location "home" has a subnet of 192.168.1.0 and your "office" is 192.168.1.0 will not allow you to VPN, you will either need to change your "home" subnet to be different or set up your server to be a unique subnet.}}
===Shell Access===
===Shell Access===
* '''Password access'''
* then grant each user shell access:
If your admin allows it you can connect with just a username and password.
If your admin allows it you can connect with just a username and password.
* '''SSH Keys access'''
If you need to get SSH access to your server from outside the LAN (e.g. you want to get to your work server from home) then the advised method is to use Public / Private Keys.
If you need to get SSH access to your server from outside the LAN (e.g. you want to get to your work server from home) then the advised method is to use Public / Private Keys.
When you have SSH Keys working, the server Admin can disable logging in using passwords.
When you have SSH Keys working, the server Admin can disable logging in using passwords.
* Improve user remote shell cosmetics
Create a .bash_profile file for the user in ~
# include .bashrc if it exists
if [ -f ~/.bashrc ]; then
source ~/.bashrc
fi