random scanner failures after moving to new office Ricoh Aficio MP 2000

[Guest]

Last month, our company moved a block and a half down 35th Street in NYC. In this new location scanner didn't work. I tweaked email and network settings, now it works at random.

Among changes, 192.168.1.30 --> 10.0.0.8 because using a router connected to a router, rather than a router connected to a modem (tried router connected to modem, same problems, less convenient, changed back); also chose a new SMTP sender compatible with our new DSL account (myUserName@verizon.net, SMTPutgoing.verizon.net, port 25)

Quite simply: If you scan to email, it may or not be successful. No reliable means found of altering this.

I am new to copytechnet, have read posts for a couple of weeks. I hoped I could have a more helpful explanation of the problem, but it seems quite entirely random.

Number of pages doesn't matter, email address doesn't matter, previous success or failure doesn't matter, resetting hardware either by web monitor interface or merely yanking out the power cord doesn't matter.

I've had enough successes to be confident in my email and network settings. It couldn't have succeeded this often if these settings were wrong. I am starting to suspect that the network card needs replacing. If that were the case, standard PC network cards are easily obtained. Does the Ricoh MP 2000 board take PC cards? Are they easy to install?

I'm wide open here, any advice welcome. Like I said, I'm new here, apologies if I've stepped on any posting protocols, etc.

Thanks!

[candygram4mongo]

Oh, one more bit of information. We have only used this for scan to email, ever since we first got the scanner option for the copier. The office workers like the tech-friendly approach, just pop pages into the sheet feeder, press the button for their email, and then hit the big green button! Then they take the attachment and forward it to their clients.

Because of this, they are pushing me to get scan to email back up and running, even though it would be nearly as easy to get them each little desktop scanners and teach them how to use them with their PCs...

[TonerMunkeh]

Instead of using smtp.verizon.net, try pinging it and using the IP address instead. That might sort you out.

[iMind]

X2

[chaunce54]

Is this a DSL connection? If so, I suspect it is the phone lines in the building, or something on Verizon's end. I have had similar problems with Verizon DSL in several locations on several different model machines. The email would go through every so often, but mostly wouldn't work. Hooked it up on the local network using Argosoft smtp server on a local pc, and worked perfectly, so it wasn't a problem with the copy machine.

[SCSI]

i was having the same problem with at&t. i had anything set up to go through at&t servers but the problem was they only had one account with one email set up. if they were using their email and trying to scan to email at the same time it would not go through. just to test it i put in another email server and it worked every time.

[Jomama46]

We use verizon dsl in this office and a little ways back Verizon told us to switch the outgoing port from 25 to 587.

[candygram4mongo]

Ping and port, problem solved!

So far, at least, everything seems to be working great! I can't seem to get it to fail now!

As advised, I pinged outgoing.verizon.net (with Windows XP, I held down the "start" key and tapped the letter "r" to get me to the "run" dialog box, typed in "command" and hit enter. Once I got a command prompt, I typed "ping outgoing.verizon.net" and wrote down the xxx.xxx.xxx.xxx IP number that showed up). I then went to the Ricoh Web Image Monitor, logged in as admin, and changed "SMTP Server Name" from "outgoing.verizon.net" to the IP number ping provided. And did a device reset for good measure. Sure enough, now it works!

And, as advised, I changed the SMTP port from 25 to 587, and it still works fine. I've heard of port 25 getting blocked by DSL providers, so 587 seems like a safe alternative.

Thanks again for all your help! It never would have occurred to me to put in the IP address instead of the server name...

[rthonpm]

You may also want to check to make sure that the copier is using the correct DNS addresses. Since the IP range changed, the copier's IP has changed, but the DNS servers may not have been changed. Use the ipconfig /all command in command prompt on one of the XP boxes and compare the DNS servers listed there with the ones the in the copier's settings via the web interface. If the IP of the server works, but the network name doesn't, then you've probably got an issue with the DNS settings of the machine.