Ricoh Image Scanner IS200e Problems Scanning To SMB Share With Win 2003

I am trying to get my Ricoh IS200e scanner to scan to an SMB share I created.  This worked fine when I had Windows 2000, but is no longer working after installing a Windows Server 2003 system.  I set up the appropriate shares it needs, and gave them full permission for everyone to access.  
Here is the options i had on the Windows 2000 server that worked, if they were in a different format at all, it did not work:
Send File Path: \\\ShareName
Login User Name:\user
Login Password: xxxxxxxx
If any one knows any more informationon getting this to work it would be appreciated.

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.

Hi eljasbo,

have you tried just using the DOMAINNAME\USERNAME without the .com switch?

eljasboAuthor Commented:
Thank you for your reply.  Yes,  i have tried it without .com earlier when i configured it for windows 2000, but it did not work.  I tried it again without it, but it still does not work.  I also tried calling the server by its name instead of an ip address, and that did not work either, even though i have the DNS server set correct.  The combination i wrote is the only way i found to get it working.  The scanner was very picky about it when i configured it for windows 2000.  It worked great with windows 2000 after i found the configuration combination it wanted, but now it does not.  I wish the scanner gave a more detailed error, but it does not.  Can i get the Windows server to log verbose smb errors somehow? That may help.  I think the server may need a user security right assigned to it or something.  On a separate note, when I updated a server at a different company from Windows 2000 to 2003, a Linux samba server stopped working with it until i updated it with a new version of samba.  I am thinking it is something similar, that Microsoft updated the smb protocol to add security or other enhancements, and as a result broke smb support on legacy devices.  Unfortunately, there is not a newer version of the scanner firmware i can apply. Thank you for your help.
eljasboAuthor Commented:
I found the answer to my problem.  The SMB packet signing is a new feature on Windows server 2003 that is enabled by default.  When I disabled the the following group policies in the Default Domain Policy and Default Domain Controller Policy it works again:
Microsoft Network server: Digitally sign communications (always)
Microsoft Network server: Digitally sign communications (if client agrees)
Microsoft Network client: Digitally sign communications (always)
Microsoft Network client: Digitally sign communications (if server agrees)

Thank you all for your help!
ah man i was no help

you did it yourself    well done :)
PAQed with points refunded (500)

Community Support Moderator

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
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 Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.