Posted on 2013-06-13
Last Modified: 2013-06-29
In the linux machine
we have /etc/hosts file

my linux machines are pinging fine

I have a windows machine

Machine name is ie hostname is
and the ip address is @@@.@@@.@@@

my content of /etc/hosts file of my linux machine is

 Do not remove the following line, or various programs
# that require network functionality will fail.    mac.localdomain mac    wtu.localdomain wtu    term2.localdomain term2    term1.localdomain term1       localhost.localdomain   localhost

What  should I do in order to ping my linux and machine should ping each other
plesase help..
Question by:walkerdba
  • 6
  • 5
LVL 68

Expert Comment

ID: 39245935
Copy the Linux hosts file unchanged to Windows as


and add your IP/hostname to the Linux hosts file

@@@.@@@.@@@.@@@ Mathew-PC.localdomain    Mathew-PC

Author Comment

ID: 39246532
Now /etc/hosts
in linux machine is now

# Do not remove the following line, or various programs
# that require network functionality will fail.    mac.localdomain mac    wtu.localdomain wtu    term2.localdomain term2    term1.localdomain term1     Mathew-PC.localdomain   Mathew-PC       localhost.localdomain   localhost


see the ping
[root@mac ~]# ping Mathew-PC
PING Mathew-PC.localdomain ( 56(84) bytes of data.

not pinginging

not pinging
LVL 68

Expert Comment

ID: 39246820
Seems that you can't reach your machine at all.

Does a ping against its IP address work?


I'm rather sure that this won't work either, and if so, please examine the network setup of the Windows machine and your network infrastructure (switches/routers, if any).
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.


Author Comment

ID: 39246963
The same ..

I can ping from windows machine..
But not from linux machine

Author Comment

ID: 39246976
Is there any way we can edit this file

gedit /etc/samba/smb.conf

# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
# If you want to use the useradd/groupadd family of binaries please run:
# setsebool -P samba_domain_controller on
# If you want to share home directories via samba please run:
# setsebool -P samba_enable_home_dirs on
# If you create a new directory you want to share you should mark it as
# "samba-share_t" so that selinux will let you write into it.
# Make sure not to do that on system directories as they may already have
# been marked with othe SELinux labels.
# Use ls -ldZ /path to see which context a directory has
# Set labels only on directories you created!
# To set a label use the following: chcon -t samba_share_t /path
# If you need to share a system created directory you can use one of the
# following (read-only/read-write):
# setsebool -P samba_export_all_ro on
# or
# setsebool -P samba_export_all_rw on
# If you want to run scripts (preexec/root prexec/print command/...) please
# put them into the /var/lib/samba/scripts directory so that smbd will be
# allowed to run them.
# Make sure you COPY them and not MOVE them so that the right SELinux context
# is applied, to check all is ok use restorecon -R -v /var/lib/samba/scripts
#======================= Global Settings =====================================
# ----------------------- Netwrok Related Options -------------------------
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
# server string is the equivalent of the NT Description field
# netbios name can be used to specify a server name not tied to the hostname
# Interfaces lets you configure Samba to use multiple interfaces
# If you have multiple network interfaces then you can list the ones
# you want to listen on (never omit localhost)
# Hosts Allow/Hosts Deny lets you restrict who can connect, and you can
# specifiy it as a per share option as well
      workgroup = MYGROUP
      server string = Samba Server Version %v
;      netbios name = MYSERVER
;      interfaces = lo eth0
;      hosts allow = 127. 192.168.12. 192.168.13.
# --------------------------- Logging Options -----------------------------
# Log File let you specify where to put logs and how to split them up.
# Max Log Size let you specify the max size log files should reach
      # logs split per machine
;      log file = /var/log/samba/%m.log
      # max 50KB per log file, then rotate
;      max log size = 50
# ----------------------- Standalone Server Options ------------------------
# Scurity can be set to user, share(deprecated) or server(deprecated)
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.

      security = user
      passdb backend = tdbsam

# ----------------------- Domain Members Options ------------------------
# Security must be set to domain or ads
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
# Use password server option only with security = server or if you can't
# use the DNS to locate Domain Controllers
# The argument list may include:
#   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
#   password server = *
;      security = domain
;      passdb backend = tdbsam
;      realm = MY_REALM

;      password server = <NT-Server-Name>

# ----------------------- Domain Controller Options ------------------------
# Security must be set to user for domain controllers
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
# Domain Logons let Samba be a domain logon server for Windows workstations.
# Logon Scrpit let yuou specify a script to be run at login time on the client
# You need to provide it in a share called NETLOGON
# Logon Path let you specify where user profiles are stored (UNC path)
# Various scripts can be used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
;      security = user
;      passdb backend = tdbsam
;      domain master = yes
;      domain logons = yes
      # the login script name depends on the machine name
;      logon script = %m.bat
      # the login script name depends on the unix user used
;      logon script = %u.bat
;      logon path = \\%L\Profiles\%u
      # disables profiles support by specifing an empty path
;      logon path =          
;      add user script = /usr/sbin/useradd "%u" -n -g users
;      add group script = /usr/sbin/groupadd "%g"
;      add machine script = /usr/sbin/useradd -n -c "Workstation (%u)" -M -d /nohome -s /bin/false "%u"
;      delete user script = /usr/sbin/userdel "%u"
;      delete user from group script = /usr/sbin/userdel "%u" "%g"
;      delete group script = /usr/sbin/groupdel "%g"
# ----------------------- Browser Control Options ----------------------------
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
;      local master = no
;      os level = 33
;      preferred master = yes
#----------------------------- Name Resolution -------------------------------
# Windows Internet Name Serving Support Section:
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
# - WINS Support: Tells the NMBD component of Samba to enable it's WINS Server
# - WINS Server: Tells the NMBD components of Samba to be a WINS Client
# - WINS Proxy: Tells Samba to answer name resolution queries on
#   behalf of a non WINS capable client, for this to work there must be
#   at least one      WINS Server on the network. The default is NO.
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups.
;      wins support = yes
;      wins server = w.x.y.z
;      wins proxy = yes
;      dns proxy = yes
# --------------------------- Printing Options -----------------------------
# Load Printers let you load automatically the list of printers rather
# than setting them up individually
# Cups Options let you pass the cups libs custom options, setting it to raw
# for example will let you use drivers on your Windows clients
# Printcap Name let you specify an alternative printcap file
# You can choose a non default printing system using the Printing option
      load printers = yes
      cups options = raw

;      printcap name = /etc/printcap
      #obtain list of printers automatically on SystemV
;      printcap name = lpstat
;      printing = cups

# --------------------------- Filesystem Options ---------------------------
# The following options can be uncommented if the filesystem supports
# Extended Attributes and they are enabled (usually by the mount option
# user_xattr). Thess options will let the admin store the DOS attributes
# in an EA and make samba not mess with the permission bits.
# Note: these options can also be set just per share, setting them in global
# makes them the default for all shares

;      map archive = no
;      map hidden = no
;      map read only = no
;      map system = no
;      store dos attributes = yes

#============================ Share Definitions ==============================
      comment = Home Directories
      browseable = no
      writable = yes
;      valid users = %S
;      valid users = MYDOMAIN\%S
      comment = All Printers
      path = /var/spool/samba
      browseable = no
      guest ok = no
      writable = no
      printable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
;      [netlogon]
;      comment = Network Logon Service
;      path = /var/lib/samba/netlogon
;      guest ok = yes
;      writable = no
;      share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;      [Profiles]
;      path = /var/lib/samba/profiles
;      browseable = no
;      guest ok = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;      [public]
;      comment = Public Stuff
;      path = /home/samba
;      public = yes
;      writable = yes
;      printable = no
;      write list = +staff

if my ip for windows machine is
and linux is

what should I edit....
LVL 68

Expert Comment

ID: 39247037
Add the Windows IP to "hosts allow" .

If "linux" designates another Samba client add this IP to "hosts allow" too.

If "linux" is the Samba server itself add this IP to "interfaces".

There is already "" in interfaces. Is this a typo ("12.2" instead of "2.12")?

You can also omit both directives to allow all local interfaces and all remote hosts.

Samba determines the local interfaces on its own, so there is generally no need for the "interfaces" directive.

Despite the existence of "hosts allow" access still requires suitable user-level passwords,
so use that directive only if there are elevated security requirements.

Author Comment

ID: 39248331
do you want me to change the whole address

hosts allow = 127. 192.168.12. 192.168.13.


hosts allow =
LVL 68

Expert Comment

ID: 39248468
"127." allows the whole class A range from to
"192.168.12." allows the whole class C range from to
"192.168.13." allows the whole class C range from to
"" allows just this host.

The "hosts allow" parameter is a comma, space, or tab delimited set of items, so you can specify as many of them as you like.

It's obviously up to you to decide which hosts you're willing to allow access.

What am I supposed to advise here?

Author Comment

ID: 39249415
how should I edit the above file
LVL 68

Accepted Solution

woolmilkporc earned 500 total points
ID: 39249688
Doesn't gedit (or "sudo gedit" if you aren't root) work for you?

gedit /etc/samba/smb.conf

sudo gedit /etc/samba/smb.conf

"vi" is always available, so

vi /etc/samba/smb.conf

sudo vi /etc/samba/smb.conf

By the way, is all this still related to your original question about pinging from Windows to Linux?

Samba is a file sharing option and requires an underlying  functional network.

Author Closing Comment

ID: 39287117

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

The Need In an Active Directory enviroment, the PDC emulator provide time synchronization for the domain. This is important since Active Directory uses Kerberos for authentication.  By default, if the time difference between systems is off by more …
I. Introduction There's an interesting discussion going on now in an Experts Exchange Group — Attachments with no extension ( This reminded me of questions tha…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.

679 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question