ok....

samba is acting up on me...

10.0.0.4 is giving me trouble, it can see samba shares and access them on other linux and windows computers....but no computers can see it through smb....i have tried messing with the smb.conf....changed it out...restarted samba...as far as i can tell, smb.conf is fine....it is just like the others on my other linux machines(minus the share definitions, of course)

i can ping it, ssh into it, etc....

the problem is that i cant smb 10.0.0.4 at all....if i try to access it with another linux computer on the network typing(in konquerer) "smb://10.0.0.4", konquerer gives me an error saying, "Could not connect to host 10.0.0.4 There is probably no SMB service running on this host"...this always works and i can see the other computers' samba shares just fine....just not 10.0.0.4

odd....because like i said, it can smb out.....but no one can smb in....

hrmmm......

i have three linux/samba computers on my network and two of them work just fine....just not 10.0.0.4


thanks

-derfaust

anybody got a suggestion???.....

thanks....

Perhaps posting the contents of smb.conf for everyone to look at?

A weird firewall (iptables) rule perhaps? One that blocks NETBIOS access from 10.0.0.x by mistake?

my smb.conf is fine.... 10.0.0.4 is a laptop(eth1 is an 802.11b card and eth0 is built in)....when i reboot with the CAT5 plugged in...samba works....is i unplug the CAT5 i get no smb love....

the wireless eth1 isnt smbing right....not sure why....like i said i can ssh into it...ping it....just not smb into it....

thanks for your help....

samba works with eth0 not with eth1.....hmmmm????



if it is of any help--eth0 is dhcp and eth1 is static...

the other working samba computers are static...but they are working fine...

the laptop with its two ethernet interfaces could be the problem??....

thanks for you replies....

hey Azmeen....how do i check iptables for what you were talking about?...
and if that is the problem.....how do i fix it?

that sounds like best lead yet...

hrrmmmmm,.....

thanks....

hwere is my smb.conf.....i think it has something to do wit multiple interfaces..

------------------------------------

# 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
#
# 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 many any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: LINUX2
workgroup = CLAN XL

# server string is the equivalent of the NT Description field
server string = Slackware

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
hosts allow = 10.0.0. 127.
hosts deny = all

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes

# you may wish to override the location of the printcap file
; printcap name = /etc/printcap

# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
printcap name = cups

# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
printing = cups

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
guest account = nobody

# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba.%m

# Put a capping on the size of the log files (in Kb).
max log size = 50

# Security mode. Most people will want user level security. See
# security_level.txt for details. NOTE: To get the behaviour of
# Samba-1.9.18, you'll need to use "security = share".
security = user

# Use password server option only with security = server
# 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 = *
; password server = <NT-Server-Name>

# Note: Do NOT use the now deprecated option of "domain controller"
# This option is no longer implemented.

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
encrypt passwords = yes

# Where to find the SSL certificates:
; ssl CA certDir = /etc/ssl/certs

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /usr/local/samba/lib/smb.conf.%m

# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
interfaces = eth0 lo
bind interfaces only = yes
remote announce = 10.0.0.255

# 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
; local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33

# 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 master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes

# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# 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.
; wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no

map to guest = Bad User

#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/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 = /usr/local/samba/profiles
; browseable = no
; guest ok = yes


# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual Mprinter
[printers]
comment = All Printers
# path = /var/spool/samba
path = /tmp
browseable = no
public = yes
guest ok = yes
writable = no
printable = yes

# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = 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

# Other examples.
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765


[data]
comment = windows data
path = /mnt/data
browsable = yes
public = yes
writable = no
printable = no


[system]
comment = windows system
path = /mnt/system
browsable = yes
public = yes
writable = no
printable = no



#[info]
#comment = windows data
#path = /root/info
#browsable = yes
#public = yes
#writable = no
#printable = no

You stated that the laptop wireless was static. Assuming you have correctly configured the laptops /etc files to assign the proper ip, aliases, host and what nots. Did you configure the other Linux boxes and maybe your win boxes host file to reflect this "static" connection??? IF you didn't AND a Linux box wins the smb elections which it will most likely do THEN it will not be in the domain network. If it was configured for DCHP and was assigned by your server it would...

I have had about the same thing with computers on my network that are not listed below...
Once they where added to the proper host files all went well...

Well, the first thing you should do is run nmap 10.0.0.4 from one of your other hosts. Check and see if the NETBIOS ports are available on that host. If it is filtered, then it means that most likely, iptables is blocking smb requests to that host.

If it's open, then it's possible that your smb.conf is wrong... And it does seem wrong to me due to this section:

Perhaps eth1 should be in there as well, yes?

lol.....i came across this and giggled...hours and hours and all it was was adding eth1 to interfaces....

for example.....

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
interfaces = eth0 eth1 lo
bind interfaces only = yes
remote announce = 10.0.0.255

viola.....still cant browse by hostname though from the laptop...

---any ideas about thee hostname issue?....

dig

rock azmeen....i didnt see your post till just now...lol....i shoulda checked my email earlier....lol


thanks for your help....


now if i could just use the hostname instead of the IPs...

dig!!

well...thought i would post some update love...

everything is all good....

i setup a DNS server and *poof*

it works....rock!

Congrats man... glad to be of some help