2003-11-06, 05:26
for those of you having troubles getting the samba shares working with windows 2003 servers set as domain controllers, here's the fix:
as an administrator on the win2k3 server, go to your administrative tools (on start menu) and pick "domain controller security policy". goto "security settings" and then "local policies" and finally, "security options". find the setting entitled "microsoft network server: digitally sign communications (always)" and disable it. then you're all set.
the problem here is that microsoft defaultly forces all data sent over the network to be encrypted and thus unreadable by the samba system at this point (supposidly the new samba services allow support for the encryption). this explains why other windows systems are able to see the network shares while xbmc is not. disabling this will set your server to allow unencrypted data to be sent to clients who do not support the encryption. your server will, however, continue to send encrypted data to clients which support it (your windows systems).
hope this helps anyone with the problem.
canned.
as an administrator on the win2k3 server, go to your administrative tools (on start menu) and pick "domain controller security policy". goto "security settings" and then "local policies" and finally, "security options". find the setting entitled "microsoft network server: digitally sign communications (always)" and disable it. then you're all set.
the problem here is that microsoft defaultly forces all data sent over the network to be encrypted and thus unreadable by the samba system at this point (supposidly the new samba services allow support for the encryption). this explains why other windows systems are able to see the network shares while xbmc is not. disabling this will set your server to allow unencrypted data to be sent to clients who do not support the encryption. your server will, however, continue to send encrypted data to clients which support it (your windows systems).
hope this helps anyone with the problem.
canned.
