1 Rookie

 • 

1 Message

February 19th, 2013 08:00

My 2155 worked for years until a firmware update killed scan-to-email.

Our fix was to setup DNS manually (always use Google 8.8.8.8), even though DHCP was enabled the device was not picking up the gateway as the DNS server.  Once the printer rebooted, scan-to-email once again functioned normally.  VERY frustrating problem!

Good luck.

1 Message

September 27th, 2011 14:00

Hello Steve,

I have got the exact same problem here.

Now it is even worst: no error messages appear but no emails are sent either.

Have you found a solution for this?

Do you know if there is any SMTP log available somewhere?

Thanks,

Ambroise

2 Posts

December 13th, 2011 13:00

I was getting the error  "unable to connect. smtp error 016-503  scan" on Dell 3115cn.  I was able to fix it by manually adding the google DNS 8.8.8.8.  Another option is to use the IP address for the SMTP gateway.  I left the e-mail send authentication to * invalid.

1 Message

December 4th, 2012 15:00

I was able to get this to work on a 2155cdn by setting the authentication to invalid and specific a default reply address in the settings. You also have to ensure that your receive connector in Exchange is configured to allow for anonymous access for your internal network.

1 Message

June 1st, 2013 04:00

Hi Steve,

Though it's long ago you wrote about your scan-to-email-problem with the Dell2155, I have a solution for your problem.

The cause of the problem is that the Dell is not able to find a DNS. The DNS is a server with a table for translating an smtp-servername to an IP-address.

So if you open a dosbox at your PC (enter "cmd" in the default searchfield of Windows 7 or in Start/Programs of WXP) a box appears with a commandprompt like C:\Users\xxx

If you type ping and the smtp-servername, an IP-address will be showed in the reply.

Example:

C:\Users\xxx ping smtp.telfort.nl


Pinging telfortsmtp.kpnxchange.com [213.75.63.9] with 32 bytes of data:
Reply from 213.75.63.9: bytes=32 time=32ms TTL=122
Reply from 213.75.63.9: bytes=32 time=36ms TTL=122
Reply from 213.75.63.9: bytes=32 time=19ms TTL=122

Ping statistics for 213.75.63.9:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 36ms, Average = 29ms

So if you enter the Ip-address (in my case 213.75.63.9) in the Primary SMTP Gateway it will work.

In your case for mail.gmx.fr it will be: 212.227.17.174

So if your problem is not yet solved, my answer might be helpfull, otherwise for someone else it might be helpfull.

Regards,


Albert Jol

2 Posts

October 15th, 2013 18:00

Thanks for posting this I did exactly what you said but when I pinged my server My packets said Sent= 4, Received = 0, Lost =4 (100% Loss)

 

Any idea why its not pinging back???

1 Message

June 3rd, 2014 17:00

I wanted to add an additional step to this solution.  I was recently trying to solve this issue, I did find out that the SMTP gateway required would be the IP address, but I was still having issues getting the print server to recognize any connection. Then I did an oldie but goodie and reboot the printer.  I did this, and all of a sudden, I was showing SMTP Connection: Connection pending errors from printer.  I know it's a stupid little thing, but it stumped me for a couple weeks of trying to configure and fine tune this printer, and this worked in addition to the solution above, thanks Albert Jol!

Best of Luck,

Harold Hicks

2 Posts

June 4th, 2014 06:00

That would be my Internet ip address or the device ip address off my network or my email providers ip address

1 Message

August 1st, 2014 07:00

Good Morning


I received a service call for a Dell 2155cdn which was receiving this gateway issue also.  The tech who originally set this printer up years ago has since left our organization and his notes are not available.  I had to reinitialize the device (fax/send/system) to gain access to the device but after gaining access tot he device I cannot find the section where I can set the smtp gateway.  I have downloaded the manual and gone through the menus but still cannot find this screen described above.  Can you tell me how to find this setup screen? 

Printer Revision Levels:

Firmware Version 201102181421
Network Firmware Version 16.15

Thank You

Ivan

2 Intern

 • 

301 Posts

August 5th, 2014 15:00

Hello Ivan,

Thank you for posting to the forum. The basic setup process for this model starts on page 370 of the user guide. Please understand that the use of email services hosted outside a local network is not guaranteed to function, though this does not mean you won't be able to get it to work with some advanced configuring.

Regards,
Joseph E

[tag:iworkfordell]

1 Message

March 23rd, 2015 18:00

You are a Boss.

Works a charm after setting the Google SMTP servers on port 465 then set security on the print server to SSL and finally adding the google DNS manually.

Substitute character removed as per TOU>

1 Message

May 27th, 2015 23:00

The software for Dell's C2665dnf appears buggy (and that is being kind).

Situation: The printer was configured with a numeric, valid IP address in the Primary SMTP Gateway. The DNS was set to 8.8.8.8

The remaining SMTP configuration was correct and Scanning to email had been done successfully multiple times. Then, 36 hours later, the SMTP Server Connection became "Unable to connect" as opposed to "Ready" status. A user was unable to scan and email, and received a "No network" message.  Four hours later, I was able to scan and email fine, and the status changed from Unable to Connect to Ready...without even turning the printer on/off and making NO configuration changes.

Could the IP address in the Primary SMTP Gateway really have been unavailable? Unlikely since that is the IP address of my server, and I know whether it is available and can check the logs.  What about DNS - could it have been unavailable? It's Google's (8.8.8.8) and since the SMTP is already numeric, no DNS should be needed!

The only conclusion I have is the software for configuring this printer is Very Buggy.  If anyone has other experiences to share, I look forward to them. It is going to be hard for me to explain why scanning worked - then didn't work - and now works again, with no changes in the environment.

No Events found!

Top