Filter
Top Products
Appendix A: Troubleshooting
Multi-Tech Systems, Inc. FF240-IP Admin User Guide 93
CAUSE A: During transmission, the name server’s address could not be resolved (that is, the FF240-IP
unit could not contact your name server).
RESPONSE A: Contact the FF240-IP unit using secure shell and try to ping the name server.
ssh user@ip
user: admin
password: admin
# ping 192.168.y.y (where this is the address of the name server)
If the name server ping fails, you must determine why it failed.
The name server may not be reachable because it is on a different subnet. The name
server ping could also fail because the default gateway has been set incorrectly.
If the name server ping succeeds, then try to ping the mail server using its domain
name.
# ping mail.ourcompany.com
If you succeed in pinging the mail server by its IP address but yet it cannot be pinged
via its domain name, then the name server is not functioning correctly.
If the mail server can be pinged neither by its domain name nor by its IP address, then
consider item B below.
CAUSE B: The mail server is not running or cannot be contacted from the FF240-IP unit.
RESPONSE B: Verify that the mail server is running by sending an email to yourself using your
email software.
If you cannot send an email to yourself using your email software, then the mail server
is not running and you should find out why.
If you can send an email to yourself using the email software, then there is a problem
between your mail server and the FF240-IP unit. Contact Multi-Tech Technical Support
on our portal at https://support.multitech.com
.
CAUSE C: The client PC running the mail software cannot connect to the mail server.
RESPONSE C: If you, as a client, cannot send yourself an email, then contact your administrator;
there may be a problem with your mail server.
CAUSE D: The administrator’s email address may be missing or incorrect.
RESPONSE D: Check and add/correct the administrator’s email address, as needed.