[Samba] SAMBA PDC / Server 2003 Shares - Error 1728 on clients - Error C002001D on Server 2003

[Darrell A. Sullivan, II]

Hello,

A few weeks ago I was trying to add a Server 2008 machine to my network that
is using an NT 4.0 PDC. I ran into issues both with Samba communication with
Server 2008 and with NT communication with server 2008 so I "downgraded" and
installed Server 2003 on that machine instead.

Now when I attempt to connect to the Server 2003 machine I am receiving
errors.

If I type in "net view db1" in a client (I have tried XP, NT 4.0, and
Windows 2000) I recive this error message:
System error 1728 has occurred.
A remote procedure call (RPC) protocol error occurred.

Checking the logs on the Server 2003 machine I am attempting to access I
receive this information:
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date:  4/6/2009
Time:  11:30:53 AM
User:  NT AUTHORITY\SYSTEM
Computer: DB1
Description:
Logon Failure:
  Reason:  An error occurred during logon
  User Name: administrator
  Domain:  FLEXSERVICES
  Logon Type: 3
  Logon Process: NtLmSsp
  Authentication Package: NTLM
  Workstation Name: \\TESTSERVER
  Status code: 0xC002001D
  Substatus code: 0x0
  Caller User Name: -
  Caller Domain: -
  Caller Logon ID: -
  Caller Process ID: -
  Transited Services: -
  Source Network Address: 192.168.1.89
  Source Port: 0


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


I have the following set in the Local Security Settings:
domain member: Digitally encrypt or sign secure channel data (always) ->
disabled
domain member: Digitally encrypt secure channel data (when possible) ->
enabled
domain member: Requires strong (Windows 2000 or later) session key ->
disabled
microsoft network client: digitally sign communications (always) -> disabled
microsoft network client: Digitally sign communications (if server agress)
-> enabled
microsoft network client: Send unencrypted password to third party SMB
servers -> enabled
microsoft network server: Digitally sign communications (always) -> disabled
microsoft network server: Digitally sign communications (if client agress)
->enabled
network security: LAN Manager authentication level -> Send LM & NTLM
responses


I also tried:
domain member: Digitally encrypt secure channel data (when possible) ->
disabled
microsoft network client: Digitally sign communications (if server agress)
-> disabled
microsoft network server: Digitally sign communications (if client agress)
-> disabled

I did a Google search and I did not turn up much on the 0xC002001D status
code so I thought I would post this and see if someone had an idea of what
would be going on.

Thank You,

Darrell