Fwd: [Samba] Network path not found - Windows to Linux connection

I reckon that UDP port 137 (NetBIOS name service) is being blocked
between you and the remote host.

Have you tried creating a local entry in your LMHOSTS file which
matches the target servers' NetBIOS name? Give that a shot, I think
it might help.


On 1/6/06, Keith Hilen <khilen@ix.netcom.com> wrote:
> I am trying to use Samba to access files on Linux server from a Windows X=
P client. The server is running RedHat Linux 9 with Samba 3.0.21a installed=
, and the client is running Windows XP Home Edition, Service Pack 2.
>
> After installing the new Samba package on the server, I edited the config=
uration file, started the service and added a user with smbpasswd.
>
> To test that this was all working, I ran
> smbclient //dellex.net/mydir -U myuser
> on the server itself. This prompted for a password. Once the password was=
entered, the smb prompt appeared : "smb: \>" and I was able to access file=
s. So far so good.
>
> Over on the Windows side, I opened a DOS box and entered the following:
> net use q: \\dellex.net\mydir
> After about a 20 second delay, it prompted for a user name and then a pas=
sword. I entered these, and received the following message:
> System error 53 has occurred.
> The network path was not found.
>
> I see from the postings that this is a very common error message, but I h=
ave not been able to ferret out a solution from the information posted. One=
posting suggested that I needed to turn on the "Allow Netbios over TCP/IP"=
flag - I did this, but it did not solve the problem.
>
> In the log file, /var/log/samba/log.smdbd, I found a message showing that=
the first connection (using smbclient on the server) worked properly. Howe=
ver, there are no error messages or any other indication that the the Windo=
ws-initiated connection even happened. This seems to indicate that the conn=
ection request is not getting from the client to the server at all. I tried=
turning off the Windows firewall and the wireless router firewall (briefly=
) to no avail.
>
> Note that the server I am trying to reach is hosted at a remote ISP. I al=
so have a local Linux server with an almost identical configuration. I am a=
ble to use Samba on that local server with no problem.
>
> Any idea what I should try next?
>
> -------------------------------------------------------------------------=
-
> Here is /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
> #
> # 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 "testpar=
m"
> # to check that you have not made any basic syntactic errors.
> #
> #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= 3D=3D=3D=3D=3D=3D=3D Gl=
obal Settings =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D
> [global]
>
> # workgroup =3D NT-Domain-Name or Workgroup-Name
> workgroup =3D linux
>
> # server string is the equivalent of the NT Description field
> server string =3D Samba Server
>
> # 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 =3D 192.168.1. 192.168.2. 127.
>
> # if you want to automatically load your printer list rather
> # than setting them up individually then you'll need this
> printcap name =3D /etc/printcap
> load printers =3D yes
>
> # It should not be necessary to spell out the print system type unless
> # yours is non-standard. Currently supported print systems include:
> # bsd, sysv, plp, lprng, aix, hpux, qnx
> ; printing =3D bsd
>
> # Uncomment this if you want a guest account, you must add this to /etc/p=
asswd
> # otherwise the user "nobody" is used
> ; guest account =3D pcguest
>
> # this tells Samba to use a separate log file for each machine
> # that connects
> # log file =3D /var/log/samba/%m.log
> # all log information in one file
> log file =3D /var/log/samba/log.smbd
>
> # Put a capping on the size of the log files (in Kb).
> max log size =3D 50
>
> # Security mode. Most people will want user level security. See
> # security_level.txt for details.
> security =3D user
> # Use password server option only with security =3D server
> ; password server =3D <NT-Server-Name>
>
> # Password Level allows matching of _n_ characters of the password for
> # all combinations of upper and lower case.
> ; password level =3D 8
> ; username level =3D 8
>
> # 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 =3D yes
> smb passwd file =3D /etc/samba/smbpasswd
>
> # The following are needed to allow password changing from Windows to
> # update the Linux system password also.
> # NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
> # NOTE2: You do NOT need these to allow workstations to change only
> # the encrypted SMB passwords. They allow the Unix password
> # to be kept in sync with the SMB password.
> ; unix password sync =3D Yes
> ; passwd program =3D /usr/bin/passwd %u
> ; passwd chat =3D *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n=
\n *passwd:*all*authentication*tokens*updated*success fully*
>
> # Unix users can map to different SMB User names
> ; username map =3D /etc/samba/smbusers
>
> # 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 =3D /etc/samba/smb.conf.%m
>
> # Most people will find that this option gives better performance.
> # See speed.txt and the manual pages for details
> socket options =3D TCP_NODELAY SO_RCVBUF=3D8192 SO_SNDBUF=3D8192
>
> # 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 =3D 192.168.12.2/24 192.168.13.2/24
>
> # Configure remote browse list synchronisation here
> # request announcement to, or browse list sync from:
> # a specific host or from / to a whole subnet (see below)
> ; remote browse sync =3D 192.168.3.25 192.168.5.255
> # Cause this host to announce itself to local subnets here
> ; remote announce =3D 192.168.1.255 192.168.2.44
>
> # 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 =3D no
>
> # OS Level determines the precedence of this server in master browser
> # elections. The default value should be reasonable
> ; os level =3D 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 =3D yes
>
> # Preferred Master causes Samba to force a local browser election on star=
tup
> # and gives it a slightly higher chance of winning the election
> ; preferred master =3D yes
>
> # Enable this if you want Samba to be a domain logon server for
> # Windows95 workstations.
> ; domain logons =3D 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 =3D %m.bat
> # run a specific logon batch file per username
> ; logon script =3D %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 =3D \\%L\Profiles\%U
>
> # All NetBIOS names must be resolved to IP Addresses
> # 'Name Resolve Order' allows the named resolution mechanism to be specif=
ied
> # the default order is "host lmhosts wins bcast". "host" means use the un=
ix
> # system gethostbyname() function call that will use either /etc/hosts OR
> # DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch=
..conf
> # and the /etc/resolv.conf file. "host" therefore is system configuration
> # dependant. This parameter is most often of use to prevent DNS lookups
> # in order to resolve NetBIOS names to IP Addresses. Use with care!
> # The example below excludes use of name resolution for machines that are=
NOT
> # on the local network segment
> # - OR - are not deliberately to be known via lmhosts or via WINS.
> ; name resolve order =3D wins lmhosts bcast
>
> # Windows Internet Name Serving Support Section:
> # WINS Support - Tells the NMBD component of Samba to enable it's WINS Se=
rver
> ; wins support =3D 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 =3D 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 =3D 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 =3D no
>
> # Case Preservation can be handy - system default is _no_
> # NOTE: These can be set on a per share basis
> ; preserve case =3D no
> ; short preserve case =3D no
> # Default case is normally upper case for all DOS files
> ; default case =3D lower
> # Be very careful with case sensitivity - it can break things!
> ; case sensitive =3D no
>
> #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= 3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D Share Definitions =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> [homes]
> comment =3D Home Directories
> browseable =3D no
> writable =3D yes
>
> # Un-comment the following and create the netlogon directory for Domain L=
ogons
> ; [netlogon]
> ; comment =3D Network Logon Service
> ; path =3D /home/netlogon
> ; guest ok =3D yes
> ; writable =3D no
> ; share modes =3D no
>
>
> # Un-comment the following to provide a specific roving profile share
> # the default is to use the user's home directory
> ;[Profiles]
> ; path =3D /home/profiles
> ; browseable =3D no
> ; guest ok =3D yes
>
>
> # NOTE: If you have a BSD-style print system there is no need to
> # specifically define each individual printer
> [printers]
> comment =3D All Printers
> path =3D /var/spool/samba
> browseable =3D no
> # Set public =3D yes to allow user 'guest account' to print
> guest ok =3D no
> writable =3D no
> printable =3D yes
>
> # This one is useful for people to share files
> ;[tmp]
> ; comment =3D Temporary file space
> ; path =3D /tmp
> ; read only =3D no
> ; public =3D yes
>
> # A publicly accessible directory, but read only, except for people in
> # the "staff" group
> ;[public]
> ; comment =3D Public Stuff
> ; path =3D /home/samba
> ; public =3D yes
> ; read only =3D yes
> ; write list =3D @staff
>
> # Other examples.
> #
> # A private printer, usable only by fred. Spool data will be placed in fr=
ed's
> # home directory. Note that fred must have write access to the spool dire=
ctory,
> # wherever it is.
> ;[fredsprn]
> ; comment =3D Fred's Printer
> ; valid users =3D fred
> ; path =3D /homes/fred
> ; printer =3D freds_printer
> ; public =3D no
> ; writable =3D no
> ; printable =3D yes
>
> # A private directory, usable only by fred. Note that fred requires write
> # access to the directory.
> ;[fredsdir]
> ; comment =3D Fred's Service
> ; path =3D /usr/somewhere/private
> ; valid users =3D fred
> ; public =3D no
> ; writable =3D yes
> ; printable =3D no
>
> # a service which has a different directory for each machine that connect=
s
> # this allows you to tailor configurations to incoming machines. You coul=
d
> # also use the %u option to tailor it by user name.
> # The %m gets replaced with the machine name that is connecting.
> ;[pchome]
> ; comment =3D PC Directories
> ; path =3D /usr/pc/%m
> ; public =3D no
> ; writable =3D 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 c=
ourse
> # be specified, in which case all files would be owned by that user inste=
ad.
> ;[public]
> ; path =3D /usr/somewhere/else/public
> ; public =3D yes
> ; only guest =3D yes
> ; writable =3D yes
> ; printable =3D 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. I=
n this
> # setup, the directory should be writable by both users and should have t=
he
> # sticky bit set on it to prevent abuse. Obviously this could be extended=
to
> # as many users as required.
> ;[myshare]
> ; comment =3D Mary's and Fred's stuff
> ; path =3D /usr/somewhere/shared
> ; valid users =3D mary fred
> ; public =3D no
> ; writable =3D yes
> ; printable =3D no
> ; create mask =3D 0765
>
>
> [mydir]
> comment =3D My Dir
> path =3D /
> valid users =3D myuser
> public =3D no
> writable =3D yes
> printable =3D no
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/listinfo/samba
>


--
Keep flying, and stay shiny.


--
Keep flying, and stay shiny.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba