Domain Controller Denying Access to our Macs

I just upgraded a Windows 2003 (R2) server to a domain controller. Everything is working fine except our two Macintosh machines (OS 10.3) cannot access their file share anymore. PC's can access this file share just fine. The same users that work on the Macs can use a PC to access the folder, and that also works. The console error I get on the MAC is

"mount_smbfs: tree connect phase failed: syserr = Permission denied
mount_smbfs: main(lookup): bad keychain entry"

Again, this was working just fine before we promoted this server to a domain controller.
Any ideas anyone? Any help would be appreciated!
mckeoughAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TannerManCommented:
THis may or may not help you, but looks like you.

http://www.macwindows.com/AD.html#1
click on the the first section link "Active Directory Introduction"
Hopefully not a waste of your time, but a great resource for Mac Authentication on AD networks.
mckeoughAuthor Commented:
Sorry, that doesn't help. We need to figure out why we're being denied permission even though we just created another MAC share, made sure the Macs were bound to the domain, etc...
TannerManCommented:
My apologies for not catching the jest of the situation. I thought you added a Domain Controller vs. you were on a workgroup prior. You just meant you have an existing non-DC you upgraded to be a DC......... that mac's can't get to shares. Sorry.

When I have had this ocurr with other servers all of a sudden loosing permissions to a Share it has been a broken secure link between them and the domain.....removing them from the domain and then re-adding fixed it. This may not even be the issue, but if that Secure Channel is gone that is the only way to correct. Just something to try that can't hurt anything but a loss of time to try it.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mckeoughAuthor Commented:
Thanks! That worked!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.