Difference between revisions of "SME Server talk:Documentation:Administration Manual:Chapter13"

From SME Server
Jump to navigationJump to search
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
This para under Hostnames and addresses needs to be changed to as shown [[Bugzilla: 6297]]
+
--[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 03:47, 15 August 2013 (MDT) adding a not box at the end
−
===Hostnames and addresses===
+
====Workgroup====
−
   
+
If you are using a computer on a local network and you wish to access the server via Windows file sharing, it is important that you are logged onto the same workgroup as your SME Server. This screen allows you to enter the name of the Windows workgroup the server should appear in. You should also enter the Windows server name. In order that you may later connect multiple locations using IPSEC VPNs, we suggest that you use a different name for each server. If you wish you can change the workgroup name to correspond with an existing workgroup.  
  
−
"Current Image" don't copy text this to wiki
+
[[Image:Workgroup.png]]
  
−
====Modify Hostname====
+
Macintosh users need only enter a server name or accept the defaults.
  
−
Using the Hostnames Panel. Suppose, for example, your company's web site was hosted at some other location, such as on your ISP's web servers. If you wanted "www.mycompany.xxx" to point to your ISP's server, you would modify the entry here by clicking the "Modify..." link next to "www". The image below shows the screen in which you would perform the task:
+
Also in this section, you can specify whether the server should be the domain master for your Windows workgroup. Most sites should choose "Yes" unless you are adding an server to an existing network which already has a domain master.
−
 
  
−
"Current Image" don't copy text this to wiki
+
{{Warning box|If you have a Windows NT server or Windows 2000 server on your network that is functioning as a network server, you should answer "no" as that other server will act as the domain master.}}
  
 +
If you do configure your system to be the domain master, a special Windows share called NETLOGON is created with a DOS batch file called netlogon.bat. This batch file is executed by Windows clients that have been configured to "Logon to domain". The netlogon.bat file we provide by default does very little, but advanced users can, if they wish, modify this script to set environment variables for their clients or provide automatic drive mappings.
  
−
You would first change the location to "Remote" and then enter the IP address or Fully Qualified Domain Name (FQDN) of your ISP's server in the field marked "IP Address or FQDN".
+
As the NETLOGON share is only writable by the "admin" user, you modify the netlogon.bat script by logging on to a Windows system as "admin", connecting to the share and then modifying the script using a Windows text editor. Be aware that the NETLOGON share will not be visible in Network Neighborhood or other similar tools. As the "admin" user, you will need to connect to the share or map a drive to it, by using the specific path:
 +
\\ servername \NETLOGON\
  
−
====Creating New Hostnames====
+
The sample file contains a few examples of setting the system time for each machine and also for mapping a common drive for all Windows client.
−
 
−
Creating new hostnames simply involves selecting one of the links at the top of the Hostnames and addresses panel and filling out the appropriate fields.
 
−
 
−
Note that if your system is configured with any virtual domains, you will have the choice of the domain in which you want to create the hostname. This allows you, for instance, to have "www.tofu-dog.com" pointing to one IP address and "www.mycompany.xxx" pointing to a completely separate IP address.
 
−
 
−
The hostnames you can create on this panel fall into three categories and are available from the drop box "Location":
 
  
−
Self: Additional names for your server: For instance, you might want to set up "intranet.mycompany.xxx" to point to your server. All you do here is enter the hostname and, if appropriate, choose the domain for the hostname.
+
{{Note box|You can see the [[SME_Server:Documentation:Administration_Manual:Chapter7#Setting_up_network_drives|chapter 7]] if you want a manual method to modify the netlogon.bat}}
−
+
----
−
Remote: As mentioned in the example earlier, you might want to point a hostname such as "www" to a remote system. While "www" is created by default, you can create other names such as "home", "research", or any other appropriate name. In the form, you simply enter the hostname, choose the domain, and enter the remote IP address or FQDN.
 
−
 
−
Local: This screen is a bit more complicated because you have more options. At a basic level, you can create a hostname in a domain that points to another computer on your local network. To do this, just type in the hostname and enter the IP address in the "Local IP" field. For instance, you might want "research" to point to a computer system inside your network.
 
−
 
−
Where this gets complicated is when you want "research.mycompany.xxx" to be accessible both inside and outside your local network. The challenge is that your local IP addresses are only accessible inside your network. For that reason, the target computer system will need to have two network interface cards - one connected to the internal network and one connected to the external network.
 
  
−
{{Note box|At this stage, one cannot create a Hostname under local using a FQDN. However, it is possible to point to a local machine entering the FQDN of this machine as "remote" if this FQDN is valid.}}
 
  
−
 
−
http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter13#E-mail
 
  
−
This chapter needs some brief explanatory text about the ssmtp section.
 
  
−
[[User:RayMitchell|RayMitchell]] 15:08, 25 March 2008 (MDT)
+
--[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 03:51, 15 August 2013 (MDT) addind some a tip box at the end to explain a bit more why you should have a smtp relay for your sme server
 +
=====E-mail Delivery=====
 +
This screen presents you with additional options for controlling how your system handles e-mail.
 +
 
 +
[[Image:Email-delivery.png]]
 +
 
 +
* Forwarding address for administrative notices: The default address for administrative notices (i.e. undeliverable mail, backup notifications and other status/error messages) is "admin". If you'd like those messages to be sent elsewhere, then you have to use the menu Collaboration > User panel > admin and fill the field "Forwarding address" in the admin menu.
 +
 
 +
{{Note box|Be aware that all messages sent to postmaster, root or mailer-daemon at your domain are sent to either admin or the address that you enter in this field.}}
 +
 
 +
* E-mail to unknown users: This field allows you to choose whether incoming messages to unknown users are bounced back to the sender or forwarded to the system administrator. Some users prefer the latter setting because it allows them to catch and reroute e-mail that was incorrectly addressed.
 +
 
 +
{{Note box|If you choose to have messages forwarded to the system administrator, they will be sent to either "admin" or the e-mail address specified in the forwarding address field mentioned above.}}
 +
 
 +
* Internet provider's SMTP server: Normally the server will send outgoing messages directly to their intended destination. If, however, you have an unreliable connection or are using a residential Internet service, it may be advisable to route e-mail via your provider's SMTP server. In that case, you should enter the SMTP server's hostname or IP address here.
 +
 
 +
{{Tip box|In fact, if you have a temporary dial-up connection to the Internet or dynamic IP, you may find that you need to use your ISP's mail server in order to deliver mail to some locations. '''As a reaction to the huge volume of unsolicited commercial e-mail ("spam")''', many Internet sites are refusing direct SMTP connections from IP addresses that are known to be temporary dial-up accounts or  dynamic IP. '''For this reason, you may need to use your ISP's mail server since it will have a permanent connection to the Internet.}}'''

Latest revision as of 10:51, 15 August 2013

--Stephdl (talk) 03:47, 15 August 2013 (MDT) adding a not box at the end

Workgroup

If you are using a computer on a local network and you wish to access the server via Windows file sharing, it is important that you are logged onto the same workgroup as your SME Server. This screen allows you to enter the name of the Windows workgroup the server should appear in. You should also enter the Windows server name. In order that you may later connect multiple locations using IPSEC VPNs, we suggest that you use a different name for each server. If you wish you can change the workgroup name to correspond with an existing workgroup.

Workgroup.png

Macintosh users need only enter a server name or accept the defaults.

Also in this section, you can specify whether the server should be the domain master for your Windows workgroup. Most sites should choose "Yes" unless you are adding an server to an existing network which already has a domain master.


Warning.png Warning:
If you have a Windows NT server or Windows 2000 server on your network that is functioning as a network server, you should answer "no" as that other server will act as the domain master.


If you do configure your system to be the domain master, a special Windows share called NETLOGON is created with a DOS batch file called netlogon.bat. This batch file is executed by Windows clients that have been configured to "Logon to domain". The netlogon.bat file we provide by default does very little, but advanced users can, if they wish, modify this script to set environment variables for their clients or provide automatic drive mappings.

As the NETLOGON share is only writable by the "admin" user, you modify the netlogon.bat script by logging on to a Windows system as "admin", connecting to the share and then modifying the script using a Windows text editor. Be aware that the NETLOGON share will not be visible in Network Neighborhood or other similar tools. As the "admin" user, you will need to connect to the share or map a drive to it, by using the specific path: \\ servername \NETLOGON\

The sample file contains a few examples of setting the system time for each machine and also for mapping a common drive for all Windows client.


Important.png Note:
You can see the chapter 7 if you want a manual method to modify the netlogon.bat




--Stephdl (talk) 03:51, 15 August 2013 (MDT) addind some a tip box at the end to explain a bit more why you should have a smtp relay for your sme server

E-mail Delivery

This screen presents you with additional options for controlling how your system handles e-mail.

Email-delivery.png

  • Forwarding address for administrative notices: The default address for administrative notices (i.e. undeliverable mail, backup notifications and other status/error messages) is "admin". If you'd like those messages to be sent elsewhere, then you have to use the menu Collaboration > User panel > admin and fill the field "Forwarding address" in the admin menu.


Important.png Note:
Be aware that all messages sent to postmaster, root or mailer-daemon at your domain are sent to either admin or the address that you enter in this field.


  • E-mail to unknown users: This field allows you to choose whether incoming messages to unknown users are bounced back to the sender or forwarded to the system administrator. Some users prefer the latter setting because it allows them to catch and reroute e-mail that was incorrectly addressed.


Important.png Note:
If you choose to have messages forwarded to the system administrator, they will be sent to either "admin" or the e-mail address specified in the forwarding address field mentioned above.


  • Internet provider's SMTP server: Normally the server will send outgoing messages directly to their intended destination. If, however, you have an unreliable connection or are using a residential Internet service, it may be advisable to route e-mail via your provider's SMTP server. In that case, you should enter the SMTP server's hostname or IP address here.


Information.png Tip:
In fact, if you have a temporary dial-up connection to the Internet or dynamic IP, you may find that you need to use your ISP's mail server in order to deliver mail to some locations. As a reaction to the huge volume of unsolicited commercial e-mail ("spam"), many Internet sites are refusing direct SMTP connections from IP addresses that are known to be temporary dial-up accounts or dynamic IP. For this reason, you may need to use your ISP's mail server since it will have a permanent connection to the Internet.


Retrieved from "https://wiki.koozali.org/index.php?title=SME_Server_talk:Documentation:Administration_Manual:Chapter13&oldid=21182"