"no se pudo montar el lugar" al intentar entrar en red de windows

Imagen de silvani67
0 puntos

Hola a todos:

He buscado durante bastante tiempo y no he encontrado la solución. He hecho lo siguiente:

- desinstalar samba y volver a instalar.Todo desde sinaptic.
- desinstalar samba desde sinaptic e instalar desde consola.

Nada.

He entrado en el directorio /etc/samba y no hay nada excepto smb.conf.ucf-dist. Nada más. No encuentro el archivo de configuracion de samba ya que muchos foros entran por ahi para resolver problemas.

En fin. A ver si me podeis ayudar.

Un saludo.

Imagen de jprdo77
+1
0
-1

Hola, mira puede ser que X motivos no te cree el fichero de configuración de samba, te sugiro que le "metas el pie"
fichero se nombra smb.conf
dentro de él, pones esto, configuraro para ti...

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# 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 most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = grupo tuyo

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# 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

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes

#### Debugging/Accounting ####

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

# Cap the size of the individual log files (in KiB).
max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d

####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
# security = user

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam

obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan < for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

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

# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups

############ Misc ############

# 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 = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
# domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
; share modes = no

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

wins support = no
[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes

# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom

+1
0
-1
Imagen de silvani67
+1
0
-1

Hola, gracias por responder.

El problema es que a pesar de que he desinstalado e instalado samba varias veces, no aparece el archivo smb ni el resto de archivos. EStá vacio.

¿Que es lo que pasa?

En fin,

Un saludo.

+1
0
-1
Imagen de Gabriel_M
+1
0
-1

1-- Archivo lmhosts
Para resolver localmente los nombres NetBIOS se los asocia con direcciones IP correspondientes, esto se hace en el archivo /etc/samba/lmhosts.

sudo gedit /etc/samba/lmhosts

En donde encontraremos lo siguiente:
127.0.0.1 localhost
Se deben añadir los nombres asociados a la dirección IP que se tenga dentro de la red local, separados con un espacio de tabulador, quedando así:

127.0.0.1 localhost
192.168.1.1 Linux
192.168.1.2 Windows

Con todas las IPs y cada uno de los nombres de los ordenadores que integran la red.

2-- Edita el archivo /etc/nsswitch.conf

sudo gedit /etc/nsswitch.conf

Busca la línea que dice
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4

Agrega wins antes de dns, para que quede asi
hosts: files mdns4_minimal [NOTFOUND=return] wins dns mdns4

3-- Cambia en smb.conf

local master = no
domain master = no

por

local master = yes
domain master = yes
preferred master = yes

+1
0
-1
Imagen de silvani67
+1
0
-1

Hola, gracias por responder.

El problema es que a pesar de que he desinstalado e instalado samba varias veces, no aparece el archivo smb ni el resto de archivos. EStá vacio.

¿Que es lo que pasa?

En fin,

Un saludo.

+1
0
-1
Imagen de Gabriel_M
+1
0
-1

En Gnu/Linux, cuando un archivo de configuración no esta
Se crea.

+1
0
-1
Imagen de silvani67
+1
0
-1

Gracias a todos.

He creado un archivo smb.conf y he pegado la configuración que jpardo77 me sugería.
La red apareció y ya he podido compartir las carpetas que he seleccionado.

Muchas gracias.

Uf. Al fin.

+1
0
-1
Imagen de jose l
+1
0
-1

Este foro ya tiene mucho tiempo, sin embargo lo leí con atención, pero no pude arreglar mi problema.
Después de horas y horas y de no encontrar el problema, trate de experimentar.
Aclaro cual era mi problema: Con virtualBox instalado en Ubuntu 11.04 e instalado windows 7 en la maquina virtual, podía ver, en está última, la red y los contenidos compartidos de Ubuntu, pero en Ubuntu no podía ver las carpetas o contenidos de win7, podía ver la red y el equipo win, pero no las carpetas compartidas. siempre el mismo letrero: "No se puede montar el lugar. Fallo al obtener la lista de compartición del servidor." Lo que encontré casi siempre se enfoco en samba, para casi todos el problema está en samba, por supuesto, hay que tener en la configuración de samba en el archivo etc/samba/smb.conf el nombre de la red el cual por defecto es WORKGROUP tanto en win como en samba, obvio esto se puede cambiar pero hay que hacerlo en ambas partes, tanto en el archivo mencionado como en la config. de grupo de trabajo en win.
El descubrimiento, que espero no sea del agua tibia. fue ir a Dispositivos de VirtualBox luego Adaptadores de Red normalmente el adaptador 1 (uno) , está habilitado y funciona la red y acceso a Internet pero no lo que nos atañe aquí. Lo que hice fue habilitar el adaptador 2 (dos) y en conectado a: escogí, Adaptador puente. en nombre: eth0 En tipo de adaptador: Intel PRO/1000 MT Desktop (82540EM) modo promiscuo: Permitir todo y habilitar la casilla: _cable conectado.
Lo anterior hay que hacerlo apagando win en la maquina virtual, luego se enciende y listo, con esto pude ver las carpetas compartidas en win desde lugares_red en Ubuntu.
Normalmente te pedirá el nombre y la contraseña. El nombre es el nombre del usuario activo en win. El grupo de trabajo debe ser el mismo en el archivo mencionado, y la contraseña es la que usa el usuario de win.
Espero que esto le sirva a alguien.

+1
0
-1
Imagen de Alexmagic
+1
0
-1

Mil gracias por el apunte, estoy muy verde en distros de Linux (uso habitualmente Ubuntu y Debian), el caso es que tengo virtualizadas ambas distros y no era capaz de poder ver el contenido de mi disco duro (tengo win 7 instalado), ahora puedo ver todo el contenido , pero con Debian no puedo acceder a la carpetas locales de mi disco duro, me sale: usuario , dominio y contraseña, ya he probado con todo lo que se me ocurre y no hay manera, alguna idea?? mil gracias

+1
0
-1
Imagen de alviarez
+1
0
-1

tengo el mismo problema pero no entiendo bien ninguna de las 2 soluciones q explican aqui si pueden volver a postearlos mas explicados por ejemplo
Para resolver localmente los nombres NetBIOS se los asocia con direcciones IP correspondientes, esto se hace en el archivo /etc/samba/lmhosts.

sudo gedit /etc/samba/lmhosts

En donde encontraremos lo siguiente:
127.0.0.1 localhost (EN EL MIO NO APARECE NADA AQUI)
Se deben añadir los nombres asociados a la dirección IP que se tenga dentro de la red local, separados con un espacio de tabulador, quedando así:

127.0.0.1 localhost
192.168.1.1 Linux (AQUI VA EL NOMBRE DE LA PC?)
192.168.1.2 Windows

o por ejemplo la otra solucion:
Dispositivos de VirtualBox luego Adaptadores de Red normalmente el adaptador 1 (uno) , está habilitado y funciona la red y acceso a Internet pero no lo que nos atañe aquí. Lo que hice fue habilitar el adaptador 2 (dos) y en conectado a: escogí, Adaptador puente. en nombre: eth0 En tipo de adaptador: Intel PRO/1000 MT Desktop (82540EM) modo promiscuo: Permitir todo y habilitar la casilla: _cable conectado.
No se como buscar virtualBox para empezar si me ayudan con esto se lo agradeceria tengo el mismo problema pero si no lo soluciono pronto me toca volver a windows

+1
0
-1