thr3ads.net - samba - [Samba] Problem Accessing Samba Server from Windows [Mar 2006]

If this information is useful, please help other people find it:
Share via:

Administrator

2006-Mar-06 00:01 UTC

[Samba] Problem Accessing Samba Server from Windows

Hi,

 

I'm having a problem accessing my samba server from Windows. The problem
occurs every time I try to browse to it on either XP or 2003 Server. The
error message I get is: "\\Zeus is not accessible. You might not have
permission to use this network resource. Contact the administrator of
this server to find out if you have access permissions. The account is
not authorized to log in from this station."

 

There are no errors in the event logs on the Windows 2003 SP1 Enterprise
server, which is the PDC. The samba server is running Mandriva 2006
PowerPack. It's running Samba 3.020 with krb 1.4.2.

 

For setting up the Samba server I followed the steps on the Samba
website to join the domain. The join went flawlessly and I can list the
users properly using wbinfo and getent.

 

The PDC is named "Paradise", the XP client is "Tama", and
the samba
server is "Zeus".

 

Here's my config files:

 

# Samba config file

 

[global]

      log file = /var/log/samba/%m.log

      ldap ssl = no

      idmap gid = 10000-20000

      wins server = 192.168.0.5

      null passwords = yes

      domain master = no

      username map = /etc/samba/smbusers

      encrypt passwords = yes

      winbind trusted domains only = no

      realm = CHU.PARADISENT.COM

      public = yes

      template shell = /bin/tcsh

      dns proxy = no

      netbios name = zeus

      netbios aliases = ZEUS Zeus

      server string = Samba Server

      printing = cups

      password server = 192.168.0.5

      idmap uid = 10000-20000

      local master = no

      workgroup = CHU

      os level = 20

      printcap name = CUPS

      security = ads

      preferred master = no

      winbind separator = |

      max log size = 50

 

[shared]

      comment = Shared Folder

      path = /shared

      ;valid users = CHU|administrator, CHU|annie, CHU|jacob,
@CHU|Household

      read only = No

 

[jacob]

      comment = Jacob's Home Dir

      path = /home/jacob

      ;valid users = CHU|jacob

      read only = No

 

[root]

      comment = Root's Home Dir

      path = /root

      ;valid users = CHU|administrator, CHU|annie, CHU|jacob,
@BUILTIN|Administrators, "@CHU|Domain Admins", "@CHU|Enterprise
Admins"

      read only = No

 

[annie]

      comment = Annie's Home Dir

      path = /home/annie

      ;valid users = CHU|annie

      read only = No

 

[website]

      comment = Main Website

      path = /var/www/html

      ;valid users = CHU|administrator, CHU|annie, CHU|jacob,
@CHU|Household

      read only = No

 

 

#

# /etc/nsswitch.conf

 

passwd:           files winbind

shadow:           files winbind

group:            files winbind

 

#hosts:     db files nisplus nis dns

hosts:      files dns winbind

 

bootparams: nisplus [NOTFOUND=return] files

 

ethers:     files

netmasks:   files

networks:   files dns

protocols:  files winbind

rpc:        files

services:   files winbind

 

netgroup:   files winbind

 

publickey:  nisplus

 

automount:  files winbind

aliases:    files nisplus

 

 

krb5.conf

 

[logging]

 default = FILE:/var/log/krb5libs.log

 kdc = FILE:/var/log/krb5kdc.log

 admin_server = FILE:/var/log/kadmind.log

 

[libdefaults]

 ticket_lifetime = 24000

 default_realm = CHU.PARADISENT.COM

 

[realms]

 CHU.PARADISENT.COM = {

  kdc = paradise.paradisent.com

  admin_server = paradise.paradisent.com

  default_domain = chu.paradisent.com

 }

 

[domain_realm]

 .kerberos.server = CHU.PARADISENT.COM

 .chu.paradisent.com = CHU.PARADISENT.COM

 chu.paradisent.com = CHU.PARADISENT.COM

 

[appdefaults]

 pam = {

   debug = false

   ticket_lifetime = 36000

   renew_lifetime = 36000

   forwardable = true

   krb4_convert = false

 }

 

 

Here is what I found in my samba server logs:

 

/var/log/messages

 

Mar  5 10:24:57 zeus smbd[5099]: [2006/03/05 10:24:57, 0]
lib/util_sock.c:get_peer_addr(1222) 

Mar  5 10:24:57 zeus smbd[5099]:   getpeername failed. Error was
Transport endpoint is not connected 

Mar  5 10:24:57 zeus smbd[19273]: [2006/03/05 10:24:57, 0]
lib/util_sock.c:get_peer_addr(1222) 

Mar  5 10:24:57 zeus smbd[19273]:   getpeername failed. Error was
Transport endpoint is not connected 

Mar  5 10:24:57 zeus smbd[19273]: [2006/03/05 10:24:57, 0]
lib/util_sock.c:write_data(554) 

Mar  5 10:24:57 zeus smbd[19273]:   write_data: write failure in writing
to client 0.0.0.0. Error Connection reset by peer 

Mar  5 10:24:57 zeus smbd[19273]: [2006/03/05 10:24:57, 0]
lib/util_sock.c:send_smb(762) 

Mar  5 10:24:57 zeus smbd[19273]:   Error writing 4 bytes to client. -1.
(Connection reset by peer) 

Mar  5 10:24:57 zeus smbd[5099]: [2006/03/05 10:24:57, 0]
lib/util_sock.c:get_peer_addr(1222) 

Mar  5 10:24:57 zeus smbd[5099]:   getpeername failed. Error was
Transport endpoint is not connected 

Mar  5 10:24:57 zeus smbd[19276]: [2006/03/05 10:24:57, 0]
lib/util_sock.c:get_peer_addr(1222) 

Mar  5 10:24:57 zeus smbd[19276]:   getpeername failed. Error was
Transport endpoint is not connected 

Mar  5 10:24:57 zeus smbd[19276]: [2006/03/05 10:24:57, 0]
lib/util_sock.c:write_data(554) 

Mar  5 10:24:57 zeus smbd[19276]:   write_data: write failure in writing
to client 0.0.0.0. Error Connection reset by peer 

Mar  5 10:24:57 zeus smbd[19276]: [2006/03/05 10:24:57, 0]
lib/util_sock.c:send_smb(762) 

Mar  5 10:24:57 zeus smbd[19276]:   Error writing 4 bytes to client. -1.
(Connection reset by peer) 

Mar  5 10:59:52 zeus smbd[5099]: [2006/03/05 10:59:52, 0]
lib/util_sock.c:get_peer_addr(1222) 

Mar  5 10:59:52 zeus smbd[5099]:   getpeername failed. Error was
Transport endpoint is not connected 

Mar  5 10:59:52 zeus smbd[19280]: [2006/03/05 10:59:52, 0]
lib/util_sock.c:get_peer_addr(1222) 

Mar  5 10:59:52 zeus smbd[19280]:   getpeername failed. Error was
Transport endpoint is not connected 

Mar  5 10:59:52 zeus smbd[19280]: [2006/03/05 10:59:52, 0]
lib/util_sock.c:write_data(554) 

Mar  5 10:59:52 zeus smbd[19280]:   write_data: write failure in writing
to client 0.0.0.0. Error Connection reset by peer 

Mar  5 10:59:52 zeus smbd[19280]: [2006/03/05 10:59:52, 0]
lib/util_sock.c:send_smb(762) 

Mar  5 10:59:52 zeus smbd[19280]:   Error writing 4 bytes to client. -1.
(Connection reset by peer) 

 

 

log.nmbd

 

