PCI ISDN Card Adapter Readme for RAS through NDIS/TAPI Miniport Driver with Stollmann tina-PCI under Windows NT 4.0 Copyright OEM License 1. General There are two ways to connect a Windows NT computer to ISDN: - Integration via NDIS-Miniport driver (this floppy) - Integration via serial modem driver and COM-Port (a different product, please contact your dealer for further information) This floppy contains the software necessary for the integration via NDIS/TAPI Miniport. It supports one/two B-channel with up to 64.000 bps. This floppy contains the following files: - oemsetnt.inf Installation script for NT - readme.txt This text - colwmac.sys NDIS/TAPI Miniport driver - isdnmsg.dll DLL for display of eventlogs - isdncfg.dll DLL for configuration *************************************************************** 2. PCI ISDN Card adapter 2.1 Installing PCI ISDN Card hardware Install the PCI ISDN Card as described in the manual. Configure the port of the PCI ISDN adapter on a free interrupt (see manual of PCI ISDN Card). 2.1.1 Updating from previous version Please deinstall the PCI ISDN Card from RAS and from the list of network adaptors and install it with the new version again. While installing make sure that you choose the installation from the floppy and not from harddisk. 2.2 Installing COLWMAC Install RAS and your LAN protocols before you install the PCI ISDN Card NDIS driver. Choose a port like COM2 for RAS installation. The driver is to be installed with the "Control Panel". Start "Network" and "Add Adapter...". Now you get a list of the available adaptors. Select "Diskette" to force the system to load the files from the floppy onto the harddisk. Select "PCI ISDN Card". Select the D-channel protocol you will use. Please enter the telephone numbers (phone 1 and phone 2) you will use. If you have only one telephone number you may leave the second phone number blank. Now you can configure your MSN's. - For incoming calls you can select followings: 1 Only phone number 1 1+2 Both phone numbers 1 and 2 2 Only phone number 2 all All MSN's will accept incoming calls. - For outgoing calls you can select followings: 1 Phone number 1 2 Phone number 2 will be used within outgoing call. By using US D-Channel protocols like NI-1, DMS-100 or NI-2 you have to enter SPID's for each phone number you will use. After that, please change to "Network Services", choose "Remote Access Service" and call "Add..". Add the ISDN (ISDN1) colwmac to the list of devices and delete other devices, if not used. Afterwards close "Network Settings" and restart Windows NT. To use both B-channels simultaneously please install ISDN (ISDN2) colwmac too. 2.2.1 Interrupt number The interrupt number is configured by your WinNT system. 2.2.2 I/O address The I/O address is configured by your WinNT system. 2.2.3 D-channel protocol Following D-channel protocols are supported by PCI ISDN Card: - DSS1 - 1TR6 - VN-4/5 - NI-1/2 - DMS 100 2.2.3.1 Public ISDN, DSS1 The DSS1 protocol is the common European protocol. Most of the new ISDN-interfaces in Germany support DSS1. Other countries supporting DSS1 are: Finland, Sweden, Denmark, Norway, The Netherlands, Portugal, Spain, Italy, Switzerland, Austria and many others. The data transfer service of the ISDN interface has to be configured in the switch or the PABX. 2.2.3.2 Private switches (PABX) PABXs use different protocols, including 1TR6, DSS1, DKZE and proprietary protocols. If in doubt, consult the vendor. The data transfer service of the ISDN interface has to be configured in the switch or the PABX. 2.2.4 Multiple Subscriber Number (MSN) You can distinguish different ISDN terminals by a different MSN (DSS1). With this parameter you select a specific MSN for the PCI ISDN Card. 2.3 Running COLWMAC After you have restarted your computer, you can start "RAS" from the "RAS" program group and add an entry into the telephone directory. Select the COLWMAC (ISDN) at the "Port" pull down. If it is not existing, maybe you did not configure the RAS port for dialling out. If ok, close the "Add" window and dial. You can get connections to most data terminals on ISDN, but to get any data transfer it has to support the PPP protocol in a Windows NT compatible way. If you call a Windows NT RAS Server, you will be prompted by "Verifying user name and password" if the connection is established. If the connection fails, check the eventlog. You will find an entry with the ISDN cause. If the logon process does not suceed, check the following settings on the RAS server and client: - user accounts - domain trustees - network protocols - security settings, type of password encryption To check the status of the RAS server process choose "RAS Administration" from the RAS window. To be able to handle incoming calls RAS has to be started. If you double- click the bar, you get additional status information on the ports. 3. Troubleshooting - Driver not loaded If the driver is not loaded at restart of the computer, check the Event Viewer and save it in a file. - COLWMAC entry does not exist in RAS port list During installation, it may happen that the entry COLWMAC does not exist in the window "Network Software", "Remote Access Service". In this case please deinstall the PCI ISDN Card and repeat the complete installation. - RAS Error 640, invalid TAPI configuration: Remove "PCI ISDN Card" from "Network Settings", remove COLWMAC from "RAS Configuration" under "Network Settings" and restart the PC. Afterwards install the "PCI ISDN Card" again and configure RAS to it. - RAS Error 651: The partner you have called does not react. Check the number you have dialed. Check if the computer you have called is running and the line is not busy. Check if the RAS of the computer you are calling is configured as server (not client only). - No user responding 0x34BA (Event Log) The number settings are not correct. You call another ISDN line, but there is no data terminal responding. The reasons can be: - the number you call does not address the ISDN bus your NT-Server is connected to. If the calling client is connected to a PBX you have to dial a prefix to access the public ISDN. - the MSN you have programmed in the called NT server is different from the number which is transmitted with the call in the DAD from the public/private switch. Set MSN to wildcard to accept all incoming calls. - You cannot be called There is no way to check your own ISDN number by yourself without any doubt. Make sure that you configured RAS as server (not client only). ****************************************************************** ****************************************************************** ****************************************************************** PCI ISDN Card CAPI 2.0 Protocol Readme for Windows NT CAPI Copyright OEM License 1. General Supported CAPI versions - CAPI 2.0 is supported by CAPI2032.DLL This floppy contains the following files: - oemsetnt.inf Installation script for NT - ndiscapi.sys CAPI transport provider for NDIS - capi.sys CAPI 2.0 kernel mode driver - capi2032.dll CAPI DLL - isdncfg.dll DLL for configuration For programing details please refer to the CAPI 2.0 specification. We suggest to use CAPI 2.0 which is based on DSS1. It will replace CAPI V1.1 which was designed for the German national ISDN. 2. Installation - Before installing the CAPI-Interface you have to install NDIS- Interface. This NDIS-Interface can you download from our Mailbox. - Now you can install the CAPI-Interface by choosing "Control" Group further "Network", "Software" and "DISK". Switch to A:\CAPI and say OK. 3. Troubleshooting If you face problems please use a development environment with two NT machines and use kernel debugging. The kernel debugger output is collected in a file on the debug monitor computer and can be sent for support purposes. You find details on kernel debugging on the MSDN developer CD.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.