Manualsbrain.com
  1. Manuals
  2. Brands
  3. Multi-Tech Systems
  4. FF200
  5. User Manual

Multi-Tech Systems FF200 User Manual

Download
Page of 169
Chapter 9:  Troubleshooting 
Multi-Tech Systems, Inc.           FF200 FaxFinder Fax Server Admin User Guide 
161 
 
Chapter 9 – Troubleshooting 
1. What if I can't see the web page for my FaxFinder ? 
REMEDY:  Is the status LED on the FaxFinder unit blinking? If not, then the unit is either malfunctioning or 
not turned on.  If the Status LED is blinking, then verify that the Admin PC is actually on the 
same subnet as the FaxFinder and that it can be “pinged.”   
Launch a Command Prompt. 
(In WinNT, go to Start | Programs | Command Prompt. 
In WinXP, go to Start | All Programs | Accessories | Command Prompt. 
In Win2000, go to Start | Programs | Accessories | Command Prompt.) 
Type ipconfig to verify that the Admin PC’s IP address is in the same network as the 
FaxFinder’s IP address. 
Then type ping 192.168.2.1 (or server’s current IP address) and press Return. 
If the FaxFinder unit does reply to the ping and you are still unable to view the FaxFinder web 
page, then call Multi-Tech Tech Support for more assistance (1-800-972-2439). 
2. What if I don't get an email when I set the mail server address ? 
This pertains to the procedure “Setting Up the Mail Server.” 
The email may have failed due to one of three causes: 
(A) the name server is unresolvable,  
(B) the mail server cannot be contacted; or  
(C) the client PC running the mail software cannot connect to the mail server; or 
(D) the administrator’s email address may be missing or incorrect. 
CAUSE A:  During transmission, the name server’s address could not be resolved (that is, the FaxFinder 
unit could not contact your name server). 
RESPONSE A:  Contact the FaxFinder unit using telnet and try to ping the name server.   
   telnet 192.168.x.x 
   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 contact-able 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.