[2006/03/05 04:02:04, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(284)

  dump_workgroups()

   dump workgroup on subnet    192.168.0.20: netmask=  255.255.255.0:

      CHU(1) current master browser = PARADISE

            ZEUS 40009b03 (Samba Server)

            PARADISE 4084122b ()

[2006/03/05 04:02:04, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(284)

  dump_workgroups()

   dump workgroup on subnet  UNICAST_SUBNET: netmask=        0.0.0.0:

      CHU(1) current master browser = UNKNOWN

            ZEUS 40009b03 (Samba Server)

 

Log.wb-CHU

 

[2006/03/05 00:32:30, 0] lib/util_sock.c:write_data(556)

  write_data: write failure. Error = Connection reset by peer

[2006/03/05 00:32:30, 0] libsmb/clientgen.c:write_socket(138)

  write_socket: Error writing 190 bytes to socket 3: ERRNO = Connection
reset by peer

[2006/03/05 00:32:30, 0] libsmb/clientgen.c:cli_send_smb(168)

  Error writing 190 bytes to client. -1 (Connection reset by peer)

[2006/03/05 00:32:30, 0] rpc_client/cli_pipe.c:rpc_api_pipe(438)

  cli_pipe: return critical error. Error was Write error: Connection
reset by peer

[2006/03/05 00:37:30, 0] rpc_client/cli_pipe.c:cli_rpc_close(1767)

  cli_rpc_open failed on pipe \NETLOGON to machine PARADISE.  Error was
Write error: Connection reset by peer

[2006/03/05 00:37:30, 0] rpc_client/cli_pipe.c:cli_rpc_close(1767)

  cli_rpc_open failed on pipe \NETLOGON to machine PARADISE.  Error was
Write error: Connection reset by peer

[2006/03/05 01:08:00, 0] lib/util_sock.c:write_data(556)

  write_data: write failure. Error = Connection reset by peer

[2006/03/05 01:08:00, 0] libsmb/clientgen.c:write_socket(138)

  write_socket: Error writing 190 bytes to socket 3: ERRNO = Connection
reset by peer

[2006/03/05 01:08:00, 0] libsmb/clientgen.c:cli_send_smb(168)

  Error writing 190 bytes to client. -1 (Connection reset by peer)

[2006/03/05 01:08:00, 0] rpc_client/cli_pipe.c:rpc_api_pipe(438)

  cli_pipe: return critical error. Error was Write error: Connection
reset by peer

[2006/03/05 01:10:34, 0] rpc_client/cli_pipe.c:cli_rpc_open_noauth(1700)

  rpc_pipe_bind failed

 

 

paradise.log

 

[2006/03/04 23:54:45, 0] lib/util_sock.c:write_data(554)

  write_data: write failure in writing to client 192.168.0.5. Error
Connection reset by peer

[2006/03/04 23:54:45, 0] lib/util_sock.c:send_smb(762)

  Error writing 4 bytes to client. -1. (Connection reset by peer)

[2006/03/05 10:59:52, 0] lib/util_sock.c:write_data(554)

  write_data: write failure in writing to client 0.0.0.0. Error
Connection reset by peer

[2006/03/05 10:59:52, 0] lib/util_sock.c:send_smb(762)

  Error writing 4 bytes to client. -1. (Connection reset by peer)

 

 

Smbd.log

 

[2006/03/05 04:02:04, 1] smbd/server.c:open_sockets_smbd(354)

  Reloading services after SIGHUP

[2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)

  getpeername failed. Error was Transport endpoint is not connected

[2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)

  getpeername failed. Error was Transport endpoint is not connected

[2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)

  getpeername failed. Error was Transport endpoint is not connected

[2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)

  getpeername failed. Error was Transport endpoint is not connected

[2006/03/05 10:59:52, 0] lib/util_sock.c:get_peer_addr(1222)

  getpeername failed. Error was Transport endpoint is not connected

[2006/03/05 10:59:52, 0] lib/util_sock.c:get_peer_addr(1222)

  getpeername failed. Error was Transport endpoint is not connected

 

 

tama.log

 

[2006/03/04 22:22:39, 0] lib/util_sock.c:write_data(554)

  write_data: write failure in writing to client 0.0.0.0. Error
Connection reset by peer

[2006/03/04 22:22:39, 0] lib/util_sock.c:send_smb(762)

  Error writing 4 bytes to client. -1. (Connection reset by peer)

[2006/03/05 01:19:57, 0] lib/util_sock.c:write_data(554)

  write_data: write failure in writing to client 192.168.0.15. Error
Connection reset by peer

[2006/03/05 01:19:57, 0] lib/util_sock.c:send_smb(762)

  Error writing 4 bytes to client. -1. (Connection reset by peer)

[2006/03/05 10:24:57, 0] lib/util_sock.c:write_data(554)

  write_data: write failure in writing to client 0.0.0.0. Error
Connection reset by peer

[2006/03/05 10:24:57, 0] lib/util_sock.c:send_smb(762)

  Error writing 4 bytes to client. -1. (Connection reset by peer)

[2006/03/05 10:24:57, 0] lib/util_sock.c:write_data(554)

  write_data: write failure in writing to client 0.0.0.0. Error
Connection reset by peer

[2006/03/05 10:24:57, 0] lib/util_sock.c:send_smb(762)

  Error writing 4 bytes to client. -1. (Connection reset by peer)

 

 

Any help would be greatly appreciated!

 

Thanks,

 

Jacob.

Jörg Nissen

2006-Mar-06 08:22 UTC

head link

[Samba] Problem Accessing Samba Server from Windows

I'm not quite sure about this but I miss the IPC section in your smb.conf. 
It should be similar to this:

[IPC$]
    path = /tmp
    guest ok = yes
    valid users     hosts allow = 127.0.0.1, your.IP.subnet


MfG
J?rg Nissen
----- Original Message ----- 
From: ""Administrator"" <Administrator@paradisent.com>
Newsgroups: mailing.unix.samba
Sent: Monday, March 06, 2006 1:09 AM
Subject: [Samba] Problem Accessing Samba Server from Windows

> Hi,
>
> =20
>
> I'm having a problem accessing my samba server from Windows. The
problem
> occurs every time I try to browse to it on either XP or 2003 Server. The
> error message I get is: "\\Zeus is not accessible. You might not have
> permission to use this network resource. Contact the administrator of
> this server to find out if you have access permissions. The account is
> not authorized to log in from this station."
>
> =20
>
> There are no errors in the event logs on the Windows 2003 SP1 Enterprise
> server, which is the PDC. The samba server is running Mandriva 2006
> PowerPack. It's running Samba 3.020 with krb 1.4.2.
>
> =20
>
> For setting up the Samba server I followed the steps on the Samba
> website to join the domain. The join went flawlessly and I can list the
> users properly using wbinfo and getent.
>
> =20
>
> The PDC is named "Paradise", the XP client is "Tama",
and the samba
> server is "Zeus".
>
> =20
>
> Here's my config files:
>
> =20
>
> # Samba config file
>
> =20
>
> [global]
>
>      log file =3D /var/log/samba/%m.log
>
>      ldap ssl =3D no
>
>      idmap gid =3D 10000-20000
>
>      wins server =3D 192.168.0.5
>
>      null passwords =3D yes
>
>      domain master =3D no
>
>      username map =3D /etc/samba/smbusers
>
>      encrypt passwords =3D yes
>
>      winbind trusted domains only =3D no
>
>      realm =3D CHU.PARADISENT.COM
>
>      public =3D yes
>
>      template shell =3D /bin/tcsh
>
>      dns proxy =3D no
>
>      netbios name =3D zeus
>
>      netbios aliases =3D ZEUS Zeus
>
>      server string =3D Samba Server
>
>      printing =3D cups
>
>      password server =3D 192.168.0.5
>
>      idmap uid =3D 10000-20000
>
>      local master =3D no
>
>      workgroup =3D CHU
>
>      os level =3D 20
>
>      printcap name =3D CUPS
>
>      security =3D ads
>
>      preferred master =3D no
>
>      winbind separator =3D |
>
>      max log size =3D 50
>
> =20
>
> [shared]
>
>      comment =3D Shared Folder
>
>      path =3D /shared
>
>      ;valid users =3D CHU|administrator, CHU|annie, CHU|jacob,
> @CHU|Household
>
>      read only =3D No
>
> =20
>
> [jacob]
>
>      comment =3D Jacob's Home Dir
>
>      path =3D /home/jacob
>
>      ;valid users =3D CHU|jacob
>
>      read only =3D No
>
> =20
>
> [root]
>
>      comment =3D Root's Home Dir
>
>      path =3D /root
>
>      ;valid users =3D CHU|administrator, CHU|annie, CHU|jacob,
> @BUILTIN|Administrators, "@CHU|Domain Admins",
"@CHU|Enterprise Admins"
>
>      read only =3D No
>
> =20
>
> [annie]
>
>      comment =3D Annie's Home Dir
>
>      path =3D /home/annie
>
>      ;valid users =3D CHU|annie
>
>      read only =3D No
>
> =20
>
> [website]
>
>      comment =3D Main Website
>
>      path =3D /var/www/html
>
>      ;valid users =3D CHU|administrator, CHU|annie, CHU|jacob,
> @CHU|Household
>
>      read only =3D No
>
> =20
>
> =20
>
> #
>
> # /etc/nsswitch.conf
>
> =20
>
> passwd:           files winbind
>
> shadow:           files winbind
>
> group:            files winbind
>
> =20
>
> #hosts:     db files nisplus nis dns
>
> hosts:      files dns winbind
>
> =20
>
> bootparams: nisplus [NOTFOUND=3Dreturn] files
>
> =20
>
> ethers:     files
>
> netmasks:   files
>
> networks:   files dns
>
> protocols:  files winbind
>
> rpc:        files
>
> services:   files winbind
>
> =20
>
> netgroup:   files winbind
>
> =20
>
> publickey:  nisplus
>
> =20
>
> automount:  files winbind
>
> aliases:    files nisplus
>
> =20
>
> =20
>
> krb5.conf
>
> =20
>
> [logging]
>
> default =3D FILE:/var/log/krb5libs.log
>
> kdc =3D FILE:/var/log/krb5kdc.log
>
> admin_server =3D FILE:/var/log/kadmind.log
>
> =20
>
> [libdefaults]
>
> ticket_lifetime =3D 24000
>
> default_realm =3D CHU.PARADISENT.COM
>
> =20
>
> [realms]
>
> CHU.PARADISENT.COM =3D {
>
>  kdc =3D paradise.paradisent.com
>
>  admin_server =3D paradise.paradisent.com
>
>  default_domain =3D chu.paradisent.com
>
> }
>
> =20
>
> [domain_realm]
>
> .kerberos.server =3D CHU.PARADISENT.COM
>
> .chu.paradisent.com =3D CHU.PARADISENT.COM
>
> chu.paradisent.com =3D CHU.PARADISENT.COM
>
> =20
>
> [appdefaults]
>
> pam =3D {
>
>   debug =3D false
>
>   ticket_lifetime =3D 36000
>
>   renew_lifetime =3D 36000
>
>   forwardable =3D true
>
>   krb4_convert =3D false
>
> }
>
> =20
>
> =20
>
> Here is what I found in my samba server logs:
>
> =20
>
> /var/log/messages
>
> =20
>
> Mar  5 10:24:57 zeus smbd[5099]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:get_peer_addr(1222)=20
>
> Mar  5 10:24:57 zeus smbd[5099]:   getpeername failed. Error was
> Transport endpoint is not connected=20
>
> Mar  5 10:24:57 zeus smbd[19273]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:get_peer_addr(1222)=20
>
> Mar  5 10:24:57 zeus smbd[19273]:   getpeername failed. Error was
> Transport endpoint is not connected=20
>
> Mar  5 10:24:57 zeus smbd[19273]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:write_data(554)=20
>
> Mar  5 10:24:57 zeus smbd[19273]:   write_data: write failure in writing
> to client 0.0.0.0. Error Connection reset by peer=20
>
> Mar  5 10:24:57 zeus smbd[19273]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:send_smb(762)=20
>
> Mar  5 10:24:57 zeus smbd[19273]:   Error writing 4 bytes to client. -1.
> (Connection reset by peer)=20
>
> Mar  5 10:24:57 zeus smbd[5099]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:get_peer_addr(1222)=20
>
> Mar  5 10:24:57 zeus smbd[5099]:   getpeername failed. Error was
> Transport endpoint is not connected=20
>
> Mar  5 10:24:57 zeus smbd[19276]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:get_peer_addr(1222)=20
>
> Mar  5 10:24:57 zeus smbd[19276]:   getpeername failed. Error was
> Transport endpoint is not connected=20
>
> Mar  5 10:24:57 zeus smbd[19276]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:write_data(554)=20
>
> Mar  5 10:24:57 zeus smbd[19276]:   write_data: write failure in writing
> to client 0.0.0.0. Error Connection reset by peer=20
>
> Mar  5 10:24:57 zeus smbd[19276]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:send_smb(762)=20
>
> Mar  5 10:24:57 zeus smbd[19276]:   Error writing 4 bytes to client. -1.
> (Connection reset by peer)=20
>
> Mar  5 10:59:52 zeus smbd[5099]: [2006/03/05 10:59:52, 0]
> lib/util_sock.c:get_peer_addr(1222)=20
>
> Mar  5 10:59:52 zeus smbd[5099]:   getpeername failed. Error was
> Transport endpoint is not connected=20
>
> Mar  5 10:59:52 zeus smbd[19280]: [2006/03/05 10:59:52, 0]
> lib/util_sock.c:get_peer_addr(1222)=20
>
> Mar  5 10:59:52 zeus smbd[19280]:   getpeername failed. Error was
> Transport endpoint is not connected=20
>
> Mar  5 10:59:52 zeus smbd[19280]: [2006/03/05 10:59:52, 0]
> lib/util_sock.c:write_data(554)=20
>
> Mar  5 10:59:52 zeus smbd[19280]:   write_data: write failure in writing
> to client 0.0.0.0. Error Connection reset by peer=20
>
> Mar  5 10:59:52 zeus smbd[19280]: [2006/03/05 10:59:52, 0]
> lib/util_sock.c:send_smb(762)=20
>
> Mar  5 10:59:52 zeus smbd[19280]:   Error writing 4 bytes to client. -1.
> (Connection reset by peer)=20
>
> =20
>
> =20
>
> log.nmbd
>
> =20
>
> [2006/03/05 04:02:04, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(284)
>
>  dump_workgroups()
>
>   dump workgroup on subnet    192.168.0.20: netmask=3D  255.255.255.0:
>
>      CHU(1) current master browser =3D PARADISE
>
>            ZEUS 40009b03 (Samba Server)
>
>            PARADISE 4084122b ()
>
> [2006/03/05 04:02:04, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(284)
>
>  dump_workgroups()
>
>   dump workgroup on subnet  UNICAST_SUBNET: netmask=3D        0.0.0.0:
>
>      CHU(1) current master browser =3D UNKNOWN
>
>            ZEUS 40009b03 (Samba Server)
>
> =20
>
> Log.wb-CHU
>
> =20
>
> [2006/03/05 00:32:30, 0] lib/util_sock.c:write_data(556)
>
>  write_data: write failure. Error =3D Connection reset by peer
>
> [2006/03/05 00:32:30, 0] libsmb/clientgen.c:write_socket(138)
>
>  write_socket: Error writing 190 bytes to socket 3: ERRNO =3D >
Connection
> reset by peer
>
> [2006/03/05 00:32:30, 0] libsmb/clientgen.c:cli_send_smb(168)
>
>  Error writing 190 bytes to client. -1 (Connection reset by peer)
>
> [2006/03/05 00:32:30, 0] rpc_client/cli_pipe.c:rpc_api_pipe(438)
>
>  cli_pipe: return critical error. Error was Write error: Connection
> reset by peer
>
> [2006/03/05 00:37:30, 0] rpc_client/cli_pipe.c:cli_rpc_close(1767)
>
>  cli_rpc_open failed on pipe \NETLOGON to machine PARADISE.  Error was
> Write error: Connection reset by peer
>
> [2006/03/05 00:37:30, 0] rpc_client/cli_pipe.c:cli_rpc_close(1767)
>
>  cli_rpc_open failed on pipe \NETLOGON to machine PARADISE.  Error was
> Write error: Connection reset by peer
>
> [2006/03/05 01:08:00, 0] lib/util_sock.c:write_data(556)
>
>  write_data: write failure. Error =3D Connection reset by peer
>
> [2006/03/05 01:08:00, 0] libsmb/clientgen.c:write_socket(138)
>
>  write_socket: Error writing 190 bytes to socket 3: ERRNO =3D >
Connection
> reset by peer
>
> [2006/03/05 01:08:00, 0] libsmb/clientgen.c:cli_send_smb(168)
>
>  Error writing 190 bytes to client. -1 (Connection reset by peer)
>
> [2006/03/05 01:08:00, 0] rpc_client/cli_pipe.c:rpc_api_pipe(438)
>
>  cli_pipe: return critical error. Error was Write error: Connection
> reset by peer
>
> [2006/03/05 01:10:34, 0] rpc_client/cli_pipe.c:cli_rpc_open_noauth(1700)
>
>  rpc_pipe_bind failed
>
> =20
>
> =20
>
> paradise.log
>
> =20
>
> [2006/03/04 23:54:45, 0] lib/util_sock.c:write_data(554)
>
>  write_data: write failure in writing to client 192.168.0.5. Error
> Connection reset by peer
>
> [2006/03/04 23:54:45, 0] lib/util_sock.c:send_smb(762)
>
>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>
> [2006/03/05 10:59:52, 0] lib/util_sock.c:write_data(554)
>
>  write_data: write failure in writing to client 0.0.0.0. Error
> Connection reset by peer
>
> [2006/03/05 10:59:52, 0] lib/util_sock.c:send_smb(762)
>
>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>
> =20
>
> =20
>
> Smbd.log
>
> =20
>
> [2006/03/05 04:02:04, 1] smbd/server.c:open_sockets_smbd(354)
>
>  Reloading services after SIGHUP
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)
>
>  getpeername failed. Error was Transport endpoint is not connected
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)
>
>  getpeername failed. Error was Transport endpoint is not connected
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)
>
>  getpeername failed. Error was Transport endpoint is not connected
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)
>
>  getpeername failed. Error was Transport endpoint is not connected
>
> [2006/03/05 10:59:52, 0] lib/util_sock.c:get_peer_addr(1222)
>
>  getpeername failed. Error was Transport endpoint is not connected
>
> [2006/03/05 10:59:52, 0] lib/util_sock.c:get_peer_addr(1222)
>
>  getpeername failed. Error was Transport endpoint is not connected
>
> =20
>
> =20
>
> tama.log
>
> =20
>
> [2006/03/04 22:22:39, 0] lib/util_sock.c:write_data(554)
>
>  write_data: write failure in writing to client 0.0.0.0. Error
> Connection reset by peer
>
> [2006/03/04 22:22:39, 0] lib/util_sock.c:send_smb(762)
>
>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>
> [2006/03/05 01:19:57, 0] lib/util_sock.c:write_data(554)
>
>  write_data: write failure in writing to client 192.168.0.15. Error
> Connection reset by peer
>
> [2006/03/05 01:19:57, 0] lib/util_sock.c:send_smb(762)
>
>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:write_data(554)
>
>  write_data: write failure in writing to client 0.0.0.0. Error
> Connection reset by peer
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:send_smb(762)
>
>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:write_data(554)
>
>  write_data: write failure in writing to client 0.0.0.0. Error
> Connection reset by peer
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:send_smb(762)
>
>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>
> =20
>
> =20
>
> Any help would be greatly appreciated!
>
> =20
>
> Thanks,
>
> =20
>
> Jacob.
>
> =20
>
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba

