We don't run the WINS service on our network.  We have no Win9x or
earlier clients.  All clients are Windows XP.

However, to answer your question this is what I get on the server when I
run the nmblookup

nmblookup admin1:
creating lame upcase table
creating lame lowcase table
querying admin1 on x.x.y.y
x.x.n.n admin1<00>

nmblookup <client name>:
creating lame upcase table
creating lame lowcase table
querying admin1 on x.x.y.y
x.x.a.a <client name><00>

nmblookup doesn't work on Windows XP.

Thanks again!

On Tue, 2008-10-14 at 17:19 +0200, Bruno La Torre wrote:
> I thing that you have a WINS problem.
> nmblookup admin1 on the server and client give the rigth IP?
> 
> Matthew Lind ha scritto:
> > I gave that a shot and it was a no go.  Same errors are produced.
> >
> > Thanks!
> >
> > On Mon, 2008-10-13 at 13:57 -0500, Adam Williams wrote:
> >   
> >> add in your [global] section:
> >>
> >> msdfs root = yes
> >>
> >> restart samba, and then try connecting to your shares by server name again.
> >>
> >> Matthew Lind wrote:
> >>     
> >>> Hey all,
> >>>
> >>> I've got an issue with my Samba server.  I can't seem to get file shares
> >>> to map using Server Name, but I can get them to map using IP Address. 
> >>>
> >>> Here is my smb.conf:
> >>>
> >>> [global]
> >>>   workgroup = ADMIN
> >>>   server string = Snap Server
> >>>   timestamp logs = yes
> >>>   dos filetimes = yes
> >>>   dos filemode = yes
> >>>   inherit acls = yes
> >>>   name cache timeout = 0
> >>>   winbind uid = 101-6000000
> >>>   winbind gid = 101-6000000
> >>>   local master = No
> >>>   guest account = guest
> >>>   map to guest = Never
> >>>   unix charset = CP1252
> >>>   dos charset = CP850
> >>>   allow trusted domains = no
> >>>   security = ADS
> >>>   disable netbios = no
> >>>   password server = *
> >>>   encrypt passwords = Yes
> >>>   username level = 5
> >>>   debug level = 0
> >>>   load printers = no
> >>>   utmp directory = /var/run
> >>>   utmp = yes
> >>>   name resolve order = host lmhosts wins bcast
> >>>   ldap timeout = 5
> >>>   restrict anonymous = 2
> >>>   include = /etc/smb.conf.perm
> >>>   include = /etc/smb.conf.extra
> >>>   include = /etc/smb.conf.dm
> >>>   include = /etc/smb_shares.conf
> >>>
> >>> Here is my smb_shares.conf: *Note All shares follow this format and all 
> >>> seem affected I am just truncating *
> >>> ..snip..
> >>> [bordway]
> >>> path = /shares/bordway
> >>> read only = no
> >>> comment = 
> >>> follow symlinks = no
> >>> printable = no
> >>> browseable = yes
> >>> map acl inherit = yes
> >>> create mask = 0777
> >>> security mask = 0777
> >>> directory mask = 0777
> >>> directory security mask = 0777
> >>> create mask_ext = 0777
> >>> directory mask_ext = 0777
> >>> guest ok = No
> >>> valid users = \ 
> >>>      "admin"   \  
> >>>      "ADMIN\bordway"     
> >>>
> >>> write list = \ 
> >>>       "admin"   \   
> >>>       "ADMIN\bordway"  
> >>> ..snip..
> >>>
> >>> Here is my smb.conf.perm:
> >>> panic action = /usr/bin/backtrace %d > /tmp/segv_samba_%d.out 2>&1
> >>> #  root preexec = /usr/local/samba/bin/log_connect.sh '%u' '%m' '%I' '%S'
> >>> #  root postexec = /usr/local/samba/bin/log_disconnect.sh '%u' '%m' '%I' 
> >>> '%S'
> >>>   username level = 0
> >>>  realm = ADMIN.NHTI
> >>>
> >>> smb.conf.dm and smb.conf.extra are empty.
> >>>
> >>> When a client tries to connect using the Server Name this is the error in 
> >>> the log:
> >>>
> >>> [2008/10/13 11:51:54, 0] lib/util_sock.c:get_socket_addr(926)
> >>>   getpeername failed. Error was Transport endpoint is not connected
> >>> [2008/10/13 11:51:54, 0] lib/util_sock.c:get_socket_addr(926)
> >>>   getpeername failed. Error was Transport endpoint is not connected
> >>> [2008/10/13 11:51:54, 0] lib/util_sock.c:write_socket_data(388)
> >>>   write_socket_data: write failure. Error = Connection reset by peer
> >>> [2008/10/13 11:51:54, 0] lib/util_sock.c:write_socket(413)
> >>>   write_socket: Error writing 4 bytes to socket 19: ERRNO = Connection 
> >>> reset by peer
> >>> [2008/10/13 11:51:54, 0] lib/util_sock.c:send_smb(585)
> >>>   Error writing 4 bytes to client. -1. (Connection reset by peer)
> >>> [2008/10/13 11:53:00, 0] lib/util_sock.c:get_socket_addr(926)
> >>>   getpeername failed. Error was Transport endpoint is not connected
> >>> [2008/10/13 11:53:01, 0] lib/util_sock.c:get_socket_addr(926)
> >>>   getpeername failed. Error was Transport endpoint is not connected
> >>> [2008/10/13 11:53:01, 0] lib/util_sock.c:write_socket_data(388)
> >>>   write_socket_data: write failure. Error = Connection reset by peer
> >>> [2008/10/13 11:53:01, 0] lib/util_sock.c:write_socket(413)
> >>>   write_socket: Error writing 4 bytes to socket 19: ERRNO = Connection 
> >>> reset by peer
> >>> [2008/10/13 11:53:01, 0] lib/util_sock.c:send_smb(585)
> >>>   Error writing 4 bytes to client. -1. (Connection reset by peer)
> >>>
> >>> On the Windows side if I try by name the user is presented with a Login 
> >>> Box.  When the credentials are entered the map fails.
> >>> If I try with IP no login box is presented and the mapping succeeds.
> >>>
> >>> Things I have tried:
> >>>
> >>> I have tried adding the following to smb.conf (individually and in 
> >>> combination)
> >>>
> >>> smb ports = 139
> >>> smb ports = 445
> >>> netbios name = admin1
> >>>
> >>> The clients can ping the server by name and the server can ping the 
> >>> clients by name.
> >>> The clients use the Domain Controller as their DNS server and it can map 
> >>> to the server by name.
> >>>
> >>> wbinfo -u and wbinfo -g come back with the correct group and user 
> >>> information.
> >>>
> >>> Any help would be appreciated!
> >>>
> >>> Thanks
> >>>
> >>>
> >>>
> >>>
> >>>   
> >>>       
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Reply via email to