Possible Faults and Remedies
180
ISDN PC Card – 13 Using NDIS
•
Fault condition:
CAPI applications that answer incom-
ing data calls (with the service indicator DATA64K) are
not functioning alongside the NDIS WAN CAPI Driver in
RAS server mode.
Possible cause:
Both the CAPI data application and RAS
with the NDIS WAN CAPI driver are trying to answer the
same calls.
Solution:
Assign a different Multiple Subscriber Num-
ber (MSN) to each application so that incoming calls
can be differentiated.
•
Fault condition:
Unable to establish PPP connection
Possible cause:
The Windows 95 ISDN Accelerator Pack
v1.1 uses the Point-to-Point Protocol (PPP) over ISDN as
specified in RFC 1618. This protocol is also referred to as
synchronous PPP, and is a standard in ISDN internet-
working.
Solution:
The remote site, i.e. your Internet Service Pro-
vider must also support this standard.
•
Fault condition:
Multilink PPP connections are not pos-
sible.
Possible cause:
Your Internet Service Provider (ISP)
does not support multilink PPP connections, or you
have not configured the RAS server with a second mo-
dem entry for incoming calls.
Solution:
Ask your I SP whether multilink connections
are supported, and whether they areenabled for your
account. On your RAS server, configure a second ISDN B
channel for incoming calls.
•
Fault condition:
Multilink PPP connections to a RAS
server are extremely slow.
Possible cause:
You are using the ISDN CAPI Port driver
at one end of the RAS connection, and the NDIS WAN
driver at the other end.
Solution:
Use the same driver at both ends of the con-
nection, i.e. either the ISDN CAPI Port driver or the NDIS
WAN driver. Avoid mixed operation of the two drivers.
