OPC oota
2009-Jul-23 06:33 UTC
[Samba] TOSHAG-WindowsClientConfig.xml translate finished and some bug and typo(?) found
Now, TOSHARG-WindowsClientConfig.xml translate to Japanese finished(3.4.0 base).
And some bug and typo(?) found.
-------------------------------------------------------------------------------------------------
<indexterm><primary>network
difficulty</primary></indexterm>
<indexterm><primary>network client</primary></indexterm>
<indexterm><primary>client client
instructions</primary></indexterm>
------- duplicate?
Occasionally network administrators report difficulty getting Microsoft Windows
clients to interoperate
correctly with Samba servers. It seems that some folks just cannot accept the
fact that the right way
Many network administrators will want to use DHCP to
configure all client TCP/IP
protocol stack settings. (For information on how to
configure the ISC DHCP server
for Windows client support see <link
linkend="DHCP">the DNS and DHCP Configuration Guide</link>,
<link linkend="DHCP">DHCP
Server</link>.
_ forget )
</para>
The example system uses manually configured DNS
settings. When finished making changes, click the
<guibutton>OK</guibutton> to commit the
settings. See <link linkend="WXPP014"/>.
<figure id="WXPP014"> <title>DNS
Configuration.</title> <imagefile>WXPP014</imagefile>
</figure>
_
needless?
</para></step>
<figure id="w2kp001"><title>Local
Area Connection
Properties.</title><imagefile>w2kp001</imagefile></figure>
_needless?
</para></step>
<step><para>
<indexterm><primary>Local Area Connection
Properties</primary></indexterm>
<indexterm><primary>TCP/IP</primary></indexterm>
<indexterm><primary>DNS</primary></indexterm>
<indexterm><primary>ISC DHCP
server</primary></indexterm>
Many network administrators will want to use DHCP to
configure all client TCP/IP
protocol stack settings. (For information on how to
configure the ISC DHCP server
for Windows client support see <link
linkend="DHCP">the DNS and DHCP Configuration Guide<
/link>,
------------------------------------------------------------------duplicate?
<link linkend="DHCP">DHCP
Server</link>.
</para>
The default setting is DHCP-enabled operation
(i.e., <quote>Obtain an IP address
automatically</quote>). See <link linkend="w2kp002"/>.
<figure
id="w2kp002"><title>Internet Protocol (TCP/IP)
Properties.</title><imagefile>w2kp002</imagefile></figure>
_neadless?
</para>
<step><para>
Click the <guimenu>Advanced</guimenu> button
to proceed with TCP/IP configuration.
Refer to <link
linkend="w2kp003"></link>.
<figure
id="w2kp003"><title>Advanced Network
Settings.</title><imagefile>w2kp003</imagefile></figure>
_neadless?
</para>
<figure id="w2kp004"><title>DNS
Configuration.</title><imagefile>w2kp004</imagefile></figure>
_neadless?
</para></step>
See <link
linkend="w2kp005"></link>.
<figure id="w2kp005">
<title>WINS
Configuration.</title><imagefile>w2kp005</imagefile>
_neadless?
</figure>
See <link
linkend="WME001"></link>.
<figure id="WME001">
<title>The Windows Me Network
Configuration Panel.</title>
_neadless?
<imagefile>WME001</imagefile>
<indexterm><primary>DHCP</primary></indexterm>
<indexterm><primary>TCP/IP</primary></indexterm>
<indexterm><primary>ISC DHCP
server</primary></indexterm>
Many network administrators will want to use DHCP to
configure all client TCP/IP
protocol stack settings. (For information on how to
configure the ISC DHCP server
for Windows client support see <link
linkend="DHCP">the DNS and DHCP Configuration Guide<
/link>,
-------------------------------------------------------------------duplicate?
<link linkend="DHCP">DHCP
Server</link>. The default setting on Windows Me workstations i
s for DHCP-enabled operation
(i.e., <guimenu>Obtain IP address
automatically</guimenu> is enabled). See <link
linkend"WME002"></link>.
<figure id="WME002"><title>IP
Address.</title><imagefile>WME002</imagefile></figure>
_neadless?
<figure id="WME005"><title>DNS
Configuration.</title><imagefile>WME005</imagefile></figure>
_neadless?
</para>
<para>
<indexterm><primary>single DHCP
server</primary></indexterm>
<indexterm><primary>multiple Windows workgroups or
domains</primary></indexterm>
Windows workgroups or domains. See <link
linkend="WME003"></link>.
<figure id="WME003"><title>WINS
Configuration.</title><imagefile>WME003</imagefile></figure>
_neadless?
</para></step>
</procedure>
<figure id="wxpp001"><title>The General
Panel.</title><imagefile>wxpp001</imagefile></figure>
_neadless?
</para></step>
<step><para>
<indexterm><primary>Computer Name</primary></indexterm>
Samba-3. If you wish to change the computer name or join or
leave the domain, click the <guimenu>Change</guimenu> button.
See <link linkend="wxpp004"></link>.
<figure id="wxpp004"><title>The Computer
Name
Panel.</title><imagefile>wxpp004</imagefile></figure>
_needless?
</para></step>
We will join the domain called MIDEARTH. See <link
linkend="wxpp006"></link>.
<figure id="wxpp006"><title>The Computer
Name Changes
Panel.</title><imagefile>wxpp006</imagefile></figure>
_neadless?
</para></step>
<figure id="wxpp007"><title>The Computer
Name Changes Panel &smbmdash; Domain
MIDEARTH.</title><imagefile>wxpp007</imagefile></figure>
_neadless?
</para></step>
<figure id="wxpp008">
<title>Computer Name Changes &smbmdash;
Username and Password
Panel.</title><imagefile>wxpp008</imagefile>
_neadless?
</figure>
</para></step>
The Network Configuration Panel allows all common network
settings to be changed.
See <link linkend="WME009"></link>.
<figure id="WME009"><title>The Network
Panel.</title><imagefile>WME009</imagefile></figure>
_neadless?
</para>
settings. See <link
linkend="WME010"></link>.
<figure id="WME010"><title>Client for
Microsoft Networks Properties
Panel.</title><imagefile>WME010</imagefile></figure>
_neadless?
</para>
(domain) name and the machine name (computer name) need to be
set. See <link linkend="WME013"></link>.
<figure id="WME013"><title>Identification
Panel.</title><imagefile>WME013</imagefile></figure>
_neadless?
</para></step>
--
--- Oota Toshiya --- t-oota at dh.jp.nec.com
NEC Computers Software Operations Unit Shiba,Minato,Tokyo
Open Source Software Platform Development Division Japan,Earth,Solar system
(samba-jp/ldap-jp Staff,mutt-j/samba-jp postmaster)
John H Terpstra - Samba Team
2009-Jul-23 14:46 UTC
[Samba] TOSHAG-WindowsClientConfig.xml translate finished and some bug and typo(?) found
On 07/23/2009 01:33 AM, OPC oota wrote:> Now, TOSHARG-WindowsClientConfig.xml translate to Japanese finished(3.4.0 base). > > And some bug and typo(?) found.Thank you for your follow-through. The typos have been fixed in the master source branch. Cheers, John T.> > ------------------------------------------------------------------------------------------------- > <indexterm><primary>network difficulty</primary></indexterm> > <indexterm><primary>network client</primary></indexterm> > <indexterm><primary>client client instructions</primary></indexterm> > ------- duplicate?Fixed.> > Occasionally network administrators report difficulty getting Microsoft Windows clients to interoperate > correctly with Samba servers. It seems that some folks just cannot accept the fact that the right way > > > Many network administrators will want to use DHCP to configure all client TCP/IP > protocol stack settings. (For information on how to configure the ISC DHCP server > for Windows client support see <link linkend="DHCP">the DNS and DHCP Configuration Guide</link>, > <link linkend="DHCP">DHCP Server</link>. > _ forget )Added.> </para> > > > The example system uses manually configured DNS settings. When finished making changes, click the > <guibutton>OK</guibutton> to commit the settings. See <link linkend="WXPP014"/>. > <figure id="WXPP014"> <title>DNS Configuration.</title> <imagefile>WXPP014</imagefile> </figure> > _ needless?The <title></title> metatags were needed at one time to get around a preprocessor bug. You can remove them if you wish, but I decided to just leave them there.> </para></step> > > > <figure id="w2kp001"><title>Local Area Connection Properties.</title><imagefile>w2kp001</imagefile></figure> > _needless? > </para></step> > > <step><para> > <indexterm><primary>Local Area Connection Properties</primary></indexterm> > > > <indexterm><primary>TCP/IP</primary></indexterm> > <indexterm><primary>DNS</primary></indexterm> > <indexterm><primary>ISC DHCP server</primary></indexterm> > Many network administrators will want to use DHCP to configure all client TCP/IP > protocol stack settings. (For information on how to configure the ISC DHCP server > for Windows client support see <link linkend="DHCP">the DNS and DHCP Configuration Guide< > /link>, > ------------------------------------------------------------------duplicate?No, not duplicated - it is in a different section.> <link linkend="DHCP">DHCP Server</link>. > </para> > > > The default setting is DHCP-enabled operation > (i.e., <quote>Obtain an IP address automatically</quote>). See <link linkend="w2kp002"/>. > <figure id="w2kp002"><title>Internet Protocol (TCP/IP) Properties.</title><imagefile>w2kp002</imagefile></figure> > _neadless? > </para> > > > > > <step><para> > Click the <guimenu>Advanced</guimenu> button to proceed with TCP/IP configuration. > Refer to <link linkend="w2kp003"></link>. > <figure id="w2kp003"><title>Advanced Network Settings.</title><imagefile>w2kp003</imagefile></figure> > _neadless? > </para> > > > <figure id="w2kp004"><title>DNS Configuration.</title><imagefile>w2kp004</imagefile></figure> > _neadless? > </para></step> > > > See <link linkend="w2kp005"></link>. > <figure id="w2kp005"> > <title>WINS Configuration.</title><imagefile>w2kp005</imagefile> > _neadless? > </figure> > > > See <link linkend="WME001"></link>. > <figure id="WME001"> > <title>The Windows Me Network Configuration Panel.</title> > _neadless? > <imagefile>WME001</imagefile> > > > <indexterm><primary>DHCP</primary></indexterm> > <indexterm><primary>TCP/IP</primary></indexterm> > <indexterm><primary>ISC DHCP server</primary></indexterm> > Many network administrators will want to use DHCP to configure all client TCP/IP > protocol stack settings. (For information on how to configure the ISC DHCP server > for Windows client support see <link linkend="DHCP">the DNS and DHCP Configuration Guide< > /link>, > -------------------------------------------------------------------duplicate?Again in a different section.> <link linkend="DHCP">DHCP Server</link>. The default setting on Windows Me workstations i > s for DHCP-enabled operation > (i.e., <guimenu>Obtain IP address automatically</guimenu> is enabled). See <link linkend> "WME002"></link>. > <figure id="WME002"><title>IP Address.</title><imagefile>WME002</imagefile></figure> > _neadless? > > > > <figure id="WME005"><title>DNS Configuration.</title><imagefile>WME005</imagefile></figure> > _neadless? > </para> > > <para> > <indexterm><primary>single DHCP server</primary></indexterm> > <indexterm><primary>multiple Windows workgroups or domains</primary></indexterm> > > > Windows workgroups or domains. See <link linkend="WME003"></link>. > <figure id="WME003"><title>WINS Configuration.</title><imagefile>WME003</imagefile></figure> > _neadless? > </para></step> > </procedure> > > > <figure id="wxpp001"><title>The General Panel.</title><imagefile>wxpp001</imagefile></figure> > _neadless? > </para></step> > > <step><para> > <indexterm><primary>Computer Name</primary></indexterm> > > > Samba-3. If you wish to change the computer name or join or leave the domain, click the <guimenu>Change</guimenu> button. > See <link linkend="wxpp004"></link>. > <figure id="wxpp004"><title>The Computer Name Panel.</title><imagefile>wxpp004</imagefile></figure> > _needless? > </para></step> > > > We will join the domain called MIDEARTH. See <link linkend="wxpp006"></link>. > <figure id="wxpp006"><title>The Computer Name Changes Panel.</title><imagefile>wxpp006</imagefile></figure> > _neadless? > </para></step> > > > <figure id="wxpp007"><title>The Computer Name Changes Panel &smbmdash; Domain MIDEARTH.</title><imagefile>wxpp007</imagefile></figure> > _neadless? > </para></step> > > > <figure id="wxpp008"> > <title>Computer Name Changes &smbmdash; Username and Password Panel.</title><imagefile>wxpp008</imagefile> > _neadless? > </figure> > </para></step> > > > The Network Configuration Panel allows all common network settings to be changed. > See <link linkend="WME009"></link>. > <figure id="WME009"><title>The Network Panel.</title><imagefile>WME009</imagefile></figure> > _neadless? > </para> > > > settings. See <link linkend="WME010"></link>. > <figure id="WME010"><title>Client for Microsoft Networks Properties Panel.</title><imagefile>WME010</imagefile></figure> > _neadless? > </para> > > > (domain) name and the machine name (computer name) need to be set. See <link linkend="WME013"></link>. > <figure id="WME013"><title>Identification Panel.</title><imagefile>WME013</imagefile></figure> > _neadless? > </para></step> > > -- > --- Oota Toshiya --- t-oota at dh.jp.nec.com > NEC Computers Software Operations Unit Shiba,Minato,Tokyo > Open Source Software Platform Development Division Japan,Earth,Solar system > (samba-jp/ldap-jp Staff,mutt-j/samba-jp postmaster)