Scan to Server

donte10

donte10

Member
Reaction score
1
Location
Milwaukee, WI
I recently setup a new 2012 Essentials server for a client that is replacing an older 2008 foundation server. Everything went pretty smooth, there is however one hiccup that I can't quite figure out. There is a Sharp MX-M283N printer on the network that is used to scan to the new server. However, I continue to lose communication between the server and the Sharp printer.

When trying to scan to the server, I receive the error: "Selected Servers are not Found. Contact Network Admin" **Occasionally scanning will work for 1 page documents to the server, but very seldom.

From the server command prompt, I test communication by PINGING the scanner from the server and I get a 'timed out' response. This also means I can't go to the web browser to access the scanner configuration (only from workstations). If I ping from any other of the 10 computers on the network to the scanner, I receive 4 successful responses. It only happens when trying communication/ping from the new server to the scanner. There seems to be some communication problem from the scanner to/from the server. Seems to be something to do with server security, but wasn't quite sure.

Note: the server has the DHCP and DNS role configured. Currently the firewall is turned off on the server for troubleshooting and the problem still exist. See

Any suggestions for troubleshooting is appreciated.
 
Last edited:
Server 2012 uses SMB 3.0. Server 2008 uses SMB 2.0 - you may need to update the firmware on the scanner to get it to work?? I have had to do this with some Ricoh photocopiers to allow scanning to Server 2012.
 
This reminds me about a problem I had many years ago(about 12 yrs ago). It was when server 2003 came out and I think it supported smb2 which our scanner didn't. We ended up having to disable smb2 and all was ok. I will bet it's the same type of issue where the new server is smb3 and the scanner doesn't support it.

Edit

Just seen the ping issue, I would think that should work in any case
 
It's odd as ping is a ICMP echo packet. Nothing has changed in years. I agree with the firmware update. I would also open up event viewer on the server and see what pops up when the scan save is attempted. Also, did you create a brand new entry or modify the existing entry on the device? Have you turned off IPV6 on the server? When you try hitting the device webpage are you using IE or something more reliable from the server? Can you access the scan to folder from a regular workstation with the same credentials?
 
Yeah I've been enabling SMB1 on Server 2012 for MFPs (can enable it and leave newer SMBs there)....done in PS window.
Also check the port, config on the scanning itself, scanner may be set on older SMB ports...137, 138, or 139...and try changing to 445.
Added a domain user account for the scanner? Is that account added to the share and NTFS permissions? I know "domain users group" should do it.......but...some of them scanners..weird....I've had them only start working when I added their domain user account to the share and NTFS permissions.
 
I'm just trying to get a good understanding; how does the SMB version relate also to the problem I'm having with pinging to the printer from the server? Are SMB version and Ping related in some way?

I've went ahead and disabled IPv6 from the server. Everything does work as expected from other workstations on the network running Windows 7 Professional.
 
Let me add more information to the mix of things... After more troubleshooting today, I can occasionally log into the server and ping the Sharp printer one-time. If I immediately try to ping the printer again (say 5 seconds later), I receive a 'timed out error'.
 
Just has a similar issue with a sharp copier used for scanning to a new server 2012 standard setup. Wound being the sharp software needs to be loaded on the server for a few sharp models to scan. Uses FTP and settings are done it that software, lets you map to a folder etc.
 
We're you able to ping the printer successfully before installing the software? I cant get a successful, consistent ping.

For your model printer, what version of the software did you use? When you say software are you referring to driver software or is there special sharp software required?
 
If you can't ping it consistentaly, then I would concentrate my efforts on the simple things first. Cables, switch ports, etc. Set the scanner wtih a fixed IP if it isn't already (and if it isn't, why not?). Once you can get successful pinging, then start working on the other stuff if it still won't connect. Everything has to fail sometime, are you sure the networking on the scanner is functional?
 
Agree with the last post. You need consistency on the ping so it looks like you are getting packet loss. Try pinging the ip address with the -t switch i.e. ping <ipaddresshere> -l 1500 -t. You should get consistency here. It could be a switch port issue, cable etc. Is the server working ok otherwise?
 
donte10 said:
We're you able to ping the printer successfully before installing the software? I cant get a successful, consistent ping.

For your model printer, what version of the software did you use? When you say software are you referring to driver software or is there special sharp software required?
Click to expand...


Yeah, you need to be able to get a good ping first of course. But for successful scanning for this model (Sharp AR-M230) if I remember correctly, we had to load this software on the server. It uses a license key also. Most other larger copier/scanners we can usually get to scan fairly easily but certain Sharps need this loaded.

IMG_0730.JPG
 
Wow, it's the simple things. It turned out to be a problem with the onboard NIC card on a NEW server. I went ahead and installed a new NIC card and it works just fine now. Thanks so much for all that provided suggestions. I know it happens, but I kept thinking to myself... "But it's a new server, what are the chances".
 
donte10 said:
Wow, it's the simple things. It turned out to be a problem with the onboard NIC card on a NEW server. I went ahead and installed a new NIC card and it works just fine now. Thanks so much for all that provided suggestions. I know it happens, but I kept thinking to myself... "But it's a new server, what are the chances".
Click to expand...

I know what you mean. Had a customer with a printer networking problem, 4200DN. They said they could not browse for it using UNC. Checked it out, works fine via the IP address. Flashed it, same thing. Had a spare JD card in my van, popped that in and everything worked fine. Who would have thunk that just UNC would fail.
 
You must log in or register to reply here.

Similar threads

C
VM Server reboot has a 169. address.
Replies
3
Views
1K
YeOldeStonecat
YeOldeStonecat
thecomputerguy
Where the heck is the Ricoh scan software?
2
Replies
26
Views
1K
HCHTech
HCHTech
HCHTech
Hyper-V - Moving VM to a new host
Replies
6
Views
393
britechguy
britechguy
HCHTech
Fun with Group Policy
Replies
13
Views
2K
GTP
GTP
HCHTech
LBFO vs. SET teams
Replies
15
Views
4K
britechguy
britechguy
Back
Top