Host Engineering Forum
General Category => ECOMs and ECOM100s => Topic started by: edbfmi on March 22, 2011, 10:06:20 AM
-
Hi all,
This is the first time I have used the H0-ECOM100.
I am trying to send an email when a machine has faulted.
I think I have everything configured right per the IT guys input.
When I send a test email using NetEdit3 or from the Setup page by going to the ECOM through my browser or from a small test program in the DL05 PLC the email does not go through. The success bit is set in Directsoft5 when I run the Directsoft program but the email never makes it to me.
I monitored the traffic using the SMTP Viewer Tool in Directsoft5 and it shows this:
Mon Mar 21 13:43:42 2011 10.10.10.58: EMail Trace On
Mon Mar 21 13:43:57 2011 10.10.10.58: Recipient: ehenz@bryantcontrol.com
Mon Mar 21 13:43:57 2011 10.10.10.58: Subject: test
Mon Mar 21 13:43:57 2011 10.10.10.58: Body: test send
Mon Mar 21 13:43:57 2011 10.10.10.58: Sending HELO msg
Mon Mar 21 13:43:57 2011 10.10.10.58: State: 0x2 Received data: HTTP/1.1 400 Page not found
Does anyone know what would cause the State: 0x2 Received data: HTTP/1.1 400 Page not found
Thanks for any help.
-
What i see is that you have probably the wrong IPadres of your emailserver. because he respond with an HTTP error while a normal reaction would be 220 and after that some sort of welcome message so check the IPadress of your smtp server or use a different smtp server.
-
you might also have set the SMTP port to 80 instead of 25, that would cause an HTTP.
-
Hi all,
I just got it to work at my locations. I will check it at my customers in a few days.
Since MKL told me it was probably an issue with the smtp email server IP address. I looked around on some forums and found that my smtp server is smtpout.secureserver.net
In order to find the ip address for this server I went to the command prompt in windows and entered the following
ping smtpout.secureserver.net
it answered back with
Pinging smtpout.where.secureserver.net [xx.xxx.xx.xx] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for xx.xxx.xx.xx:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
I then used the xx.xxx.xx.xx that was returnd from the ping for my Server Address and it worked!!!
I hope this helps others.