Administrator

2006-Mar-12 21:31 UTC

head link

[Samba] Problem Accessing Samba Server from Windows

I tried adding that to my smb.conf. What's the proper syntax for the hosts
allow bit? My subnet is 192.168.0.X. I tried putting 192.168.0 and 192.168.0.
but none of those helped. I just listed all my IP's and that didn't
solve the problem either. Any other ideas?

Thank,

Jake.

-----Original Message-----
From: J?rg Nissen [mailto:joenis@arcor.de] 
Sent: Monday, March 06, 2006 12:22 AM
To: samba@lists.samba.org
Subject: Re: [Samba] Problem Accessing Samba Server from Windows

I'm not quite sure about this but I miss the IPC section in your smb.conf. 
It should be similar to this:

[IPC$]
    path = /tmp
    guest ok = yes
    valid users     hosts allow = 127.0.0.1, your.IP.subnet


MfG
J?rg Nissen
----- Original Message ----- 
From: ""Administrator"" <Administrator@paradisent.com>
Newsgroups: mailing.unix.samba
Sent: Monday, March 06, 2006 1:09 AM
Subject: [Samba] Problem Accessing Samba Server from Windows

> Hi,
>
> =20
>
> I'm having a problem accessing my samba server from Windows. The
problem
> occurs every time I try to browse to it on either XP or 2003 Server. The
> error message I get is: "\\Zeus is not accessible. You might not have
> permission to use this network resource. Contact the administrator of
> this server to find out if you have access permissions. The account is
> not authorized to log in from this station."
>
> =20
>
> There are no errors in the event logs on the Windows 2003 SP1 Enterprise
> server, which is the PDC. The samba server is running Mandriva 2006
> PowerPack. It's running Samba 3.020 with krb 1.4.2.
>
> =20
>
> For setting up the Samba server I followed the steps on the Samba
> website to join the domain. The join went flawlessly and I can list the
> users properly using wbinfo and getent.
>
> =20
>
> The PDC is named "Paradise", the XP client is "Tama",
and the samba
> server is "Zeus".
>
> =20
>
> Here's my config files:
>
> =20
>
> # Samba config file
>
> =20
>
> [global]
>
>      log file =3D /var/log/samba/%m.log
>
>      ldap ssl =3D no
>
>      idmap gid =3D 10000-20000
>
>      wins server =3D 192.168.0.5
>
>      null passwords =3D yes
>
>      domain master =3D no
>
>      username map =3D /etc/samba/smbusers
>
>      encrypt passwords =3D yes
>
>      winbind trusted domains only =3D no
>
>      realm =3D CHU.PARADISENT.COM
>
>      public =3D yes
>
>      template shell =3D /bin/tcsh
>
>      dns proxy =3D no
>
>      netbios name =3D zeus
>
>      netbios aliases =3D ZEUS Zeus
>
>      server string =3D Samba Server
>
>      printing =3D cups
>
>      password server =3D 192.168.0.5
>
>      idmap uid =3D 10000-20000
>
>      local master =3D no
>
>      workgroup =3D CHU
>
>      os level =3D 20
>
>      printcap name =3D CUPS
>
>      security =3D ads
>
>      preferred master =3D no
>
>      winbind separator =3D |
>
>      max log size =3D 50
>
> =20
>
> [shared]
>
>      comment =3D Shared Folder
>
>      path =3D /shared
>
>      ;valid users =3D CHU|administrator, CHU|annie, CHU|jacob,
> @CHU|Household
>
>      read only =3D No
>
> =20
>
> [jacob]
>
>      comment =3D Jacob's Home Dir
>
>      path =3D /home/jacob
>
>      ;valid users =3D CHU|jacob
>
>      read only =3D No
>
> =20
>
> [root]
>
>      comment =3D Root's Home Dir
>
>      path =3D /root
>
>      ;valid users =3D CHU|administrator, CHU|annie, CHU|jacob,
> @BUILTIN|Administrators, "@CHU|Domain Admins",
"@CHU|Enterprise Admins"
>
>      read only =3D No
>
> =20
>
> [annie]
>
>      comment =3D Annie's Home Dir
>
>      path =3D /home/annie
>
>      ;valid users =3D CHU|annie
>
>      read only =3D No
>
> =20
>
> [website]
>
>      comment =3D Main Website
>
>      path =3D /var/www/html
>
>      ;valid users =3D CHU|administrator, CHU|annie, CHU|jacob,
> @CHU|Household
>
>      read only =3D No
>
> =20
>
> =20
>
> #
>
> # /etc/nsswitch.conf
>
> =20
>
> passwd:           files winbind
>
> shadow:           files winbind
>
> group:            files winbind
>
> =20
>
> #hosts:     db files nisplus nis dns
>
> hosts:      files dns winbind
>
> =20
>
> bootparams: nisplus [NOTFOUND=3Dreturn] files
>
> =20
>
> ethers:     files
>
> netmasks:   files
>
> networks:   files dns
>
> protocols:  files winbind
>
> rpc:        files
>
> services:   files winbind
>
> =20
>
> netgroup:   files winbind
>
> =20
>
> publickey:  nisplus
>
> =20
>
> automount:  files winbind
>
> aliases:    files nisplus
>
> =20
>
> =20
>
> krb5.conf
>
> =20
>
> [logging]
>
> default =3D FILE:/var/log/krb5libs.log
>
> kdc =3D FILE:/var/log/krb5kdc.log
>
> admin_server =3D FILE:/var/log/kadmind.log
>
> =20
>
> [libdefaults]
>
> ticket_lifetime =3D 24000
>
> default_realm =3D CHU.PARADISENT.COM
>
> =20
>
> [realms]
>
> CHU.PARADISENT.COM =3D {
>
>  kdc =3D paradise.paradisent.com
>
>  admin_server =3D paradise.paradisent.com
>
>  default_domain =3D chu.paradisent.com
>
> }
>
> =20
>
> [domain_realm]
>
> .kerberos.server =3D CHU.PARADISENT.COM
>
> .chu.paradisent.com =3D CHU.PARADISENT.COM
>
> chu.paradisent.com =3D CHU.PARADISENT.COM
>
> =20
>
> [appdefaults]
>
> pam =3D {
>
>   debug =3D false
>
>   ticket_lifetime =3D 36000
>
>   renew_lifetime =3D 36000
>
>   forwardable =3D true
>
>   krb4_convert =3D false
>
> }
>
> =20
>
> =20
>
> Here is what I found in my samba server logs:
>
> =20
>
> /var/log/messages
>
> =20
>
> Mar  5 10:24:57 zeus smbd[5099]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:get_peer_addr(1222)=20
>
> Mar  5 10:24:57 zeus smbd[5099]:   getpeername failed. Error was
> Transport endpoint is not connected=20
>
> Mar  5 10:24:57 zeus smbd[19273]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:get_peer_addr(1222)=20
>
> Mar  5 10:24:57 zeus smbd[19273]:   getpeername failed. Error was
> Transport endpoint is not connected=20
>
> Mar  5 10:24:57 zeus smbd[19273]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:write_data(554)=20
>
> Mar  5 10:24:57 zeus smbd[19273]:   write_data: write failure in writing
> to client 0.0.0.0. Error Connection reset by peer=20
>
> Mar  5 10:24:57 zeus smbd[19273]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:send_smb(762)=20
>
> Mar  5 10:24:57 zeus smbd[19273]:   Error writing 4 bytes to client. -1.
> (Connection reset by peer)=20
>
> Mar  5 10:24:57 zeus smbd[5099]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:get_peer_addr(1222)=20
>
> Mar  5 10:24:57 zeus smbd[5099]:   getpeername failed. Error was
> Transport endpoint is not connected=20
>
> Mar  5 10:24:57 zeus smbd[19276]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:get_peer_addr(1222)=20
>
> Mar  5 10:24:57 zeus smbd[19276]:   getpeername failed. Error was
> Transport endpoint is not connected=20
>
> Mar  5 10:24:57 zeus smbd[19276]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:write_data(554)=20
>
> Mar  5 10:24:57 zeus smbd[19276]:   write_data: write failure in writing
> to client 0.0.0.0. Error Connection reset by peer=20
>
> Mar  5 10:24:57 zeus smbd[19276]: [2006/03/05 10:24:57, 0]
> lib/util_sock.c:send_smb(762)=20
>
> Mar  5 10:24:57 zeus smbd[19276]:   Error writing 4 bytes to client. -1.
> (Connection reset by peer)=20
>
> Mar  5 10:59:52 zeus smbd[5099]: [2006/03/05 10:59:52, 0]
> lib/util_sock.c:get_peer_addr(1222)=20
>
> Mar  5 10:59:52 zeus smbd[5099]:   getpeername failed. Error was
> Transport endpoint is not connected=20
>
> Mar  5 10:59:52 zeus smbd[19280]: [2006/03/05 10:59:52, 0]
> lib/util_sock.c:get_peer_addr(1222)=20
>
> Mar  5 10:59:52 zeus smbd[19280]:   getpeername failed. Error was
> Transport endpoint is not connected=20
>
> Mar  5 10:59:52 zeus smbd[19280]: [2006/03/05 10:59:52, 0]
> lib/util_sock.c:write_data(554)=20
>
> Mar  5 10:59:52 zeus smbd[19280]:   write_data: write failure in writing
> to client 0.0.0.0. Error Connection reset by peer=20
>
> Mar  5 10:59:52 zeus smbd[19280]: [2006/03/05 10:59:52, 0]
> lib/util_sock.c:send_smb(762)=20
>
> Mar  5 10:59:52 zeus smbd[19280]:   Error writing 4 bytes to client. -1.
> (Connection reset by peer)=20
>
> =20
>
> =20
>
> log.nmbd
>
> =20
>
> [2006/03/05 04:02:04, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(284)
>
>  dump_workgroups()
>
>   dump workgroup on subnet    192.168.0.20: netmask=3D  255.255.255.0:
>
>      CHU(1) current master browser =3D PARADISE
>
>            ZEUS 40009b03 (Samba Server)
>
>            PARADISE 4084122b ()
>
> [2006/03/05 04:02:04, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(284)
>
>  dump_workgroups()
>
>   dump workgroup on subnet  UNICAST_SUBNET: netmask=3D        0.0.0.0:
>
>      CHU(1) current master browser =3D UNKNOWN
>
>            ZEUS 40009b03 (Samba Server)
>
> =20
>
> Log.wb-CHU
>
> =20
>
> [2006/03/05 00:32:30, 0] lib/util_sock.c:write_data(556)
>
>  write_data: write failure. Error =3D Connection reset by peer
>
> [2006/03/05 00:32:30, 0] libsmb/clientgen.c:write_socket(138)
>
>  write_socket: Error writing 190 bytes to socket 3: ERRNO =3D >
Connection
> reset by peer
>
> [2006/03/05 00:32:30, 0] libsmb/clientgen.c:cli_send_smb(168)
>
>  Error writing 190 bytes to client. -1 (Connection reset by peer)
>
> [2006/03/05 00:32:30, 0] rpc_client/cli_pipe.c:rpc_api_pipe(438)
>
>  cli_pipe: return critical error. Error was Write error: Connection
> reset by peer
>
> [2006/03/05 00:37:30, 0] rpc_client/cli_pipe.c:cli_rpc_close(1767)
>
>  cli_rpc_open failed on pipe \NETLOGON to machine PARADISE.  Error was
> Write error: Connection reset by peer
>
> [2006/03/05 00:37:30, 0] rpc_client/cli_pipe.c:cli_rpc_close(1767)
>
>  cli_rpc_open failed on pipe \NETLOGON to machine PARADISE.  Error was
> Write error: Connection reset by peer
>
> [2006/03/05 01:08:00, 0] lib/util_sock.c:write_data(556)
>
>  write_data: write failure. Error =3D Connection reset by peer
>
> [2006/03/05 01:08:00, 0] libsmb/clientgen.c:write_socket(138)
>
>  write_socket: Error writing 190 bytes to socket 3: ERRNO =3D >
Connection
> reset by peer
>
> [2006/03/05 01:08:00, 0] libsmb/clientgen.c:cli_send_smb(168)
>
>  Error writing 190 bytes to client. -1 (Connection reset by peer)
>
> [2006/03/05 01:08:00, 0] rpc_client/cli_pipe.c:rpc_api_pipe(438)
>
>  cli_pipe: return critical error. Error was Write error: Connection
> reset by peer
>
> [2006/03/05 01:10:34, 0] rpc_client/cli_pipe.c:cli_rpc_open_noauth(1700)
>
>  rpc_pipe_bind failed
>
> =20
>
> =20
>
> paradise.log
>
> =20
>
> [2006/03/04 23:54:45, 0] lib/util_sock.c:write_data(554)
>
>  write_data: write failure in writing to client 192.168.0.5. Error
> Connection reset by peer
>
> [2006/03/04 23:54:45, 0] lib/util_sock.c:send_smb(762)
>
>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>
> [2006/03/05 10:59:52, 0] lib/util_sock.c:write_data(554)
>
>  write_data: write failure in writing to client 0.0.0.0. Error
> Connection reset by peer
>
> [2006/03/05 10:59:52, 0] lib/util_sock.c:send_smb(762)
>
>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>
> =20
>
> =20
>
> Smbd.log
>
> =20
>
> [2006/03/05 04:02:04, 1] smbd/server.c:open_sockets_smbd(354)
>
>  Reloading services after SIGHUP
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)
>
>  getpeername failed. Error was Transport endpoint is not connected
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)
>
>  getpeername failed. Error was Transport endpoint is not connected
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)
>
>  getpeername failed. Error was Transport endpoint is not connected
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)
>
>  getpeername failed. Error was Transport endpoint is not connected
>
> [2006/03/05 10:59:52, 0] lib/util_sock.c:get_peer_addr(1222)
>
>  getpeername failed. Error was Transport endpoint is not connected
>
> [2006/03/05 10:59:52, 0] lib/util_sock.c:get_peer_addr(1222)
>
>  getpeername failed. Error was Transport endpoint is not connected
>
> =20
>
> =20
>
> tama.log
>
> =20
>
> [2006/03/04 22:22:39, 0] lib/util_sock.c:write_data(554)
>
>  write_data: write failure in writing to client 0.0.0.0. Error
> Connection reset by peer
>
> [2006/03/04 22:22:39, 0] lib/util_sock.c:send_smb(762)
>
>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>
> [2006/03/05 01:19:57, 0] lib/util_sock.c:write_data(554)
>
>  write_data: write failure in writing to client 192.168.0.15. Error
> Connection reset by peer
>
> [2006/03/05 01:19:57, 0] lib/util_sock.c:send_smb(762)
>
>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:write_data(554)
>
>  write_data: write failure in writing to client 0.0.0.0. Error
> Connection reset by peer
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:send_smb(762)
>
>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:write_data(554)
>
>  write_data: write failure in writing to client 0.0.0.0. Error
> Connection reset by peer
>
> [2006/03/05 10:24:57, 0] lib/util_sock.c:send_smb(762)
>
>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>
> =20
>
> =20
>
> Any help would be greatly appreciated!
>
> =20
>
> Thanks,
>
> =20
>
> Jacob.
>
> =20
>
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba

