Hello Shannon,I'm afraid that I don't have a machine that is running Windows Advanced Server 2003...
Are you aware of any problems with Apache::Authensmb talking to a Windows Advanced Server 2003 server?
Thanks,
Hamish
My guess is that this URL might contain the answer to the problem:
http://lists.samba.org/pipermail/samba/2003-May/095207.html
Here is an excerpt:
<!---
/ So, W2K doesn’t need SMB-packets signatures and we have no problems, but we/>/ want it to work with Windows 2003. What’s the difference between Windows 2000 />/ and Windows 2003 when it comes to security signatures of SMB-packets? /
By default, a Windows Server 2003 requires signature of SMB packets (at
least, a Windows Server 2003 DC).
/ Can we disable signatures in Windows 2003 Server or do we have to make
/>/ some changes in Red Hat/Samba? Is ther another way to get around this />/ problem? / Yes, you can look for the following security option
Microsoft network server: Digitally sign commnunications (always) :
and set it to Disabled, instead of Enabled.
This security option modifies the following registry value:
Key: HKLM\SYSTEM\CCS\Service\lanmanserver\parameters\ Value: RequireSecuritySignature Content: 0 to disable, 1 to enable
If you don't want to reboot after that change, you can stop the srv.sys driver and services that depend on it using the following command:
C:\>net stop srv
Then, you can restart it, as well as the services that depend on it (in particular, netlogon)
C:\>net start srv
--->
Let me know if that's it, speeves cws
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
