win2003 server samba client

[Guest vitorneves]

Hi there,

 

I'm having some problems on connecting my mdk10 machine to the shares at win2003 server. mdk10 can connect to other shares on other win xp clients but not to the win2003 server.

 

Maybe some configuration at the win2003 server must be disable in order to acept the mdk10.

 

on Smb4K I can see the shares on the win 2003 server. It even detects the win server OS but I cannot mount the share on linux. I get the following error:

cli_negprot: SMB signing is mandatory and we have disabled it.

2322: protocol negotiation failed.

Still I can see previews of the shares.

 

Thanks

[Gowator]

sounds like this is in the ipsec stuff on the win2003 server!

 

(oh welcome btw- sorry i cant be more help but I guess the prob is in the win2003 config)

[jimdunn]

This is because Win 2k3 by default requires signing of SMB packets.

 

Windows 2003 requires SMB signing. Client side SMB signing has been implemented in Samba-3.0. Set client use spnego = yes when communicating with a Windows 2003 server.

 

So the best way is to update to Samba 3 and Set client use spnego = yes

 

You can also disable the requirement on the Windows Server if you have the authority, and accept the security implications, by changing this registry key

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters]
"requiresecuritysignature"=dword:00000000

 

Just save that code as a .reg file and run it.

 

(Although you may find that Windows sets it back to enabled from time to time, depending on your other security settings)

 

 

 

But the preferred way would be to upgrade Samba

 

There's a pretty good article all about it at:

 

Integrating Samba 3 into a Windows 2003 Domain

Edited June 22, 2004 by jimdunn

[Guest vitorneves]

Well...I've just tried SUSE 9.1 and it worked fine as client for a WIN2003 Server lan. No special setups were needed! amazing!

 

Fantastic OS! Thanks Suse LINUX. Probably the best OS ever seen.

[Guest riccitelli]

Changing registry setting will temporary since Windows will reset to Group Policy settings.

 

To change the policy setting abount digital-signing on Windows 2003/2000 check this link

http://support.microsoft.com/?kbid=839499

 

On Windows 2003 there's no need to restart after applying the GPO update.

 

ZioDave

[Guest pleinair]

I tried the suggestion of setting client use spnego = yes as well as no.

Neither works.

 

It looks like I have Samba 3.0.2 (not sure of the definitive way to do it from text mode).

 

I read somewhere esle that what's really required is the new file system type CIFS which is not installed by default.

 

Haven't tried the registry change suggestion.

 

Eric

[Guest Underdog]

I am having this exact same problem. I upgraded to MDK 10.1 Beta this weekend thinking it may fix the problem. It did upgrade SMB4K to version .4 but is still does not work. I have read that you can turn SMB signing off on the Win2K3 server but I would rather get it to work without having to touch the server . . . I had tried to make and install the newest version of Samba, but I don't even know if SMB4K links to it . . . kinda new to this . . . but I will be watching this thread to see if anyone finds the answer. I have tried setting client spnego = yes and client signing = mandatory and no luck . . .

[Guest fhess]

still no progression here?

i'm stuck with the same problem, see http://mandrakeusers.org/index.php?showtopic=23718 as well.

[adolfix]

It seems to be a problem of acces permissions on the 2003 server.

Even if the folders are shared, it is necessary to declare who can acces to them.

Verify this point. This may be the reason.

Bye