Multitech MultiAccess MA220 User Manual page 34

Analog communications server
Hide thumbs Also See for MultiAccess MA220:
Table of Contents

Advertisement

Chapter 5 – Troubleshooting
Use a network analyzer to capture DNS and SMTP packets. Common security practices
implemented today relating to MX packets, reverse look-ups and firewall settings can prevent
successful delivery of e-mail messages.
Contact the MultiAccess unit using telnet and try to ping the mail server.
telnet 192.168.x.x
user: admin
password: admin
# ping 192.168.y.y (where this is the address of the mail server)
If the mail server ping fails, you must determine why it failed.
The mail server may not be contact-able because it is on a different subnet. The mail server
ping could also fail because the default gateway has been set incorrectly.
If the mail server ping succeeds, then try to ping the mail server using its domain name.
What if the remote users are failing authentication?
Variable: The shared secret is wrong (case sensitive), the user is giving the wrong
password, or the user doesn't have appropriate rights.
Variable: The Radius server doesn't see the authentication request.
The MultiAccess was not added to the clients file within the Radius server, the Radius client is
not set to the same set of UDP ports as the Radius server, the Radius client is pointing to the
wrong Radius server/IP address, or there is a network problem blocking or dropping the
request, Radius server uses UDP to communicate.
When the auth request is not seen by the Radius server, eventually the Radius client will
report a "Radius Timeout" error, no response from the Radius server, and disconnect the user.
My Windows application is unable to successfully use the modem
listed in the Phone and Modem applet of the control panel on my PC?
Variable: The MultiAccess can not tell which application, on the workstation, is opening
the TCP port/socket.
Redirectors, telnet clients, and proprietary programs all appear the same to the MultiAccess
because they all need to use/follow TCP/IP to get to the modem in the MultiAccess.
Telnet to the modem in the MultiAccess and issue AT commands, try to dial out. If it works,
then the redirector is configured wrong
or the user application is configured wrong.
Certain users are unable to use the MultiAccess to dial out?
Variable: When the MultiAccess is configured for Modem Sharing with Radius
Authentication, the user rights defined in the Radius server are not set
correctly.
The Service Type Attribute in the Radius server configuration is not set to "Outbound".
34
Multi-Tech Systems, Inc. MultiAccess User Guide

Advertisement

Table of Contents
loading

This manual is also suitable for:

Multiaccess ma420Multiaccess ma820

Table of Contents