[Solved] Windows 7 and Samba Issue

Not expecting much from this but i figured i'd throw it out there to see if anyone else has seen it.

I have a Windows 7 machine on my test network here whenever i attempt to connect to a linux based file server on the network it kills samba on the server. The steps go like this:
Start
-search programs....
\\server.domain.com or \\xxx.xxx.xxx.xxx (IP address fo server)
-Windows 7 can't find server error (even if i run the repair)
Immediately afterwards the samba service on the file server crashes and is non-responsive to other computers on the test network.
My Vista machines don't have this issue.

Anyone else seen this? If not then keep your eyes open if you run into a similar issue.

Besides this i like the new OS.

Side note: I have reported this to Microsoft...

They fixed in in Vista so i am confident that they'll fix it in 7. But yes i have the same issue with MAC's and SMB.

Samba ok here? Windows 7 beta 32 bit and Ubuntu Linux 8.04 32 bit. Perhaps it's an issue with a particular distro? I can access from XP and Windows 7, the Samba service doesn't crash. I remember hearing something on the Floss weekly podcast episode 14 about Microsoft changing something within its networking protocols to deliberately thwart interoperability with Samba. Listen 35:00 minutes in. “The Microsoft engineers were apparently told to F*$k with Samba”!

Hooray! I am able to once again connect to my Samba share via Windows 7 after removing the stored credentials for the Samba share. Control Panel -> Credential manager.

How did you remove your samba share credentials exactly?

Thanks, nikonz. This worked for me. Windows 7 Beta (client) and Mac OS X 10.5.6 (server).

My trouble wasn't that the server was turning off...it was that the client wouldn't connect at all.

Interestingly i didn't have this issue with Windows 7 Beta (LAN manager authentication level was already set to send NTLMv2 responses only, security was set to 128bit) and I had no problems accessing my Samba shares.

However in Windows 7 RC, the LAN manager authentication level wasn't defined, and i could not access Samba shares. As soon as i set it as per nikonz post, it worked again.

Many thanks for the fix )

I was having problems with the following setup:

Win 7 Enterprise connecting to Fedora 4 with Samba 3.0.23a-1.fc4.1 machine that had been humming along since April '04. I keep all my work/project files on this (as well as my mp3's... shhhhhh)

I have had various problems over the years depending upon windows service packs, but always been able to figure out the problems. This one was driving me nutzo however.

Most google searches will tell you the answer to the NTLMv2 options you must set, which was the problem i had been having from Vista RC1. So, i figured this would fix my latest quandary, yeah? Uhh, no.

I had recently changed my open share, or "Anonymous" SAMBA share to use Active Directory authentication (for many reasons), and that had it's own set of challenges. Once those reasons were gone, I no longer needed this to be a "secure" share.

But after removing the ADS security samba settings back to normal Anonymous settings, I had figured there would be no problem connecting, right? Grrrrr, I keep getting, "The account is not authorized to log in from this station"

After beating my head on the keyboard, I kept coming back to why other machines I "own" and operate could get to this Anonymous share, but not my own personal domain computer. I was keying on why the could map "Guest" to "Nobody"

So as soon as I "enabled" the Guest account on my local domain PC, bingo! now i can open the Anon share. But... I dont like this!

I am very skilled at securing SAMBA, but not so good at making it work in a less secure operational mode.

Can anyone help me figure out how to map SAMBA setup so that no matter who is trying to connect, they will be mapped to "Nobody" ?

I too was having heaps of trouble getting windows 7 to login to Samba, it would ocasionally see the server, but most of the time it would not see it at all.
Then one day as I was edition s web page, I had a spot of inspiration, my server was called 'Sambe Server', ie with a space in the name.
Samba gave no errors, XP was happy (as well as samba on an iMac)
So I changed the space to a dash and win7 immediatly became happy!
Now if only I can get Win98 to see it.....

Paul S

How do you do this in Home Premium? I know we're missing the Local Security Policy editor. I have read you can edit the registry to do it but I am not sure what to look for. Thanks.

I had a similar problem when trying to connect Windows 7 Home Premium and Windows 7 Ultimate to a Mac OS 10.3.9 Server. I made the following change with the Local Security Policy on Ultimate and tested it successfully while watching the registry for changes. I found the following REG_DWORD values were changed:

HKLM\System\CurrentControlSet\Control\Lsa\LmCompatibilityLevel
HKLM\System\ControlSet001\Control\Lsa\LmCompatibilityLevel

After further testing, I found these to be the values and coresponding settings:

0) Send LM & NTLM responses
1) Send LM & NTLM - use NTLMv2 session security if negotiated
2) Send NTLM response only
3) Send NTLMv2 response only
4) Send NTLMv2 response only. Refuse LM
5) Send NTLMv2 response only. Refuse LM & NTLM

