Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We're in a mixed Unix (AIX in this Samba case) and Windows domain environment.

Part of what our goal to do this year is to upgrade from XP to Windows 7. While testing, we discovered that we couldn't connect to our Samba shares from Windows 7 like we could on Windows XP.

We're running Windows 7 Enterprise x64 and Samba 3.5.2.

We've disabled the firewall on the Windows 7 machine and created the appropriate keys in from the Samba wiki entry on Windows 7.


>cat smb.conf
        workgroup = DATABASE
        netbios name = MS
        server string = ms
        interfaces =
        encrypt passwords = Yes
        update encrypted = Yes
        pid directory = /opt/pware64/var/locks
        private dir = /opt/pware64/private
        smb passwd file = /opt/pware64/private/smbpasswd
        log level = 1
        log file = /opt/pware64/var/log/samba_log.%m
        max log size = 50
        max xmit = 65535
        name resolve order = host
        deadtime = 3600
        os level = 255
        preferred master = Yes
        dns proxy = No
        #wins support = Yes
        wins support = No
        lock dir = /opt/pware64/var/locks
        hosts allow = all
        keepalive = 0
        syslog = 2
        winbind enum users = No
        winbind enum groups = No
        smb ports = 139

        read only = No

        comment = Data
        path = /data
        valid users = testpc
        read only = No

        comment = I Drive
        path = /I
        valid users = dba
        read only = No

        comment = Downloads
        path = /downloads
        valid users = dba
        read only = No

Connection log:

>$ ll *testpc
-rw-r--r--  1 root system 17K 18 Apr 2011 14:08 samba_log.testpc 

>$ tail -4 *testpc
2011/04/18 14:08:35.408950,  1] smbd/service.c:1069(make_connection_snum)
  testpc ( connect to service data initially as user testuser (uid=6011, gid=1) (pid 1032402)
[2011/04/18 14:08:35.409878,  1] smbd/service.c:1250(close_cnum)
  testpc ( closed connection to service data

Connecting to the samba server was attempted through mapping a network drive. It does prompt for the password but it doesn't proceed from there, really. The message that it displays is that The specified server can not perform the requested operation.

Any help would be greatly appreciated. Thanks.

share|improve this question
up vote 1 down vote accepted

Found out the problem thanks to a co-worker looking into it.

The problem is that within our environment, by default, Windows 7 required all SMB packets to be signed. Samba servers, however, do not. So there are two ways to fix this: turn off client signing in Win7 or add a flag to the smb.conf file in the global section as this: 'server signing = auto'. (we were using Samba 3.5.2).

For Windows 7, you can 'fix' this policy by making it more lenient -- going from requiring digital signatures to optionally using it if the server agrees.

Here's how you can use it:

The local windows security policy changes are as follows: Start menu type GPEdit.msc Browse to Computer Configuration->Windows Settings->Security Settings->Local Policies->Security Options Look for "Microsoft network client: Digitally sign communications (always)" and change it to Disabled

You may also need to do the same for "Microsoft network client: Digitally sign communications (if server agrees)". In theory this should be negotiated during the negotiate/challenge phase of NTLM but it may fail; NTLM doesn't explicitly demand any real negotiation.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.