Problem mapping drives from SBS2000 to 2003 Server - Access Denied Error seeing Shares

Setting up a new 2003 server with an existing 2000SBS server.  Each have own domain name and seem to be working okay with the execption that I cannot map any drives from the 2000SBS to 2003.  The other direction is okay.  I am also to take an xp workstation and map to both.  The admin user name and password are the same on both servers.
Who is Participating?
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.

What error message do you get when you try and map a drive?
This may have something to do with the setting in the Domain Controller Security Policy setting that defines whether or not communications to the server has to be digitally encrypted or not. Windows 2003 server has stricter rules in sharing resources on the network than Windows 2000 did, look in the Domain Controller Security Policy on your Windows 2003 server under Local Policies, Security Options. I was looking at a server I had to configure so that a copier would scan to a share on the server. I believe I changed the option Domain Member: Digitally encrypt or sign secure channel data (always), I enabled this setting.

The only other settings that look like they may have been changed are.

Microsoft Network Server: Digitally sign communications (always) - enabled
Microsoft Network Server: Digitally sign communications (if client agrees) - enabled

It's been awhile since I did this, but I do recall that the copier could not connect to the shares until this was done. I imagine the Windows 2000 server may be behaving in the same manner. I may be wrong.

Be careful when working with these settings when people are using the network.

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
mjwebbAuthor Commented:
We are checking that now but the error was "sysem error 5 has occured" but that was at a dos prompt.
mjwebbAuthor Commented:
In our case we had both of those set to enabled - once we put them to disabled we connected no problems.  Thanks so much!!!
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.