I created the LmCompatibilityLevel setting on my Home Premium machine with a value of 1 (http://www.builderau.com.au/blogs/codemonkeybusiness/viewblogpost.htm?p=339270746) and was finally able to connect to the 10.3.9 Server.

nikonz wrote :


Control Panel - Administrative Tools - Local Security Policy

Local Policies - Security Options



Network security: LAN Manager authentication level
Send LM & NTLM responses

Minimum session security for NTLM SSP
Disable Require 128-bit encryption



my SMB server worked after changing those two options






Thank u very much for adding this post. now i can connect to my mac server.

Best answer selected by lvdax.

Thanks:
This helped me start connecting to both server 2003 and Server 2000 systems when all els failed from a Win-7 pro installation from one particular computer. Funny thing is that this Win-7 (pro) had n problems connecting to other Win-7 and WinXP desktops.

thanks mate. this really worked for me too. i had hard time accessing the intra net resources on my new lappy with win7.

I have tried everything in this thread (as well as everything else I can locate on the Internet) and still I cannot get Windows 7 Home Premium to connect to a Samba share on Ubuntu. I have another computer running XP Pro and it connects with no problem. On Win 7, I keeping getting access denied. Actually, I found one setting in smb.conf that does allow Win 7 to connect:

protocol = LANMAN2

But this causes more issues than it solves. With that set, *both* my XP and Win7 boxes behave very strangely (and wrongly), e.g., with the following 3 files on the Ubuntu box:

ActivePerl-5.10.1.1007-MSWin32-x86-291969.msi
ActivePython-2.6.5.12-win32-x86.msi
ActiveTcl8.6.0.0b2.291226-win32-ix86-threaded.exe

from either Win box, typing "a" or "A" and hitting the tab key just produces a beep. Typing "dir A*" lists one file and then "file not found".

So, using that protocol is not an option.

Here are the relevant options I have in smb.conf:

client lanman auth = yes
client ntlmv2 auth = yes
lanman auth = yes
ntlm auth = yes

To get my XP box to work, only the second one is required (using LmCompatibilityLevel 2). On the Win7 box, I've tried levels 1 and 2 with no difference in outcome.

I'd appreciate any other ideas. My frustration level is boiling over. Ubuntu is 10.4 x86 with Samba 3.4.7. Thanks.

Hi all,

I have a similar problem with Ubuntu Server and Windows Vista and Seven.

I have created a share on Samba with user and password. I opened some ports on the firewall to allow access outside.

I can see the share and mapping the disk with this command:

NET USE Z: \\publicIP\share "PASSWORD" /USER:user

The problem is that: When I'm opening a file (Excel for example) this file is always in ready only mode. With Windows XP everything works fine.

Can this fix resolve my problems?

Control Panel - Administrative Tools - Local Security Policy

Local Policies - Security Options

Network security: LAN Manager authentication level
Send LM & NTLM responses

Minimum session security for NTLM SSP
Disable Require 128-bit encryption

Hey all, this thread seems the closest to my issue so I thought I'd ask it here:

I'm trying to connect to my OS X 10.6.3 MacBook Pro via my Windows 7 Ultimate Laptop

They are both on the same wireless network and see each other. Additionally, they are direct connected via Ethernet cable (and both recognize as such. I did this in an attempt to speed up wireless internet especially on the PC and improve file transfer rate times.)

On the PC, I've shared some folders via "Share With".

The Mac can access (read/write) said shared folders on the PC as expected (using SMB), finding it easily on the network. No problems there.

On the Mac, I've allowed File Sharing (with SMB and AFP). I've allowed Internet Sharing. *** NOTE *** I DO have Little Snitch running. This may be an issue. I have tried to get it to accept incoming connections from "natd" which seems to be DIVERTing connections to port 2560 (labrat) of 0.0.0.0 [I have NO idea what this means). There does not seem to be any success in altering this Little Snitch rule.

HOWEVER, the issue arises when I try to access OS X via the PC. While the PC recognizes the mac on the network, it is unable to connect to any form of:

//MAC
afp://MAC
//mac.local
//MAC.local
smb://MAC.local
//mac/homefolder <--I shared the homefolder
//MAC/homefolder
//MAC.local/homefolder
//ipaddress/homefolder
etc. etc.

Giving the error(s):
Firefox can't establish a connection to the server at xxx.xxx.xxx.xxx
or
Windows can not connect to //MAC
- If I diagnose it, I receive this:
file and print sharing resource (MAC) is online but isn't responding to any connection attempts


The PC does not recognize AFP or SMB protocols (I haven't added any new software for it).

I followed the instructions by nikonz, but i saw no change.

Does anyone have any idea how to fix this or what to do? I'd greatly appreciate 2 way interaction between my machines.

Thanks a bunch!