Solved

How do I allow Ricoh scanner to connect to network share hosted on 2008 R2 Domain controller

Posted on 2011-09-21
8
1,868 Views
Last Modified: 2012-08-13
I recently migrated toa  primary dedicated domain controller. This DC has a Perc6i raid card connected to a MD1000 NAS, all the drive are accessible by users via mapped drives, however the path will not connect when I try to perfomr a scan function witha  Ricoh copier.

When I search the network via the Ricoh it can try to connect to any server or workstation with shares and will prompt your for credentials since its not mapped by default, the domain controlelr share will simply time out. Scan to email does not work either, I can ping SMTP and the DNS serrvers from the copier.

Can anyone help me?
0
Comment
Question by:manelson05
8 Comments
 
LVL 20

Expert Comment

by:brwwiggins
ID: 36577979
the two biggest issues that I've run into lately with multi-function devices and Windows Server 2008 R2 is SMB signing and SMB 2.0

In most of my cases disabling smb signing did the trick but that will depend on your Ricoh.
0
 
LVL 43

Expert Comment

by:Steve Knight
ID: 36579329
Lack of connectivity from old connections seems logical.  Aside from amendments to the Windows 2008 server does that NAS have a network connection too that you could write directly to a share on perhaps?

Curious, in what way does scan to email not work?  Does your internal smtp server accept connections from the IP address / email address, perhaps it is restricted?

If you do this from another computer, or the same IP as the copier does it work:
start | run (or from cmd.exe prompt):

telnet x.x.x.x 25
helo test
mail from: copier.address@yourdomain.com
rcpt to: your.address@yourdomain.com
data
From:  copier.address@yourdomain.com
To:  your.address@yourdomain.com
Subject: test email

something to see in the body
.
quit
0
 

Author Comment

by:manelson05
ID: 36934625
I actually used ip instead of fqdn.

192.x.x.x/Scans/admin, this worked. Ricoh has a documented error with SMB 2.0
0
 

Accepted Solution

by:
manelson05 earned 0 total points
ID: 37036431
I've requested that this question be closed as follows:

Accepted answer: 0 points for manelson05's comment http:/Q_27319682.html#36934625

for the following reason:

I discovered that FQDN does not work with SMB 2.0 error with exisiting firmware, I had to map via IP.
0
 
LVL 43

Expert Comment

by:Steve Knight
ID: 37036430
did you try the smtp troubleshooting above?  Did you not find it was an smb2 issue then as in guys first post.  maybe you dont have its DNS setting pointing at your new DC to resolve addresses too?  Glad we took the time to post here without any feedback....    Tip for the future.   If you respond we can offer other suggestions  If you troubleshoot likee we ask andd feed back we know if it was that or something else.
0
 

Expert Comment

by:modus_in_rebus
ID: 37098884
Since there has been no further discussion, I'm restarting the auto-close procedure, the way the asker originally intended.

modus_in_rebus
Community Support Moderator
0

Join & Write a Comment

Synchronize a new Active Directory domain with an existing Office 365 tenant
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now