Symptom:
The Dial on Demand may drop immediately
after the first successful dial.
Back to Top
Symptom:
The Apex Manager will display an error message
stating that the IP Address is not in the same Subnet Mask.
Back to Top
Symptom:
The Apex 1100 has PPP compatibility problems
with Livingston Server.
Back
to Top
Symptom:
Dial-tone detection, phone ringing, or
voice connection problems, analog modem or analog phone not recognized
by Apex 1100.
Suggestion: You can check
your hardware's serial
number below. If your serial number
is within the ranges, contact Arescom directly as we may have a special
hardware upgrade to enable improved performance.
Back
to Top
Symptom:
Data-over-voice or 56K connection problems
Suggestion: You can check
your hardware's serial
number below. If your serial number
is within the ranges, contact Arescom directly as we may have a special
hardware upgrade to enable improved performance.
Back
to Top
Symptom:
Power supply has failed to operate.
Suggestion: You can check
your hardware's serial number below. If your serial number is within
the ranges, contact Arescom directly as we may have a special hardware
upgrade address this problem.
| |
From
|
To
|
|
Apex 1100-1
|
00201-1-10-000001
|
00201-1-10-999999
|
| |
00201-1-20-020001
|
00201-1-20-020045
|
| |
|
|
|
Apex 1100-2
|
00202-1-10-000001
|
00202-1-10-999999
|
| |
00202-1-20-000001
|
00202-1-20-000845
|
| |
|
|
|
Apex 1100-3
|
00203-1-10-000001
|
00203-1-10-999999
|
| |
00203-1-10-010001
|
00203-1-20-010202
|
Back to Top
Symptom:
Router keeps dialing out for no reason.
Cause: There are four main causes for
the router dialing out by itself:
Dial-On-Demand
(DOD) has been enabled, and out-going packets are sending by applications
Bridging Broadcast
Packets Trigger Dial-On-Demand has been enabled
Never
disconnect / Always re-connect has been enabled
NetBIOS requesting
for Name Resolution on DNS
Cause:
Dial-On-Demand (DOD) has been enabled,
and out-going packets are sending by applications.
If you have the Dial-On-Demand enabled, the
router will be triggered by any packets going out of the LAN. For
example, activate Internet Browser, check e-mails, and real-time news
(Push technology) will trigger the router.
Solutions:
1. Make sure you don't have any of the above
application is running.
2. You can disable Dial-On-Demand by deselect
"Enable Outgoing Dial-On-Demand" under PPP Connection in
Advanced menu. By doing this, router will never be triggered by browser
or e-mail program. You have to connect manually by click "Connect"
button in Status window every time you want to connect.
3. If you do not want to disable the Dial-On-Demand,
please check the followings one by one:
Bridging Broadcast
Packets Trigger Dial-On-Demand has been enabled
Never disconnect/Always
re-connect has been enabled
NetBIOS requesting
for Name Resolution on DNS
Cause: "Bridging Broadcast
Packets Trigger Dial-On-Demand" has been enabled. Many
bridging packets are travelling through the LAN, and many of them
are broadcast packets. The router will be triggered easily by those
type of packets.
Solution: Do not enable "Broadcast
Packets Trigger Dial-On-Demand" under Bridging Configuration
in Advanced menu.
Cause:
"Never disconnect/Always re-connect" has been enabled. This
option is for people that have a flat rate and want the router connected
on line all the time. For any reason the connection gets dropped,
the router will always try to re-connect. The number of re-connect
attempts depends on the user's setting.
Solution: Deselect "Never disconnect
/Always re-connect" by select "Automatically disconnect
after xxx seconds idle".
Cause:
NetBIOS is making a request for name resolution on DNS. NetBIOS is
a network operating system that allows computers to communicate with
each other on a network. Occasionally, the NetBIOS is unable to resolve
a domain name on the local network, and will attempt to trigger dial-on-demand
to find a DNS outside the LAN.
Solution: Create a Filter to stop the
NetBIOS Name Resolution on DNS.
In this case, the PC's address and subnet is
192.168.1.5/255.255.255.0,
DNS's address and subnet is x.x.x.x/y.y.y.y.
Go to Apex Manager >Advanced >Protocol Configuration >
IP Packet Filtering >Add
Source:
IP address: 192.168.1.5
Subnet Mask: 255.255.255.0
TCP/IP port: 137
Protocol type: UDP
Destination
IP address: x.x.x.x
Subnet Mask: y.y.y.y
TCP/IP port: 53
If True then: Discard
If False then: Pass
The advantage is you can stop the trigger,
no matter which computer is sending out requests. But you will not
be able to locate the computer is making the trigger.
Reference Material:
Disable NetBIOS Name Resolution
on DNS: Article
ID Q137368
Article Summary: Describes how to disable
NetBIOS name resolution on a domain-name
system (DNS) while retaining other DNS functionality. The document
is located at <http://support.microsoft.com/
support/kb/articles/q137/3/68.asp>, and the copyright belongs to
Microsoft Corp.
If you have more than one PC, you have to
NetBIOS name resolution one by one to locate which computer is making
the trigger.
Browsing & Other Traffic
Incur High Costs over ISDN Routers: Article
ID Q134985
Article Summary: If your network spans
two or more sites, you use ISDN TCP/IP routers, or you use an ISDN
service that charges you based on connection time then some Windows
NT features may cause a lot of traffic between domain servers on different
sites, causing your ISDN telecommunication costs to be high. The document
is located at <http://support.microsoft.com/
support/kb/articles/q134/9/85.asp>, and the copyright belongs to
Microsoft Corp.
NetBIOS over TCP/IP Name Resolution
and WINS: Article
ID Q119493
Article Summary: NetBIOS over TCP/IP
is the network component that performs computer name to IP address
mapping, name resolution (NETBT.SYS in Windows NT and VNBT.VXD in
Windows for Worgroups and Windows 95). There are currently four NetBIOS
over TCP/IP name resolution methods: b-node, p-node, m-node and h-node.
The document is located at <http://support.microsoft.com/
support/kb/articles/q119/4/93.asp>, and the copyright belongs to
Microsoft Corp.
Back to Top
Symptom:
Cannot find the Apex router.
Suggestions:
Check power connection.
- Check the Ethernet connection.
- Make sure that Ethernet card is installed
properly.
- Make sure that TCP/IP has been installed
on the same Ethernet card.
- If using direct connection (PC to Router),
make sure you are using a crossover cable.
- If their is another Dial-up/Terminal Adapter
installed on the same PC, make sure that the adapter does not have
an IP address.
- Un-plug, wait 30 seconds, and re-plug the
router.
- Run the Apex Manager.
- If the Apex Manger still cannot detect the
router, then configure your PC and router so that they are in the
same
subnet.
- If none of the suggestions above worked,
set your PC's IP address as 192.168.1.2 and Subnet Mask as 255.255.255.0
and try to detect again.
- If you are using "Specify an IP
address" for your PC's TCP/IP settings, try to ping
one of your nodes in the LAN and see if you can get the reply. If
you cannot get the reply, check your Ethernet connection. If you
get the reply from the node, try pinging the router. (To ping: Start
> Programs > MS-DOS prompt > type ping and the IP
address of the Ethernet or router. For example, c:\>ping
100.100.100.5.)
- If Apex Manager still cannot detect the
router, please try the following. Attach a null modem cable connect
to your PC's COM port and the router's Console. Use your Terminal/Hyper
Terminal (Baud Rate 9600, Data Bits 8, Stop Bits 1, Parity None,
Flow Control Xon/Xoff) to access the command prompt. Type "show
system" and check the configurations, or type "?"
for help. If you find out that the configurations have been accidentally
erased, manually assign an IP (such as 192.168.1.1 255.255.255.0)
to the router then detect again.
Back to Top
Symptom:
Get the dial tone from analog phone attached
to the router, but when trying to connect, the event log shows "Clear
indication received" or "Making a data call, B1 channel,"
then it hangs and cannot connect.
Suggestions:
- Make sure you enter the ISP's phone number
correctly.
- Check with ISP to see if the line is busy
or out of service.
- Make sure you follow the ISP's "dialing
format." Most ISPs provide local access number. You can first
try dial as a local call (phone #), or as a long distance call (1+area
code+phone #), or (area code+phone #). Some ISPs require users to
dial the ISP phone number as long distance, even it is a local call.
Or you might get different results, such as different transfer rate,
when using a different dialing method. Please check with your ISP
for more details.
Back to Top
Symptom:
Click the connect button but get disconnected
right away.
Suggestions:
- Check your SPID registration (see How
do I know if Switch Type and SPID register passed?).
Sometimes the router losses the SPID registration. This may be caused
by an electric short or an out of service ISDN line. Re-register
the SPID, or check with the phone company to see if the line is
out. Make sure the ISDN cable is plugged in to the router and ISDN
wall jack correctly.
- Check your transfer speed. Most phone companies
and ISPs support 64Kbps/channel capability. However, some ISPs only
support 56Kbps/channel or Data-Over-Voice only. Confirm the maximum
speed for your ISP's and phone company's ISDN connections.
Back
to Top
Symptom:
Appear connected because the B1 channel's
LED was green in the Status window, but then it disappeared and router
disconnected.
Suggestions:
- Please go to the Event Log. If you see the
messages "PAP login failed" or "CHAP login failed,"
verify that your User Name and Password are correct in the Authentication
configuration panel under the ISDN Interface menu of Advanced.
- Check with your ISP to make sure that the
ISDN account has been set up correctly.
- If you are using Static IP, verify your
Router's IP address (LAN IP configuration panel under the LAN Interface
menu of Advanced) and ISP's router IP address (ISDN IP configuration
panel under the ISDN Interface menu of Advanced).
Back to Top
Symptom:
Can connect with only 1 channel.
Suggestion: Check your Multilink PPP
setting. From the Multilink PPP configuration panel under the ISDN
Interface menu of Advanced, select either "Dynamically Use One
or Two Channels" or "Always Use Two Channels." You
should be able to connect with B1 and B2channels. Remember if Multilink
PPP setting is set to "Dynamically...," you will need to
have higher volume of traffic to trigger the second channel. If the
traffic volume is not high enough, the second channel will not be
activated.
Back
to Top
Symptom:
After setting the Multilink PPP as "Always,"
can connect with B1 channel, but the router keeps trying to bring up
the 2nd channel, but it never gets connected.
Suggestions:
- Make sure that the phone company has provisioned
your ISDN line for data on both channels.
- Confirm that your ISP has configured your
ISDN account for data on both channels.
- Some ISPs require a second ISDN phone number
to access the second channel. Check with your ISP to find out if
they has a second ISDN phone number. If they have another ISDN phone
number, enter it in the Multilink PPP configuration panel under
ISDN Interface menu of Advanced.
Back to Top
Symptom:
Configure the Multilink PPP setting as
"Dynamically." When I start a download session, the second
channel connects and disconnects after a few seconds.
Cause: The router is looking for an
available port on the ISP's server. If the server is busy, you will
need to wait for a free port. If your download session is relatively
small, the second channel will be dropped before it gets connected.
Back to Top
Symptom:
Can make a connection, but cannot ping
or browse.
Suggestions:
Check your PC's default gateway setting, from
the IP Routing Table configuration panel under the Protocol Configuration
menu in Advanced. The gateway IP address should be the IP address
of the router .
- Try to access a different network via browser
or pinging. The network you have been trying to access could be
down.
- Try to ping or browse by IP address. For
example, you can type 207.214.100.35 (ARESCOM's web site)
in your browser's address column, instead of "http://www.arescom.com."
If you can ping or browse by IP address, check your DNS setting.
Usually DNS is provided by ISP when you dial in. But some ISPs require
users to enter a DNS IP address. Contact your ISP for more information.
- If you still cannot receive a reply, contact
your ISP and check your account settings. This may be caused by
an incorrect Subnet Mask.
- If you are using v3.0 or higher software
and firmware, check your routing table. If you have trouble setting
up your routing table, see the Routing
Table Setup Technical Note.
If you are using IP Master mode
- Check your PC's default gateway setting,
from the IP Routing Table configuration panel under the Protocol
Configuration menu in Advanced. The gateway IP address should be
blank.
- Try to access a different network via browser
or pinging. The network you have been trying to access could be
down.
- Try to ping or browse by IP address. For
example, you can type 207.214.100.35 (ARESCOM's web site)
in your browser's address column, instead of "http://www.arescom.com."
If you can ping or browse by IP address, check your DNS setting.
Usually DNS is provided by ISP when you dial in. But some ISPs require
users to enter a DNS IP address. Contact your ISP for more information.
- If you still cannot receive a reply, contact
your ISP and check your account settings. This may be caused by
an incorrect Subnet Mask.
If you are using IP Master mode, but you
have reserved an IP address for a particular PC or Workstation
- Check your PC's default gateway setting,
from the IP Routing Table configuration panel under the Protocol
Configuration menu in Advanced. It should be the IP address of
the router (Note: If you are using v2.x software and firmware,
it will be 192.168.1.1. If you are using v.3.x software and firmware,
it will be the IP of the router that you have assigned.)
- Try to access a different network via browser
or pinging. The network you have been trying to access could be
down.
- Try to ping or browse by IP address. For
example, you can type 207.214.100.35 (ARESCOM's web site)
in your browser's address column, instead of "http://w NS is
provided by ISP when you dial in. But some ISPs require users to
enter a DNS IP address. Contact your ISP for more information.
- If you still cannot receive a reply, contact
your ISP and check your account settings. This may be caused by
an incorrect Subnet Mask.
Back to Top
|
