2,569
edits
Changes
Jump to navigation
Jump to search
mLine 80:
Line 80: − − − (comments) − ====Appendix F. Quick Start Guide==== − =====Installation===== − * Select a PC to dedicate as a server, minimum 450mhz 128mb ram, but double this is better, and plug into your network. See|Chapter 4 for details about selectng server hardware. − * Insert the SMEserver CD and reboot, answer the initial questions to install the software, then answer the questions from the install wizard to suit your circumstances. See|Chapter 5.4 for more details. − * Restart a Client PC after the server has finished, this allows the client to pickup a new DHCP address. Further configure your server with a browser at yourservername/server-manager, see next section. − − =====Access===== − '''Server-manager''' (See|Chapter 8) − * The server manager is a series of web forms called panels that enable a client PC to configure the server. Access to the server-manager is via a browser using one of the following addresses: − http://servername/server-manager − http://server.domain/server-manager − http://serverIPaddress/server-manager − User is Admin, with the server Admin password − − '''Command Line''' (See|Chapter 6.2) − * Local access. − Keep a monitor attached to the server and press [alt]-[f2] to access a login prompt. − * Remote access. − Preferably the server is placed in an out of the way location and it's monitor is removed. − Access to the command line is obtained with a ssh client (Secure SHell). We reccommend using a free windows client --suhc-- such as putty or terratermSSH. − Before you can access the server with ssh you need to allow it at server-manager >> remote access − Secure shell access: Private OR Public − Allow administrative command line access over secure shell: Yes − Allow secure shell access using standard passwords : Yes − * Admin or Root? − When you ssh to the server or use it's own monitor and keyboard − login as root to access the command line − or − login as admin to access the console wizard. − − =====Configuration===== − '''Windows LAN (Local Area Network)''' − * Further configuration if the SMEserver will be your file server on you local LAN. − * All windows PC's on a LAN need to be in the same workgroup (see chapter 13.2). − * Set the server to be in the local workgroup via the server-manager >> workgroup. − * Also in the workgroup panel set your server to be the domain controller, this lets the server create one set of users for authorisation. − * Add users via the server-manager >> user accounts panel and set a password for them (see chapter 9.1 Users). − * Add a network drive via the server-manager >> information bay (see chapter 14) − * You may need to logoff and logon again to access these new resources, you should see the network drive and a personal drive for the user in your network neighbourhood. − * To map these drives either use windows explorer >> tools >> map network drive − select a letter then enter \\servername\homes or \\server\ibayname − Or − configure your client to use netlogon.bat, and edit /home/e-smith/files/samba/netlogon/netlogon.bat − * you must use a dos editor, one way to do this is copy or link to a windows visable area, chown yourUserName netlogon.bat, make your changes, then copy back − * If you use the "Home" version of Windows XP, it can't use the servers netlogon.bat, you can use it by placing a copy in your PC's startup folder.
SME Server:Documentation:Administration Manual:Appendix (view source)
Revision as of 15:20, 17 February 2007
, 15:20, 17 February 2007→SME Manual Appendix
VPN
VPN
Virtual Private Network (see PPTP)
Virtual Private Network (see PPTP)