IPV4 to IPV6

[Fail2Ban] SSH: banned 61.235.153.45

Tukiyooo 0 01:21

Hi, The IP 61.235.153.45 has just been banned by Fail2Ban after 5 attempts against SSH. Here are more information about <a href="http://61.235.153.45">61.235.153.45</a>: [Querying <a href="http://whois.apnic.net">whois.apnic.net</a>] [<a href="http://whois.apnic.net">whois.apnic.net</a>] % [<a href="http://whois.apnic.net">whois.apnic.net</a>] % Whois data copyright terms <a href="http://www.apnic.net/db/dbcopyright.html">http://www.apnic.net/db/dbcopyright.html</a> % Information related to '61.232.0.0 - 61.237.255.255' inetnum: 61.232.0.0 - 61.237.255.255 netname: CTTNET descr: China TieTong Telecommunications Corporation descr: Jinze Mansion, 2 Guangningbo Street, descr: Xicheng District, Beijing, China, 100032 country: CN admin-c: WP188-AP tech-c: LM273-AP status: ALLOCATED PORTABLE mnt-by: MAINT-CNNIC-AP mnt-lower: MAINT-CN-CRTC mnt-routes: MAINT-CNNIC-AP mnt-irt: IRT-CNNIC-CN changed: <a href="mailto:hm-changed@apnic.net">hm-changed@apnic.net</a> 20090430 source: APNIC irt: IRT-CNNIC-CN address: Beijing, China e-mail: <a href="mailto:ipas@cnnic.cn">ipas@cnnic.cn</a> abuse-mailbox: <a href="mailto:ipas@cnnic.cn">ipas@cnnic.cn</a> admin-c: IP50-AP tech-c: IP50-AP auth: # Filtered remarks: Please note that CNNIC is not an ISP and is not remarks: empowered to investigate complaints of network abuse. remarks: Please contact the tech-c or admin-c of the network. mnt-by: MAINT-CNNIC-AP changed: <a href="mailto:ipas@cnnic.cn">ipas@cnnic.cn</a> 20110428 source: APNIC person: liu min nic-hdl: LM273-AP e-mail: <a href="mailto:crnet_mgr@chinatietong.com">crnet_mgr@chinatietong.com</a> address: 22F Yuetan Mansion, Xicheng District, Beijing, P.R.China phone: +86-10-51848796 fax-no: +86-10-51842426 country: CN changed: <a href="mailto:ipas@cnnic.net.cn">ipas@cnnic.net.cn</a> 20120320 mnt-by: MAINT-CNNIC-AP source: APNIC person: Wang Pei nic-hdl: WP188-AP e-mail: <a href="mailto:crnet_mgr@chinatietong.com">crnet_mgr@chinatietong.com</a> address: Jinze Mansion, 2 Guangningbo Street, address: Xicheng District, Beijing, China, 100032 phone: +21-51892106 fax-no: +21-51847802 country: CN changed: <a href="mailto:ipas@cnnic.net.cn">ipas@cnnic.net.cn</a> 20060926 mnt-by: MAINT-CNNIC-AP source: APNIC % Information related to '<a href="http://61.232.0.0/14AS9394">61.232.0.0/14AS9394</a>' route: <a href="http://61.232.0.0/14">61.232.0.0/14</a> descr: CHINA RAILWAY TELECOMMUNICATIONS country: CN origin: AS9394 mnt-by: MAINT-CNNIC-AP changed: <a href="mailto:ipas@cnnic.cn">ipas@cnnic.cn</a> 20100528 source: APNIC % This query was served by the APNIC Whois Service version 1.68.5 (WHOIS1) Regards, Fail2Ban

[Fail2Ban] SSH: banned 61.235.153.45