Jörg Nissen

2006-Mar-20 14:12 UTC

head link

[Samba] Problem Accessing Samba Server from Windows

"hosts allow" accepts single IP addresses as well as complete subnets
noted
like "192.168.xxx.0/255.255.255.0" or "192.168.xxx.0/24".

MfG
J?rg Nissen
----- Original Message ----- 
From: ""Administrator"" <Administrator@paradisent.com>
Newsgroups: mailing.unix.samba
Sent: Sunday, March 12, 2006 10:33 PM
Subject: RE: [Samba] Problem Accessing Samba Server from Windows

>I tried adding that to my smb.conf. What's the proper syntax for the
> hosts allow bit? My subnet is 192.168.0.X. I tried putting 192.168.0 and
> 192.168.0. but none of those helped. I just listed all my IP's and that
> didn't solve the problem either. Any other ideas?
>
> Thank,
>
> Jake.
>
> -----Original Message-----
> From: J=F6rg Nissen [mailto:joenis@arcor.de]=20
> Sent: Monday, March 06, 2006 12:22 AM
> To: samba@lists.samba.org
> Subject: Re: [Samba] Problem Accessing Samba Server from Windows
>
> I'm not quite sure about this but I miss the IPC section in your >
smb.conf.=20
> It should be similar to this:
>
> [IPC$]
>    path =3D /tmp
>    guest ok =3D yes
>    valid users =3D
>    hosts allow =3D 127.0.0.1, your.IP.subnet
>
>
> MfG
> J=F6rg Nissen
> ----- Original Message -----=20
> From: ""Administrator""
<Administrator@paradisent.com>
> Newsgroups: mailing.unix.samba
> Sent: Monday, March 06, 2006 1:09 AM
> Subject: [Samba] Problem Accessing Samba Server from Windows
>
>
>> Hi,
>>
>> =3D20
>>
>> I'm having a problem accessing my samba server from Windows. The
> problem
>> occurs every time I try to browse to it on either XP or 2003 Server.
> The
>> error message I get is: "\\Zeus is not accessible. You might not
have
>> permission to use this network resource. Contact the administrator of
>> this server to find out if you have access permissions. The account is
>> not authorized to log in from this station."
>>
>> =3D20
>>
>> There are no errors in the event logs on the Windows 2003 SP1 >
Enterprise
>> server, which is the PDC. The samba server is running Mandriva 2006
>> PowerPack. It's running Samba 3.020 with krb 1.4.2.
>>
>> =3D20
>>
>> For setting up the Samba server I followed the steps on the Samba
>> website to join the domain. The join went flawlessly and I can list
> the
>> users properly using wbinfo and getent.
>>
>> =3D20
>>
>> The PDC is named "Paradise", the XP client is
"Tama", and the samba
>> server is "Zeus".
>>
>> =3D20
>>
>> Here's my config files:
>>
>> =3D20
>>
>> # Samba config file
>>
>> =3D20
>>
>> [global]
>>
>>      log file =3D3D /var/log/samba/%m.log
>>
>>      ldap ssl =3D3D no
>>
>>      idmap gid =3D3D 10000-20000
>>
>>      wins server =3D3D 192.168.0.5
>>
>>      null passwords =3D3D yes
>>
>>      domain master =3D3D no
>>
>>      username map =3D3D /etc/samba/smbusers
>>
>>      encrypt passwords =3D3D yes
>>
>>      winbind trusted domains only =3D3D no
>>
>>      realm =3D3D CHU.PARADISENT.COM
>>
>>      public =3D3D yes
>>
>>      template shell =3D3D /bin/tcsh
>>
>>      dns proxy =3D3D no
>>
>>      netbios name =3D3D zeus
>>
>>      netbios aliases =3D3D ZEUS Zeus
>>
>>      server string =3D3D Samba Server
>>
>>      printing =3D3D cups
>>
>>      password server =3D3D 192.168.0.5
>>
>>      idmap uid =3D3D 10000-20000
>>
>>      local master =3D3D no
>>
>>      workgroup =3D3D CHU
>>
>>      os level =3D3D 20
>>
>>      printcap name =3D3D CUPS
>>
>>      security =3D3D ads
>>
>>      preferred master =3D3D no
>>
>>      winbind separator =3D3D |
>>
>>      max log size =3D3D 50
>>
>> =3D20
>>
>> [shared]
>>
>>      comment =3D3D Shared Folder
>>
>>      path =3D3D /shared
>>
>>      ;valid users =3D3D CHU|administrator, CHU|annie, CHU|jacob,
>> @CHU|Household
>>
>>      read only =3D3D No
>>
>> =3D20
>>
>> [jacob]
>>
>>      comment =3D3D Jacob's Home Dir
>>
>>      path =3D3D /home/jacob
>>
>>      ;valid users =3D3D CHU|jacob
>>
>>      read only =3D3D No
>>
>> =3D20
>>
>> [root]
>>
>>      comment =3D3D Root's Home Dir
>>
>>      path =3D3D /root
>>
>>      ;valid users =3D3D CHU|administrator, CHU|annie, CHU|jacob,
>> @BUILTIN|Administrators, "@CHU|Domain Admins",
"@CHU|Enterprise > Admins"
>>
>>      read only =3D3D No
>>
>> =3D20
>>
>> [annie]
>>
>>      comment =3D3D Annie's Home Dir
>>
>>      path =3D3D /home/annie
>>
>>      ;valid users =3D3D CHU|annie
>>
>>      read only =3D3D No
>>
>> =3D20
>>
>> [website]
>>
>>      comment =3D3D Main Website
>>
>>      path =3D3D /var/www/html
>>
>>      ;valid users =3D3D CHU|administrator, CHU|annie, CHU|jacob,
>> @CHU|Household
>>
>>      read only =3D3D No
>>
>> =3D20
>>
>> =3D20
>>
>> #
>>
>> # /etc/nsswitch.conf
>>
>> =3D20
>>
>> passwd:           files winbind
>>
>> shadow:           files winbind
>>
>> group:            files winbind
>>
>> =3D20
>>
>> #hosts:     db files nisplus nis dns
>>
>> hosts:      files dns winbind
>>
>> =3D20
>>
>> bootparams: nisplus [NOTFOUND=3D3Dreturn] files
>>
>> =3D20
>>
>> ethers:     files
>>
>> netmasks:   files
>>
>> networks:   files dns
>>
>> protocols:  files winbind
>>
>> rpc:        files
>>
>> services:   files winbind
>>
>> =3D20
>>
>> netgroup:   files winbind
>>
>> =3D20
>>
>> publickey:  nisplus
>>
>> =3D20
>>
>> automount:  files winbind
>>
>> aliases:    files nisplus
>>
>> =3D20
>>
>> =3D20
>>
>> krb5.conf
>>
>> =3D20
>>
>> [logging]
>>
>> default =3D3D FILE:/var/log/krb5libs.log
>>
>> kdc =3D3D FILE:/var/log/krb5kdc.log
>>
>> admin_server =3D3D FILE:/var/log/kadmind.log
>>
>> =3D20
>>
>> [libdefaults]
>>
>> ticket_lifetime =3D3D 24000
>>
>> default_realm =3D3D CHU.PARADISENT.COM
>>
>> =3D20
>>
>> [realms]
>>
>> CHU.PARADISENT.COM =3D3D {
>>
>>  kdc =3D3D paradise.paradisent.com
>>
>>  admin_server =3D3D paradise.paradisent.com
>>
>>  default_domain =3D3D chu.paradisent.com
>>
>> }
>>
>> =3D20
>>
>> [domain_realm]
>>
>> .kerberos.server =3D3D CHU.PARADISENT.COM
>>
>> .chu.paradisent.com =3D3D CHU.PARADISENT.COM
>>
>> chu.paradisent.com =3D3D CHU.PARADISENT.COM
>>
>> =3D20
>>
>> [appdefaults]
>>
>> pam =3D3D {
>>
>>   debug =3D3D false
>>
>>   ticket_lifetime =3D3D 36000
>>
>>   renew_lifetime =3D3D 36000
>>
>>   forwardable =3D3D true
>>
>>   krb4_convert =3D3D false
>>
>> }
>>
>> =3D20
>>
>> =3D20
>>
>> Here is what I found in my samba server logs:
>>
>> =3D20
>>
>> /var/log/messages
>>
>> =3D20
>>
>> Mar  5 10:24:57 zeus smbd[5099]: [2006/03/05 10:24:57, 0]
>> lib/util_sock.c:get_peer_addr(1222)=3D20
>>
>> Mar  5 10:24:57 zeus smbd[5099]:   getpeername failed. Error was
>> Transport endpoint is not connected=3D20
>>
>> Mar  5 10:24:57 zeus smbd[19273]: [2006/03/05 10:24:57, 0]
>> lib/util_sock.c:get_peer_addr(1222)=3D20
>>
>> Mar  5 10:24:57 zeus smbd[19273]:   getpeername failed. Error was
>> Transport endpoint is not connected=3D20
>>
>> Mar  5 10:24:57 zeus smbd[19273]: [2006/03/05 10:24:57, 0]
>> lib/util_sock.c:write_data(554)=3D20
>>
>> Mar  5 10:24:57 zeus smbd[19273]:   write_data: write failure in >
writing
>> to client 0.0.0.0. Error Connection reset by peer=3D20
>>
>> Mar  5 10:24:57 zeus smbd[19273]: [2006/03/05 10:24:57, 0]
>> lib/util_sock.c:send_smb(762)=3D20
>>
>> Mar  5 10:24:57 zeus smbd[19273]:   Error writing 4 bytes to client.
> -1.
>> (Connection reset by peer)=3D20
>>
>> Mar  5 10:24:57 zeus smbd[5099]: [2006/03/05 10:24:57, 0]
>> lib/util_sock.c:get_peer_addr(1222)=3D20
>>
>> Mar  5 10:24:57 zeus smbd[5099]:   getpeername failed. Error was
>> Transport endpoint is not connected=3D20
>>
>> Mar  5 10:24:57 zeus smbd[19276]: [2006/03/05 10:24:57, 0]
>> lib/util_sock.c:get_peer_addr(1222)=3D20
>>
>> Mar  5 10:24:57 zeus smbd[19276]:   getpeername failed. Error was
>> Transport endpoint is not connected=3D20
>>
>> Mar  5 10:24:57 zeus smbd[19276]: [2006/03/05 10:24:57, 0]
>> lib/util_sock.c:write_data(554)=3D20
>>
>> Mar  5 10:24:57 zeus smbd[19276]:   write_data: write failure in >
writing
>> to client 0.0.0.0. Error Connection reset by peer=3D20
>>
>> Mar  5 10:24:57 zeus smbd[19276]: [2006/03/05 10:24:57, 0]
>> lib/util_sock.c:send_smb(762)=3D20
>>
>> Mar  5 10:24:57 zeus smbd[19276]:   Error writing 4 bytes to client.
> -1.
>> (Connection reset by peer)=3D20
>>
>> Mar  5 10:59:52 zeus smbd[5099]: [2006/03/05 10:59:52, 0]
>> lib/util_sock.c:get_peer_addr(1222)=3D20
>>
>> Mar  5 10:59:52 zeus smbd[5099]:   getpeername failed. Error was
>> Transport endpoint is not connected=3D20
>>
>> Mar  5 10:59:52 zeus smbd[19280]: [2006/03/05 10:59:52, 0]
>> lib/util_sock.c:get_peer_addr(1222)=3D20
>>
>> Mar  5 10:59:52 zeus smbd[19280]:   getpeername failed. Error was
>> Transport endpoint is not connected=3D20
>>
>> Mar  5 10:59:52 zeus smbd[19280]: [2006/03/05 10:59:52, 0]
>> lib/util_sock.c:write_data(554)=3D20
>>
>> Mar  5 10:59:52 zeus smbd[19280]:   write_data: write failure in >
writing
>> to client 0.0.0.0. Error Connection reset by peer=3D20
>>
>> Mar  5 10:59:52 zeus smbd[19280]: [2006/03/05 10:59:52, 0]
>> lib/util_sock.c:send_smb(762)=3D20
>>
>> Mar  5 10:59:52 zeus smbd[19280]:   Error writing 4 bytes to client.
> -1.
>> (Connection reset by peer)=3D20
>>
>> =3D20
>>
>> =3D20
>>
>> log.nmbd
>>
>> =3D20
>>
>> [2006/03/05 04:02:04, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(284)
>>
>>  dump_workgroups()
>>
>>   dump workgroup on subnet    192.168.0.20: netmask=3D3D  >
255.255.255.0:
>>
>>      CHU(1) current master browser =3D3D PARADISE
>>
>>            ZEUS 40009b03 (Samba Server)
>>
>>            PARADISE 4084122b ()
>>
>> [2006/03/05 04:02:04, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(284)
>>
>>  dump_workgroups()
>>
>>   dump workgroup on subnet  UNICAST_SUBNET: netmask=3D3D        >
0.0.0.0:
>>
>>      CHU(1) current master browser =3D3D UNKNOWN
>>
>>            ZEUS 40009b03 (Samba Server)
>>
>> =3D20
>>
>> Log.wb-CHU
>>
>> =3D20
>>
>> [2006/03/05 00:32:30, 0] lib/util_sock.c:write_data(556)
>>
>>  write_data: write failure. Error =3D3D Connection reset by peer
>>
>> [2006/03/05 00:32:30, 0] libsmb/clientgen.c:write_socket(138)
>>
>>  write_socket: Error writing 190 bytes to socket 3: ERRNO =3D3D =3D
>> Connection
>> reset by peer
>>
>> [2006/03/05 00:32:30, 0] libsmb/clientgen.c:cli_send_smb(168)
>>
>>  Error writing 190 bytes to client. -1 (Connection reset by peer)
>>
>> [2006/03/05 00:32:30, 0] rpc_client/cli_pipe.c:rpc_api_pipe(438)
>>
>>  cli_pipe: return critical error. Error was Write error: Connection
>> reset by peer
>>
>> [2006/03/05 00:37:30, 0] rpc_client/cli_pipe.c:cli_rpc_close(1767)
>>
>>  cli_rpc_open failed on pipe \NETLOGON to machine PARADISE.  Error was
>> Write error: Connection reset by peer
>>
>> [2006/03/05 00:37:30, 0] rpc_client/cli_pipe.c:cli_rpc_close(1767)
>>
>>  cli_rpc_open failed on pipe \NETLOGON to machine PARADISE.  Error was
>> Write error: Connection reset by peer
>>
>> [2006/03/05 01:08:00, 0] lib/util_sock.c:write_data(556)
>>
>>  write_data: write failure. Error =3D3D Connection reset by peer
>>
>> [2006/03/05 01:08:00, 0] libsmb/clientgen.c:write_socket(138)
>>
>>  write_socket: Error writing 190 bytes to socket 3: ERRNO =3D3D =3D
>> Connection
>> reset by peer
>>
>> [2006/03/05 01:08:00, 0] libsmb/clientgen.c:cli_send_smb(168)
>>
>>  Error writing 190 bytes to client. -1 (Connection reset by peer)
>>
>> [2006/03/05 01:08:00, 0] rpc_client/cli_pipe.c:rpc_api_pipe(438)
>>
>>  cli_pipe: return critical error. Error was Write error: Connection
>> reset by peer
>>
>> [2006/03/05 01:10:34, 0] >
rpc_client/cli_pipe.c:cli_rpc_open_noauth(1700)
>>
>>  rpc_pipe_bind failed
>>
>> =3D20
>>
>> =3D20
>>
>> paradise.log
>>
>> =3D20
>>
>> [2006/03/04 23:54:45, 0] lib/util_sock.c:write_data(554)
>>
>>  write_data: write failure in writing to client 192.168.0.5. Error
>> Connection reset by peer
>>
>> [2006/03/04 23:54:45, 0] lib/util_sock.c:send_smb(762)
>>
>>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>>
>> [2006/03/05 10:59:52, 0] lib/util_sock.c:write_data(554)
>>
>>  write_data: write failure in writing to client 0.0.0.0. Error
>> Connection reset by peer
>>
>> [2006/03/05 10:59:52, 0] lib/util_sock.c:send_smb(762)
>>
>>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>>
>> =3D20
>>
>> =3D20
>>
>> Smbd.log
>>
>> =3D20
>>
>> [2006/03/05 04:02:04, 1] smbd/server.c:open_sockets_smbd(354)
>>
>>  Reloading services after SIGHUP
>>
>> [2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)
>>
>>  getpeername failed. Error was Transport endpoint is not connected
>>
>> [2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)
>>
>>  getpeername failed. Error was Transport endpoint is not connected
>>
>> [2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)
>>
>>  getpeername failed. Error was Transport endpoint is not connected
>>
>> [2006/03/05 10:24:57, 0] lib/util_sock.c:get_peer_addr(1222)
>>
>>  getpeername failed. Error was Transport endpoint is not connected
>>
>> [2006/03/05 10:59:52, 0] lib/util_sock.c:get_peer_addr(1222)
>>
>>  getpeername failed. Error was Transport endpoint is not connected
>>
>> [2006/03/05 10:59:52, 0] lib/util_sock.c:get_peer_addr(1222)
>>
>>  getpeername failed. Error was Transport endpoint is not connected
>>
>> =3D20
>>
>> =3D20
>>
>> tama.log
>>
>> =3D20
>>
>> [2006/03/04 22:22:39, 0] lib/util_sock.c:write_data(554)
>>
>>  write_data: write failure in writing to client 0.0.0.0. Error
>> Connection reset by peer
>>
>> [2006/03/04 22:22:39, 0] lib/util_sock.c:send_smb(762)
>>
>>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>>
>> [2006/03/05 01:19:57, 0] lib/util_sock.c:write_data(554)
>>
>>  write_data: write failure in writing to client 192.168.0.15. Error
>> Connection reset by peer
>>
>> [2006/03/05 01:19:57, 0] lib/util_sock.c:send_smb(762)
>>
>>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>>
>> [2006/03/05 10:24:57, 0] lib/util_sock.c:write_data(554)
>>
>>  write_data: write failure in writing to client 0.0.0.0. Error
>> Connection reset by peer
>>
>> [2006/03/05 10:24:57, 0] lib/util_sock.c:send_smb(762)
>>
>>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>>
>> [2006/03/05 10:24:57, 0] lib/util_sock.c:write_data(554)
>>
>>  write_data: write failure in writing to client 0.0.0.0. Error
>> Connection reset by peer
>>
>> [2006/03/05 10:24:57, 0] lib/util_sock.c:send_smb(762)
>>
>>  Error writing 4 bytes to client. -1. (Connection reset by peer)
>>
>> =3D20
>>
>> =3D20
>>
>> Any help would be greatly appreciated!
>>
>> =3D20
>>
>> Thanks,
>>
>> =3D20
>>
>> Jacob.
>>
>> =3D20
>>
>> --=20
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/listinfo/samba=20
>
>
>
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba

Seemingly Similar Threads

Search for more possibly parallel threads

samba - Mar 2006 - Problem Accessing Samba Server from Windows

[Samba] Problem Accessing Samba Server from Windows

[Samba] Problem Accessing Samba Server from Windows

[Samba] Problem Accessing Samba Server from Windows

[Samba] Problem Accessing Samba Server from Windows

Seemingly Similar Threads