Bug 6679 - new windows clients can't access samba server
Summary: new windows clients can't access samba server
Alias: None
Product: Samba 3.2
Classification: Unclassified
Component: File services (show other bugs)
Version: unspecified
Hardware: IA64 Windows XP
: P3 major
Target Milestone: ---
Assignee: Volker Lendecke
QA Contact: Samba QA Contact
Depends on:
Reported: 2009-08-31 04:44 UTC by xintong
Modified: 2009-08-31 06:40 UTC (History)
1 user (show)

See Also:

debug level 10 log (74.02 KB, text/plain)
2009-08-31 05:58 UTC, xintong
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description xintong 2009-08-31 04:44:53 UTC

  our new Windows 2003 clients can't access our samba server. However, I can list the share directories from the samba server itself. I can access it from other unix clients. Some old Windows clients are able to access it.

  here is my smb.conf file:
# Global parameters
        workgroup = PFINTBK
        server string = phs71620
        security = SHARE
        encrypt passwords = Yes
        log file = /var/opt/samba/log.%m
        max log size = 1000
        local master = No
        guest account = guest (it is created at the Unix server)

        comment = Home Directories
        browseable = No
        path = /tmp
        guest ok = Yes

  When I try to use: net use W: \\sambaIP\tmp , it gives me this error message "System error 64 has occurred, the specified network name is no longer available"

 from the samba server, I got this error message:

[2009/08/31 15:49:34, 1] smbd/service.c:make_connection_snum(642)
  clientIP (clientIP) connect to service tmp initially as user guest(uid=109, gid=105) (pid 907)
[2009/08/31 15:49:34, 1] smbd/service.c:close_cnum(829)
  clientIP (clientIP) closed connection to service tmp

I really can't figure out the root cause. Please help if you can. thanks.
Comment 1 Volker Lendecke 2009-08-31 04:59:49 UTC
What is the exact Samba version you are using? And, please upload a debug level 10 log of smbd together with a network trace. Information on how to create useful network traces can be found under 



Comment 2 xintong 2009-08-31 05:58:04 UTC
Created attachment 4616 [details]
debug level 10 log
Comment 3 xintong 2009-08-31 06:01:34 UTC
Hi, it is # smbclient -L phs71620 -N
Domain=[PFINTBK] OS=[Unix] Server=[Samba 3.0.14a based HP CIFS Server A.02.02.01]

Have send you the debug level 10 log from the problem clients. Will try to get the log from the working client tomorrow.

the tcpdump got a missing library message, so not able to provide you that. If you really need it, I will try to download the etheral again.

Comment 4 Volker Lendecke 2009-08-31 06:05:18 UTC
Ok, 3.0.14 is really, really old. Please upgrade to a newer Samba version like 3.3.7 or 3.4.0.

And, security=share is also REALLY deprecated. Almost all things you want to achieve with it can also be done with security=user. I'm closing this bug as WONTFIX, we will not fix this in 3.0.14.

For discussion about security=share vs security=user please ask on samba@samba.org, I'm also listening there.

Comment 5 xintong 2009-08-31 06:21:55 UTC

   From your binary download depot, http://us1.samba.org/samba/ftp/Binary_Packages/hp/, the version for hpux is samba-3.0.23a and there isn't latest release for HPUX. From our HP webpage, our latest is A.02.04(3.0k): https://h20392.www2.hp.com/portal/swdepot/try.do?productNumber=B8725AA

  I have enabled the user level security at another server and it is the same.

  Can you please help me on this? If you want, I can install the lastone from our hp website. Thanks.


Comment 6 Volker Lendecke 2009-08-31 06:40:17 UTC
As you can see in the release notes of 3.0.36 on


there will be no bugfixes anymore for 3.0. Regarding the binaries: The binary packages we ship are mostly due to user contributions. Unfortunately nobody from Hewlett Packard is able or willing to supply any more recent Samba packages for HP/UX that we could upload.

If you need further assistance regarding this matter, you might want to contact HP themselves for support, or contact one of the support companies listed under


Please do not re-open this bug again unless you can reproduce it with 3.3 or 3.4.