Have followed swerdna’s guide as in the past and my wife from her win7 computer can see and has read write access to all the shares & can print to the shared printer attached to the Opensuse computer etc.
However, when I try to access her Win7 shares from my opensuse computer I am presented with a username / password prompt.
Here is my smb.conf
[global]
workgroup = FARCUSNET
netbios name = markpc
name resolve order = bcast host lmhosts wins
map to guest = Bad User
preferred master = yes
os level = 65
printcap name = cups
cups options = raw
use client driver = yes
server string = “”
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = False
wide links = Yes
have followed swerdna’s guide (as mentioned previously) and set ‘password protected sharing’ to off on the win7 computer.
Anybody have any ideas on this? Did not get this with an XP share.
>
> wife has recently upgraded from XP to Win7.
>
> Have followed swerdna’s guide as in the past and my wife from her win7
> computer can see and has read write access to all the shares & can print
> to the shared printer attached to the Opensuse computer etc.
>
> However, when I try to access her Win7 shares from my opensuse computer
> I am presented with a username / password prompt.
>
> Here is my smb.conf
>
>>
>> [global]
>> workgroup = FARCUSNET
>> netbios name = markpc
>> name resolve order = bcast host lmhosts wins
>> map to guest = Bad User
>> preferred master = yes
>> os level = 65
>> printcap name = cups
>> cups options = raw
>> use client driver = yes
>> server string = “”
>> usershare allow guests = Yes
>> usershare max shares = 100
>> usershare owner only = False
>> wide links = Yes
>
> have followed swerdna’s guide (as mentioned previously) and set
> ‘password protected sharing’ to off on the win7 computer.
>
> Anybody have any ideas on this? Did not get this with an XP share.
>
>
farcusnz;
Hi - yes, have checked this information and have the computer name correct and the only password set is the login pasword for the Win7 computer. This does not work.
A friend of mine was able to get it working by creating samba users that matched his windows users accounts. And I had to rewrite the smb.conf file from scratch to get everything working with XP, no amount of editing would get sharing working both ways.
I’ve never had a problem getting sharing working both ways with XP. Just stumped with Win7.
As mentioned previously - works perfectly one way (Win7-Opensue) just not the other (opensuse - Win7)
That was my problem before I created a new smb.conf file. Everything worked fine from XP, I could see my shared folders on my Linux box and print to it but when I tried to get on the network in Linux it would time out every time I looked in my workgroup. This is my smb.conf file.
[global]
workgroup = BOLLENDORF
netbios nmae = AGAMEMNON
passdb backend = tdbsam
name resolve order = bcast host lmhosts wins
map to guest = Bad User
local master = yes
preferred master = yes
os level = 65
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
load printers = yes
use client driver = yes
server string = “”
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = False
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0700
guest ok = Yes
browseable = No
[Music]
path = /Storage/Music
read only = no
guest ok = yes
force user = daniel
[Videos]
path = /Storage/Videos
read only = no
guest ok = yes
force user = daniel
[Pictures]
path = /Storage/Pictures
read only = no
guest ok = yes
force user = daniel
I wish I could be more help, but XP and Windows 7 networking is so different I had trouble getting them to talk to each other.
Check whether the security method/level has changed when you upgraded from XP to Windows 7. Depending on your network environment, you might have experienced a hashing upgrade from LANMAN to LANMAN2 (I’d guess likely in a SOHO network), or to Kerberos (If in a Windows AD). It looks like the Swerdna link in post #2 sidesteps this possible issue by configuring Everyone permissions on the Share which is a security issue on machines like laptops which can leave the network or are otherwise exposed to intruders (eg wireless connections).
In a Workgroup environment, particularly if a specific machine is on all the time set one machine to be the Preferred Master and all other machines not to decrease elections that can move the Workgroup Master around from machine to machine.
>
> Just some thoughts,
>
> - Check whether the security method/level has changed when you upgraded
> from XP to Windows 7. Depending on your network environment, you might
> have experienced a hashing upgrade from LANMAN to LANMAN2 (I’d guess
> likely in a SOHO network), or to Kerberos (If in a Windows AD). It looks
> like the Swerdna link in post #2 sidesteps this possible issue by
> configuring Everyone permissions on the Share which is a security issue
> on machines like laptops which can leave the network or are otherwise
> exposed to intruders (eg wireless connections).
> - In a Workgroup environment, particularly if a specific machine is on
> all the time set one machine to be the Preferred Master and all other
> machines not to decrease elections that can move the Workgroup Master
> around from machine to machine.
>
> HTH,
> Tony
>
>
Tony;
Windows has not used LANMAN since Windows 98. In fact current versions of
Samba have LANMAN turned off by default. Normally NTLMv2 is used. Since
VISTA offers smb2 but auto negotiation should settle on NTLMv2.
farcusnz;
Almost certainly this is a permission problem on Windows 7. Check the
Windows 7 security logs to see how your user is authenticating on Win7. My
guess is that your Linux user is being authenticated as Guest and if Guest
does not have rights on the the share, access will be denied.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Not entirely true. Although what you say may apply to default Windows installations, security levels are often set to or allowed at lower levels for backwards compatibility with other machines, and some specific applications like IIS were even slower to adopt better security levels than the OS they may be installed on.
So, even in XP it’s a possible issue to be considered.
Tony
BTW - This can be verified easily and simply by Googling “xp security level lanman”
>
> venzkep;2274738 Wrote:
>> On Thu January 6 2011 02:36 pm, tsu2 wrote:
<snip>
>
> Not entirely true. Although what you say may apply to default Windows
> installations, security levels are often set to or allowed at lower
> levels for backwards compatibility with other machines, and some
> specific applications like IIS were even slower to adopt better security
> levels than the OS they may be installed on.
>
> So, even in XP it’s a possible issue to be considered.
>
> Tony
>
> BTW - This can be verified easily and simply by Googling “xp security
> level lanman”
>
Tony;
I did not mean to imply the inability to use LANMAN. But by default, XP will
first offer NTLMv2 and then negotiate down. VISTA and higher will first
offer SMB2 and then negotiate down. Recent versions (3.5.x) of Samba and
Samba Client are capable of SMB2 but it is still a bit experimental and in a
default installation turned off. Samba will first try NTLMv2. Since LANMAN
is now disabled by default in newer versions of Samba and Samba Client, I
assume they will need to use NTLMv2 or NTLMv1. I believe SMB2 will be
turned on in version 3.6.0. To enable both SMB2 and LANMAN for Samba you
need these parameters in the [global] section of /etc/samba/smb.conf