Hi, The IP 61.235.153.45 has just been banned by Fail2Ban after 5 attempts against SSH. Here are more information about 61.235.153.45 : [Que...

Smbclient or samba Client Configure

Tukiyooo 0 Red Hat Enterprise & Server Administration 22:00

<div dir="ltr" style="text-align: left;" trbidi="on"><a href="http://www.ipv4-ipv6.blogspot.com/"></a>SMB or Samba Discription: An SMB client program for UNIX machines is included with the Samba distribution. It provides an ftp-like interface on the command line. You can use this utility to transfer files between a Windows 'server' and a Linux client. This Command is used for see smbclient file or directory share : [root@myhost~]#smbclient -L Server1 For access smb share  command : [root@myhost~]#smbclient -U student // Server1/homes Now ssh service is must be do you running  or  you will Check command for SSH Service. [root@myhost~]#service sshd status [root@myhost~]#chkconfig --list | grep telnet And Client machine command for used: [root@myhost~]#telnet hostname [root@myhost~]#telnet myshost1.example.com [root@myhost~]#ssh user@hostname [root@myhost~]#ssh user@hostname command [root@myhost~]# For Example: [root@myhost~]#ssh asraful@myhost1.example.com [root@myhost~]#ssh asraful@server1 'df -h' Now You will Copy, Cut , Past Command is 'scp -r '  'scp -p'  'scp -c' For More help: <a href="http://www.linux.org/" target="_blank">www.linux.org</a> Briefing for SMB Server:  An SMB client program for UNIX machines is included with the Samba distribution. It provides an ftp-like interface on the command line. You can use this utility to transfer files between a Windows 'server' and a Linux clien</div>

Smbclient or samba Client Configure

SMB or Samba Discription: An SMB client program for UNIX machines is included with the Samba distribution. It provides an ftp-like interfa...

[Fail2Ban] SSH: banned 178.20.157.16

Tukiyooo 0 19:04

Hi, The IP 178.20.157.16 has just been banned by Fail2Ban after 5 attempts against SSH. Here are more information about <a href="http://178.20.157.16">178.20.157.16</a>: [Querying <a href="http://whois.arin.net">whois.arin.net</a>] [Redirected to <a href="http://whois.ripe.net:43">whois.ripe.net:43</a>] [Querying <a href="http://whois.ripe.net">whois.ripe.net</a>] [<a href="http://whois.ripe.net">whois.ripe.net</a>] % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See <a href="http://www.ripe.net/db/support/db-terms-conditions.pdf">http://www.ripe.net/db/support/db-terms-conditions.pdf</a> % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '178.20.156.0 - 178.20.157.255' % Abuse contact for '178.20.156.0 - 178.20.157.255' is '<a href="mailto:abuse@freeehost.com.ua">abuse@freeehost.com.ua</a>' inetnum: 178.20.156.0 - 178.20.157.255 netname: FREEHOST-DC descr: Freehost UA country: UA admin-c: FNOC-RIPE tech-c: FNOC-RIPE status: ASSIGNED PA mnt-by: FREEHOST-MNT mnt-lower: FREEHOST-MNT mnt-routes: FREEHOST-MNT source: RIPE # Filtered role: Freehost NOC address: 01032, Ukraine, Kiev address: bul. Tarasa Shevchenko 36b, office 15 phone: +380 44 4515342 fax-no: +380 44 2346174 remarks: Contact information for Freehost UA network remarks: Network routing & peering issues: noc at <a href="http://freehost.ua">freehost.ua</a> remarks: SPAM and Network security issues: abuse at <a href="http://freehost.ua">freehost.ua</a> remarks: Customer support: support at <a href="http://freehost.ua">freehost.ua</a> remarks: Customer contracts issues: service at <a href="http://freehost.ua">freehost.ua</a> admin-c: ESS912-RIPE tech-c: CHIP6-RIPE tech-c: ESS912-RIPE nic-hdl: FNOC-RIPE mnt-by: FREEHOST-MNT source: RIPE # Filtered % Information related to '<a href="http://178.20.156.0/23AS42331">178.20.156.0/23AS42331</a>' route: <a href="http://178.20.156.0/23">178.20.156.0/23</a> descr: Freehost UA origin: AS42331 mnt-by: FREEHOST-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.69 (WHOIS4) Regards, Fail2Ban

[Fail2Ban] SSH: banned 178.20.157.16

Hi, The IP 178.20.157.16 has just been banned by Fail2Ban after 5 attempts against SSH. Here are more information about 178.20.157.16 : [Que...

[Fail2Ban] SSH: banned 221.178.164.251

Tukiyooo 0 17:58

Hi, The IP 221.178.164.251 has just been banned by Fail2Ban after 5 attempts against SSH. Here are more information about <a href="http://221.178.164.251">221.178.164.251</a>: [Querying <a href="http://whois.apnic.net">whois.apnic.net</a>] [<a href="http://whois.apnic.net">whois.apnic.net</a>] % [<a href="http://whois.apnic.net">whois.apnic.net</a>] % Whois data copyright terms <a href="http://www.apnic.net/db/dbcopyright.html">http://www.apnic.net/db/dbcopyright.html</a> % Information related to '221.176.0.0 - 221.183.255.255' inetnum: 221.176.0.0 - 221.183.255.255 netname: CMNET descr: China Mobile Communications Corporation descr: Mobile Communications Network Operator in China descr: Internet Service Provider in China country: CN admin-c: JS686-AP tech-c: CT74-AP mnt-by: APNIC-HM mnt-lower: MAINT-CN-CMCC mnt-routes: MAINT-CN-CMCC remarks: ------------------------------ remarks: Please send abuse e-mail to remarks: <a href="mailto:abuse@chinamobile.com">abuse@chinamobile.com</a> remarks: Please send probe e-mail to remarks: <a href="mailto:security@chinamobile.com">security@chinamobile.com</a> remarks: ------------------------------- changed: <a href="mailto:hm-changed@apnic.net">hm-changed@apnic.net</a> 20030909 changed: <a href="mailto:hm-changed@apnic.net">hm-changed@apnic.net</a> 20030923 status: ALLOCATED PORTABLE source: APNIC role: chinamobile tech address: 29, Jinrong Ave.,Xicheng district address: Beijing country: CN phone: +86 6600 6688 fax-no: +86 6600 6187 e-mail: <a href="mailto:hostmaster@chinamobile.com">hostmaster@chinamobile.com</a> remarks: send spam reports to <a href="mailto:spam@chinamobile.com">spam@chinamobile.com</a> remarks: and abuse reports to <a href="mailto:abuse@chinamobile.com">abuse@chinamobile.com</a> remarks: Please include detailed information and remarks: times in UTC admin-c: HL1318-AP tech-c: JS686-AP nic-hdl: ct74-AP notify: <a href="mailto:hostmaster@chinamobile.com">hostmaster@chinamobile.com</a> mnt-by: MAINT-cn-cmcc changed: <a href="mailto:hostmaster@chinamobile.com">hostmaster@chinamobile.com</a> 20091019 source: APNIC person: Jinxia Sun address: China Mobile Communications Corporation address: 29, Jinrong Ave., Xicheng District, Beijing, 100032 country: CN phone: +86-10-66006688-1755 fax-no: +86-10-66006012 e-mail: <a href="mailto:sunjinxia@chinamobile.com">sunjinxia@chinamobile.com</a> nic-hdl: JS686-AP remarks: ------------------------------ remarks: Please send abuse e-mail to remarks: <a href="mailto:abuse@chinamobile.com">abuse@chinamobile.com</a> remarks: Please send probe e-mail to remarks: <a href="mailto:security@chinamobile.com">security@chinamobile.com</a> remarks: ------------------------------- mnt-by: MAINT-CN-CMCC changed: <a href="mailto:hostmaster@chinamobile.com">hostmaster@chinamobile.com</a> 20030130 source: APNIC % Information related to '<a href="http://221.176.0.0/13AS9808">221.176.0.0/13AS9808</a>' route: <a href="http://221.176.0.0/13">221.176.0.0/13</a> descr: China Mobile communications corporation origin: AS9808 mnt-by: MAINT-CN-CMCC changed: <a href="mailto:hostmaster@chinamobile.com">hostmaster@chinamobile.com</a> 20120215 source: APNIC % This query was served by the APNIC Whois Service version 1.68.5 (WHOIS3) Regards, Fail2Ban

[Fail2Ban] SSH: banned 221.178.164.251

Hi, The IP 221.178.164.251 has just been banned by Fail2Ban after 5 attempts against SSH. Here are more information about 221.178.164.251 : ...

[Fail2Ban] SSH: banned 222.35.72.30

Tukiyooo 0 12:46

Hi, The IP 222.35.72.30 has just been banned by Fail2Ban after 6 attempts against SSH. Here are more information about <a href="http://222.35.72.30">222.35.72.30</a>: [Querying <a href="http://whois.apnic.net">whois.apnic.net</a>] [<a href="http://whois.apnic.net">whois.apnic.net</a>] % [<a href="http://whois.apnic.net">whois.apnic.net</a>] % Whois data copyright terms <a href="http://www.apnic.net/db/dbcopyright.html">http://www.apnic.net/db/dbcopyright.html</a> % Information related to '222.32.0.0 - 222.63.255.255' inetnum: 222.32.0.0 - 222.63.255.255 netname: CTTNET descr: China TieTong Telecommunications Corporation descr: Jinze Mansion, 2 Guangningbo Street, descr: Xicheng District, Beijing, China, 100032 country: CN admin-c: WP188-AP tech-c: LM273-AP status: ALLOCATED PORTABLE mnt-by: MAINT-CNNIC-AP mnt-lower: MAINT-CN-CRTC mnt-routes: MAINT-CNNIC-AP mnt-irt: IRT-CNNIC-CN changed: <a href="mailto:hm-changed@apnic.net">hm-changed@apnic.net</a> 20090430 source: APNIC irt: IRT-CNNIC-CN address: Beijing, China e-mail: <a href="mailto:ipas@cnnic.cn">ipas@cnnic.cn</a> abuse-mailbox: <a href="mailto:ipas@cnnic.cn">ipas@cnnic.cn</a> admin-c: IP50-AP tech-c: IP50-AP auth: # Filtered remarks: Please note that CNNIC is not an ISP and is not remarks: empowered to investigate complaints of network abuse. remarks: Please contact the tech-c or admin-c of the network. mnt-by: MAINT-CNNIC-AP changed: <a href="mailto:ipas@cnnic.cn">ipas@cnnic.cn</a> 20110428 source: APNIC person: liu min nic-hdl: LM273-AP e-mail: <a href="mailto:crnet_mgr@chinatietong.com">crnet_mgr@chinatietong.com</a> address: 22F Yuetan Mansion, Xicheng District, Beijing, P.R.China phone: +86-10-51848796 fax-no: +86-10-51842426 country: CN changed: <a href="mailto:ipas@cnnic.net.cn">ipas@cnnic.net.cn</a> 20120320 mnt-by: MAINT-CNNIC-AP source: APNIC person: Wang Pei nic-hdl: WP188-AP e-mail: <a href="mailto:crnet_mgr@chinatietong.com">crnet_mgr@chinatietong.com</a> address: Jinze Mansion, 2 Guangningbo Street, address: Xicheng District, Beijing, China, 100032 phone: +21-51892106 fax-no: +21-51847802 country: CN changed: <a href="mailto:ipas@cnnic.net.cn">ipas@cnnic.net.cn</a> 20060926 mnt-by: MAINT-CNNIC-AP source: APNIC % This query was served by the APNIC Whois Service version 1.68.5 (WHOIS3) Regards, Fail2Ban

[Fail2Ban] SSH: banned 222.35.72.30

Hi, The IP 222.35.72.30 has just been banned by Fail2Ban after 6 attempts against SSH. Here are more information about 222.35.72.30 : [Query...

[Fail2Ban] SSH: banned 121.10.105.4

Tukiyooo 0 11:47

Hi, The IP 121.10.105.4 has just been banned by Fail2Ban after 5 attempts against SSH. Here are more information about <a href="http://121.10.105.4">121.10.105.4</a>: [Querying <a href="http://whois.apnic.net">whois.apnic.net</a>] [<a href="http://whois.apnic.net">whois.apnic.net</a>] % [<a href="http://whois.apnic.net">whois.apnic.net</a>] % Whois data copyright terms <a href="http://www.apnic.net/db/dbcopyright.html">http://www.apnic.net/db/dbcopyright.html</a> % Information related to '121.8.0.0 - 121.15.255.255' inetnum: 121.8.0.0 - 121.15.255.255 netname: CHINANET-GD descr: CHINANET Guangdong province network descr: China Telecom descr: No.31,jingrong street descr: Beijing 100032 country: CN admin-c: CH93-AP tech-c: IC83-AP mnt-by: APNIC-HM mnt-lower: MAINT-CHINANET-GD mnt-routes: MAINT-CHINANET-GD status: ALLOCATED PORTABLE remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+ remarks: This object can only be updated by APNIC hostmasters. remarks: To update this object, please contact APNIC remarks: hostmasters and include your organisation's account remarks: name in the subject line. remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+ changed: <a href="mailto:hm-changed@apnic.net">hm-changed@apnic.net</a> 20060518 source: APNIC person: Chinanet Hostmaster nic-hdl: CH93-AP e-mail: <a href="mailto:anti-spam@ns.chinanet.cn.net">anti-spam@ns.chinanet.cn.net</a> address: No.31 ,jingrong street,beijing address: 100032 phone: +86-10-58501724 fax-no: +86-10-58501724 country: CN changed: <a href="mailto:dingsy@cndata.com">dingsy@cndata.com</a> 20070416 mnt-by: MAINT-CHINANET source: APNIC person: IPMASTER CHINANET-GD nic-hdl: IC83-AP e-mail: <a href="mailto:ipadm@189.cn">ipadm@189.cn</a> address: NO.1,RO.DONGYUANHENG,YUEXIUNAN,GUANGZHOU phone: +86-20-83877223 fax-no: +86-20-83877223 country: CN changed: <a href="mailto:ipadm@189.cn">ipadm@189.cn</a> 20110418 mnt-by: MAINT-CHINANET-GD remarks: IPMASTER is not for spam complaint,please send spam complaint to <a href="mailto:abuse_gdnoc@189.cn">abuse_gdnoc@189.cn</a> abuse-mailbox: <a href="mailto:abuse_gdnoc@189.cn">abuse_gdnoc@189.cn</a> source: APNIC % Information related to '<a href="http://121.8.0.0/13AS4134">121.8.0.0/13AS4134</a>' route: <a href="http://121.8.0.0/13">121.8.0.0/13</a> descr: From Guangdong Network of ChinaTelecom origin: AS4134 mnt-by: MAINT-CHINANET changed: <a href="mailto:dingsy@cndata.com">dingsy@cndata.com</a> 20060707 source: APNIC % This query was served by the APNIC Whois Service version 1.68.5 (WHOIS4) Regards, Fail2Ban

[Fail2Ban] SSH: banned 121.10.105.4

Hi, The IP 121.10.105.4 has just been banned by Fail2Ban after 5 attempts against SSH. Here are more information about 121.10.105.4 : [Query...

NFS Server Red Hat Enterprise in system Administration

Tukiyooo 0 Red Hat Enterprise & Server Administration 09:09

<div dir="ltr" style="text-align: left;" trbidi="on">What is NFS Server: Network File System, is a server-client protocol for sharing files system between computers on a common network. NFS enables you to mount a file system on a remote computer as if it were local to your own system. You can then directly access any of the files on that SSH / Telnet / remote file system. The server and client do not have to use the same operating system. The client system just needs to be running an NFS client compatible with the NFS server. For example:  NFS server could be a Linux system and Unix could be a client. But it can’t be a window system because window is not NFS compatible. The NFS server exports one or more directories to the client systems, and the client systems mount one or more of the shared directories to local directories called mount points. After the share is mounted, all I/O operations are written back to the server, and all clients notice the change as if it occurred on the local filesystem. A manual refresh is not needed because the client accesses the remote filesystem as if it were local.because access is granted by IP address, a username and password are not required. However, there are security risks to consider because the NFS server knows nothing about the users on the client system. Therefore NFS System is the best System in the world . it is very easy , or very best system than  windows system  . <a href="http://computernetworkingnotes.com/linux-network-administrations/network-configurations.html">Network configuration in Linux </a> <ul class="ul_arrow"><li>A linux server with ip address 192.168.0.254 and hostname Server</li><li>A linux client with ip address 192.168.0.1 and hostname Client1</li><li>Updated /etc/hosts file on both linux system</li><li>Running portmap and xinetd services</li><li>Firewall should be off on server</li></ul>We suggest you to review that article before start configuration of nfs server. Once you have completed the necessary steps follow this guide.Three rpm are required to configure nfs server. nfs, portmap, xinetd check them if not found then install <img alt="rpm" border="0" class="padded s5_lazyload" height="135" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass33_ser_rpm.jpg" style="opacity: 1;" width="310" /> Now check nfs, portmap, xinetd service in system service it should be on <div class="code"><pre>#setup Select System service from list [*]portmap [*]xinetd [*]nfs </pre></div>Now restart xinetd and portmap service <img alt="service restart" border="0" class="padded s5_lazyload" height="119" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass24_service_restart.jpg" style="opacity: 1;" width="607" /> To keep on these services after reboot on then via chkconfig command <img alt="chkconfig" border="0" class="padded s5_lazyload" height="55" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass24_chkconfig.jpg" style="opacity: 1;" width="337" /> After reboot verify their status. It must be in running condition <img alt="service status" border="0" class="padded s5_lazyload" height="84" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass24_service_status.jpg" style="opacity: 1;" width="354" /> now create a /data directory and grant full permission to it <img alt="mkdir" border="0" class="padded s5_lazyload" height="53" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass33_ser_mkdir.jpg" style="opacity: 1;" width="299" /> now open /etc/exports file <img alt="vi exports" border="0" class="padded s5_lazyload" height="25" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass33_ser_vi_file.jpg" style="opacity: 1;" width="318" /> share data folder for the network of 192.168.0.254/24 with read and write access <img alt="editing in exports" border="0" class="padded s5_lazyload" height="22" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass33_ser_file_edit.jpg" style="opacity: 1;" width="369" /> save file with :wq and exit now restart the nfs service and also on it with chkconfig <img alt="service nfs restart" border="0" class="padded s5_lazyload" height="263" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass33_ser_service_restart.jpg" style="opacity: 1;" width="622" /> also restart nfs daemons with expotfs <img alt="exportfs" border="0" class="padded s5_lazyload" height="41" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass33_ser_export_r.jpg" style="opacity: 1;" width="258" /> verify with showmount command that you have successfully shared data folder <img alt="showmount" border="0" class="padded s5_lazyload" height="67" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass33_ser_showmount.jpg" style="opacity: 1;" width="269" /> <h3>Or apply this system:</h3>Every file system being exported to remote users via NFS, as well as the access level for those file systems, are listed in the <tt class="FILENAME">/etc/exports</tt> file. When the <tt class="COMMAND">nfs</tt> service starts, the <tt class="COMMAND">/usr/sbin/exportfs</tt> command launches and reads this file, passes control to <tt class="COMMAND">rpc.mountd</tt> (if NFSv2 or NFSv3) for the actual mounting process, then to <tt class="COMMAND">rpc.nfsd</tt> where the file systems are then available to remote users. When issued manually, the <tt class="COMMAND">/usr/sbin/exportfs</tt> command allows the root user to selectively export or unexport directories without restarting the NFS service. When given the proper options, the <tt class="COMMAND">/usr/sbin/exportfs</tt> command writes the exported file systems to <tt class="FILENAME">/var/lib/nfs/xtab</tt>. Since <tt class="COMMAND">rpc.mountd</tt> refers to the <tt class="FILENAME">xtab</tt> file when deciding access privileges to a file system, changes to the list of exported file systems take effect immediately. The following is a list of commonly used options available for <tt class="COMMAND">/usr/sbin/exportfs</tt>: <h3> </h3><h3>configure client system</h3>ping form nfs server and check the share folder <img alt="showmount" border="0" class="padded s5_lazyload" height="69" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass33_cl_showmount.jpg" style="opacity: 1;" width="402" /> now mount this share folder on mnt mount point. To test this share folder change directory to mnt and create a test file <img alt="mount server directory" border="0" class="padded s5_lazyload" height="83" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass33_cl_mount.jpg" style="opacity: 1;" width="500" /> After use you should always unmount from mnt mount point <img alt="unmount" border="0" class="padded s5_lazyload" height="56" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass33_cl_unmount.jpg" style="opacity: 1;" width="269" /> In this way you can use shared folder. But this share folder will be available till system is up. It will not be available after reboot. To keep it available after reboot make its entry in fstab create a mount point, by making a directory <img alt="mkdir" border="0" class="padded s5_lazyload" height="22" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass33_cl_mkdir_temp.jpg" style="opacity: 1;" width="274" /> now open /etc/fstab file <img alt="vi fstab" border="0" class="padded s5_lazyload" height="19" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass33_vi_fstab.jpg" style="opacity: 1;" width="309" /> make entry for nfs shared directory and define /temp to mount point <img alt="file fstab" border="0" class="padded s5_lazyload" height="166" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass33_cl_file_fstab.jpg" style="opacity: 1;" width="682" /> <div class="custom"><div class="link_text_laybord"> <ins style="background-color: transparent; border: none; display: inline-table; height: 15px; margin: 0; padding: 0; position: relative; visibility: visible; width: 728px;"><ins id="aswift_3_anchor" style="background-color: transparent; border: none; display: block; height: 15px; margin: 0; padding: 0; position: relative; visibility: visible; width: 728px;"></ins></ins> </div></div>save the with :wq and exit reboot the system with reboot -f command <div class="code"><pre> #reboot -f </pre></div>after reboot check /temp directory it should show all the shared data <img alt="cd temp" border="0" class="padded s5_lazyload" height="71" src="http://computernetworkingnotes.com/images/rhce_certification/image/ass33_cl_cd_temp.jpg" style="opacity: 1;" width="248" /> For more information: <a href="http://www.linux.org/"><cite>www.linux.org/</cite></a> <cite> </cite>‎</div>

NFS Server Red Hat Enterprise in system Administration

What is NFS Server: Network File System, is a server-client protocol for sharing files system between computers on a common network. NFS e...