Novell is now a part of Micro Focus

Accessing the Internet with Eicon's SCOM for IntranetWare Kit

Articles and Tips: article

Senior Post Sales Engineer
Eicon Technology

01 Sep 1997

Connecting your Novell IntranetWare users to the world-external resources, corporate intranets, and the Internet-has never been easier. This AppNote tells how to do it with Eicon Technology's WAN hardware.


The growth of the Internet as a mandatory tool for business has resulted in the need for an Internet connection. Many customers with small IntranetWare-based LANs want to be able to access the Internet via an Internet Service Provider (ISP).

The SCOM for IntranetWare Kit from Eicon Technology is a good solution for providing LAN users with access to the Internet. This solution allows users to maintain IPX connectivity between workstations and the IntranetWare server, while simultaneously allowing access to the Internet through their ISDN-enabled IntranetWare server. The workstations do not need to have IP enabled; all they need is IPX. To accomplish this, they make use of Novell's IPX/IP Gateway, which is part of IntranetWare.

This AppNote provides detailed step-by-step instructions on how to provide an effective Internet solution for Novell LAN users. It includes relevant background information, tips, tests, and handy hints to help you successfully implement this solution.

The SCOM for IntranetWare Kit described in this AppNote retails for approximately US $1,000 and is available through Eicon's regional distributors: Azlan and Computer 2000 Adcomp. Further details on Eicon's line of WAN solutions for Novell can be found on the web at

A Quick Look at ISDN

Today, many ISPs support Integrated Services Digital Network (ISDN) as an access network because it has many advantages over dial-up modem connections. These advantages include:

  • High bandwidth (64Kbps or 128Kbps)

  • Fast connection setup time (typically 1 to 3 seconds, compared to 30 seconds for a modem)

  • Digital, synchronous connection for practically error free, more efficient communication

These ISPs are normally based on the Point-to-Point Protocol (PPP) and are configured to support single, dial-up users. ISPs generally handle these dial-up users by dynamically allocating an IP address when a user connects. This reduces the degree of administration required and also makes more efficient use of available "legal" IP addresses. In this environment, an ISDN connection must meet the following requirements:

  • It must be based on PPP.

  • It must support dynamic IP address allocation.

  • It must offer dial-on-demand (so it connects only when users need it).

  • It must support the most common TCP/IP protocols: SMTP (for mail), HTTP (for web) and FTP (for file transfer).

Using a combination of products from Eicon and Novell, such Internet access is now possible. The basic requirements to enable such connectivity are simply:

  • Novell's IntranetWare

  • Eicon's SCOM for IntranetWare Kit (includes Eicon SCOM ISDN Card + Software Drivers + Novell's 36-Port Licence)

Note: The standard IntranetWare Server hasonly a one-port licence for WAN connections.Therefore, if you want more than one WAN connection(for example, if you want to use both ISDNchannels on the SCOM card), you need thelicence included in the Eicon SCOM for IntranetWareKit.

The scenario described in this AppNote uses Eicon's SCOM ISDN card. A full range of Eicon cards, including the new Diva Server family of cards, is supported in the same environment. See "Eicon Hardware Support" at the end of this AppNote for a complete hardware compatibility listing.

About Eicon's SCOM Card

The SCOM card provides the interface to an ISDN Basic Rate service, and allows you to connect one or two 64Kbps "B" channels at a time to ISDN destinations. The two "B" channels can be connected to two separate locations, or alternatively both can be connected to the same remote location, thus giving you a 128 Kbps connection. (See "Using MultiLink PPP" later in this AppNote for details on MultiLink PPP support).

Technically speaking, Eicon provides a CAPI 2.0 driver for the SCOM card. Novell provides routing functionality which "sits on top" of CAPI 2.0 and allows IntranetWare to use the SCOM card to make an ISDN connection to the ISP.

Various Eicon cards (such as SCOM) provide CAPI 2.0 support. This means that Eicon cards can also be used simultaneously to support Netware Connect and Fax Solutions such as Tobit Faxware (as these applications are CAPI 2.0 based). A complete integrated solution for Internet access, routing, remote access, and faxing is thus available on one Eicon card.

How Does It All Work?

A typical small LAN has several Windows 95 workstations using IPX to access an IntranetWare server for file and print services. The users want to access, for example, Internet web sites using a browser such as NetScape or Internet Explorer. By purchasing only an SCOM for IntranetWare Kit, this is now possible. No other software is required.

On the IntranetWare server, the customer can add the Eicon SCOM card which provides the ISDN communications link to the ISP. Usually LAN connections to the ISP demand expensive "Numbered IP" links (in other words, a reserved IP address). With this setup, however, it is possible for the SCOM card to obtain a dynamic IP address from the ISP. The ISP sees the connection simply as one single remote user. The IntranetWare-based LAN has now acquired an inexpensive Internet access method.

Generally, each LAN workstation requiring access to the Internet also needs its own IP address. LAN administrators usually require a considerable degree of technical understanding to implement TCP/IP on a LAN. With this solution, however, there is no need for TCP/IP on the LAN at all. Instead, by enabling Novell's IPX/IP Gateway (which is part of IntranetWare) on the LAN, the Windows 95 workstations need IPX only. A Windows 95 client running a browser such as NetScape passes all requests for Web pages and other Internet data inside of IPX packets. From the users' perspective, there is only IPX. The IntranetWare server takes care of the conversion to proper IP packets before supplying the packets to the SCOM card for forwarding to the ISP. As a positive side effect, this removes the need for a firewall on the LAN.

This solution thus provides a cheap, secure, powerful, and easily administered connection to the Internet for all LAN users.


This section takes a look at what's needed to get started.


  • Novell IntranetWare 4.11 operating system + Novell Internet Access Server (NIAS) installed

  • Novell IWSP2 Patch (minimum) installed

  • Eicon SCOM Card physically installed (note your hardware settingsas specified in the SCOM manual


  • Novell's 32-bit client for Netware installed (use the latest available version)

  • A Web Browser such as NetScape or Internet Explorer installed

ISP Connection Details

The following details about the connection should be provided by the ISP:

  • ISDN Number (of the ISP's ISDN access device)

  • Username and Password

  • Authentication Type (PAP, CHAP, and so on)

  • IP Address of the ISP'sDomain Name Server (for Name Resolution)

Installation and Configuration

This section provides installation and configuration details.

Installing the Software Drivers

Before you begin the installation, fine the Connections for NetWare 96.2 CD in the SCOM IntranetWare kit (the required software is also available on the web at Installation of software on an IntranetWare Server is based on the INSTALL.NLM utility.

  1. Type LOAD INSTALL <Enter<at the server console.

  2. Select Product Options, then select "Install a Product Not Listed".

  3. Press <Ins< and then <F3< to specify the source path for the software. Generally, you can use the following (where D: specifies the drive letter for the CDROM):


  4. From the Installation Options menu, select "Install Product".

  5. From the Install to Servers screen, select the local server name from the list.

  6. Answer "Yes" when prompted to start installation. This will install the ISDNCAPI drivers required for the SCOM Card.

    Once the installation is complete, RESTART your server before beginning the actual configuration.

Configuring the IntranetWare Server

This section takes you through the complete process of configuring the SCOM card in the IntranetWare Server. It also contains details on how to configure the IPX/IP Gateway.

The first step is to type LOAD INETCFG <Enter<. This is the main Novell utility for configuring both LAN and WAN interfaces. Then follow the steps described below.

Creating the CAPI Board and the ISDN SCOM Board. Following these steps will create the configuration for the physical Eicon SCOM board and the logical CAPI board.

  1. From the INETCFG Main Menu, select "Boards".

  2. Press <Insert< and choose "WHSMCAPI" as the board.

  3. Name the board "SCOM1".

  4. The WHSMCAPI Board configuration screen should now appear. Select the CAPI Boards Options Menu.

  5. When prompted "Should INETCFG automatically load the CAPI Driver", answer "Yes".

  6. When prompted to "Select a CAPI Driver", select DSCAPI20 (for the SCOM Card).

  7. The CAPI Board Configuration panel appears. The number of B-channels should be set to 2. When MAXPORTS shows the desired value, press <Escape< to continue.

  8. From the WHSMCAPI Board Configuration panel, select "Driver Specific Configuration".

  9. The Eicon ISDN Card Configuration panel appears. The first time you enter this panel, the system will offer to "Automatically Scan" for newly installed ISDN cards. Answer "Yes". The utility should find your SCOM card for you.(If the card is not found, enter the hardware settings for the card which wererecorded earlier.)

  10. The Hardware Configuration panel should now appear. Select the Adapter now shown and alter the followings settings (if required):

    Adapter Name: Set to SCOM1 (it must be the same as the CAPI Board name above)

    ISDN Protocol: Select the ISDN protocol used by your ISDN service provider. In general, this is Europe and Other Countries, Euro-ISDN (E-DSS1) for European users.

    The remaining options may be set automatically for you. You can change them if necessary:

    Adapter Type:

    Select the SCOM adapter

    RAM Base:

    Enter the shared memory address selected on the adapter


    Enter the interrupt request level selected on theadapter.


    For basic ratecards such as SCOM, set this to Automatic.


    In most situations this should be set to Disabled.

  11. Press <Escape< and answer "Yes" to exit the Eicon ISDN Card Configuration panel.

  12. Press <Escape< and answer "Yes"to "Save Changes".

  13. Press <Escape< to return to the INETCFG main menu.

Configuring the CAPI Interface. Follow these steps to configure the CAPI interface.

  1. From the INETCFG Main Menu, select "Interfaces".

  2. Select the SCOM1_1 interface.

  3. Select PPP as the "Medium".

  4. The PPP Network Interface Configuration panel will be displayed. Make settings as follows:

    ISDN Address: Set to yourISDN Number (This number will have been provided to you by your PTT. This is not the ISDN number of the ISP).

    Modem/DCE Type: Set to ISDN (AT Controlled)

    The rest of the fields in this panel can be left at their default settings.

  5. Press <Escape< and answer "Yes" when prompted to "Save Changes?".

  6. Press <Escape< to return to the INETCFG main menu.

Configuring a Call Destination Entry for the ISP. Follow these steps to configure a call destination entry for your ISP.

  1. From the INETCFG main menu, select the "WAN Call Directory" option. You can now set up an ISDN Call Entry which will be used to connect to the ISP.

  2. Press <Insert< and enter a name such as ISDN-ISP for the "New Call Destination Name"option.

  3. When prompted to "Choose a Supported Wide Area Medium",select PPP.

  4. The "PPP Call Destination Configuration" panel will be displayed. Make settings as follows:

    Call Type:

    Set to On Demand (activated by data). This will ensure that ISDN calls are only made when required.

    Interface Name:

    Set to SCOM1_1.

    Telephone Number:

    Enter the ISDN number of your ISP.(Your ISP should have provided you with this information.)

    Idle ConnectionTime-out:

    Set the timer to an appropriate value such as 30 seconds.This controls when the ISDN line will be dropped if no data is being passed. This should beset if you want toensure that ISDN call charges will be kept to a minimum.

    Outbound Authentication:

    Set to the Authentication type required by your ISP.(Again, your ISP should have specified what Authentication is required).


    Enter the passwordas specified by your ISP.

    Local SystemID:

    Enter your username as specified by your ISP.

    Remote SystemID:

    Enter the ID as specified by your ISP (only required for CHAP).

    Inbound Authentication Update:

    Set to Disabled.

    The rest of the fields in this panel can be left at their default settings.

  5. Press <Escape< and answer "Yes" when prompted to "Save Changes?".

  6. Press <Escape< to return to the INETCFG main menu.

Configuring the Network Protocols. Follow these steps to configure the network protocols.

  1. From the INETCFG main menu, select the "Protocols" option.

  2. Select TCP/IP and press <Enter< to enable TCP/IP. (This assumes that you have not already enabled TCPIP or the IPX/IP Gateway).

  3. Select the "IPX/IP Gateway and DNS Resolver Configuration" option.

  4. The "DNS Resolver Configuration" panel now appears. Make settings as follows:

    IPX/IP Gateway: Set to Enabled

    Name Server #1: Enter the IP address of the DNS server at the ISP site. (This should have been provided to you by the ISP).

  5. Press <Escape< twice and answer "Yes" to "Update TCP/IP Configuration".

  6. You are next prompted to create an IPX/IP Gateway Server NDS Object. To do this, answer "Yes" when prompted to "Continue?". You must then enter the Username (ADMIN) and Password in the "Login Information" panel. This username and password should be the Admin account and password for the IntranetWare server.

  7. From the "Login Information" panel, select the "Select to Login" option to force the creation of this object. A new object will be created for the IPX/IP Gateway. Generally, it is called ServerName-GWwhere ServerName is the name assigned to your IntranetWare server.

    At this point you may also be prompted to increase the Maximum Packet Receive Buffers to 1000 to ensure the correct operation of the IPX/IP Gateway. Do this by using the Novell SERVMAN utility.

  8. Press <Escape< to return to the INETCFG main menu.

Configuring the Bindings. Follow these steps to configure the bindings.

  1. From the INETCFG main menu, select the "Bindings" option.

  2. Press <Insert< and select TCP/IP.

  3. When prompted with the "Bind To" option, select "Network Interface".

  4. Select "SCOM1_1" from the list of interfaces.

  5. You will be presented with the "Binding TCP/IP to a WAN Interface" panel. Make settings as follows:

    ISP or Remote Router will Provide the IP Address: Yes

    WAN Network Mode: Unnumbered Point to Point

  6. Select "WAN Call Destinations" and press <Insert<.

  7. The "WAN Call Destination to IP Address Mapping Configuration" panel is now presented.

  8. Select the "WAN Call Destination" option and set it to the WAN Call Directory entry name created earlier ("ISDN-ISP" in our example.

  9. Set the Type to Static On Demand.

  10. Select the "Static Routing Table" option and press <Insert<.

  11. The "Static Route Configuration" panel appears. Set "Route to Network or Host" to Default Route.

  12. Press <Escape< twice and answer "Yes" to "Update Database".

  13. Again press <Escape< twice and answer "Yes" to "Update Database." Control now returns to the "Binding TCP/IP to a WAN Interface" panel.

  14. Press <Escape< and answer "Yes"to "Update TCP/IP Configuration".

  15. Press <Escape< to return to the INETCFG main menu.

  16. Exit INETCFG, DOWN the IntranetWare server, and restart it.

This completes the IntranetWare Server configuration. You can now proceed with the client configuration.

Configuring the Windows 95 Client

First, make sure the latest Novell Netware Client 32 is installed and that the Windows 95 workstation can access the IntranetWare Server over IPX (no other protocol is required).

Enable the IPX/IP Gateway protocol on the client by completing these steps:

  1. On the Windows 95 desktop, right-click on Network Neighborhood.

  2. Select Properties.

  3. Select Add.

  4. Select Protocol and click on Add.

  5. Select Novell.

  6. Select the "Novell Netware IPX/IP Gateway". (If it is not available in the list, you can click on Have Disk and enter the \public\client\win95 path on the IntranetWare Server and select it from there instead.)

  7. You will be prompted to indicate where the IPX/IP protocol software support is located. Generally, it is located on the IntranetWare server under \public\client\win95.

    Once the software is installed, the Novell Netware IPX/IP Gateway option will be added to the list of Network Components.

  8. Select the Novell Netware IPX/IP Gateway option from the list of Network Components.

  9. Select Properties.

  10. Under the IPX/IP Gateway option, set your Preferred Gateway Server to the name allocated to your IntranetWare Gateway Server. The IntranetWare administrator should be able to provide this information. (Generally, if your IntranetWare Server is named INW411, the Gateway will be called INW411-GW by default.)

  11. Now exit Windows 95 and reboot the PC. Upon reboot, you should be provided with an option to Enable the IPX/IP Gateway. Enable this option, which should allow you to connect to your IPX/IP Gateway on the IntranetWare server.

The IPX/IP Gateway protocol should be enabled and working on the client. This completes the configuration of the client. The next task is to test your connection.

Testing the Connection

The IntranetWare server and the Windows 95 clients should now be ready for testing. This section describes how to perform a simple test. In addition, it provides useful information for troubleshooting and monitoring the connection to your ISP.

Ensuring the SCOM ISDN Card Has Loaded Successfully

A useful precursor to the initial tests is to verify that the SCOM ISDN card has been loaded successfully. To do this, simply type CONFIG <Enter< at the IntranetWare server console prompt. CONFIG provides you with information on the available interfaces configured for the server. One of these should be the CAPI Interface for the SCOM card.

You should see an interface with details similar to the following (the details will not match exactly):

CAPI Adaptation Layer Driver 03100P_1.INW 

  Version 3.00a    13 September 1996

  Hardware Setting: Channel  1

  Node Address: 000233A6DCBA

  Frame Type: PPP

  Board Name: SCOM1_1

. . .

If this CAPI Interface for the SCOM card is not shown, DOWN the server and verify the hardware settings of the card (refer to the SCOM manual for the hardware settings). Once the server is back up, you can use the IDICFG utility (type LOAD IDICFG) to change the actual hardware settings if required. (Any changes in IDICFG require you to RESTART the server for the changes to take effect). Once the CAPI interface for the SCOM card is shown in the CONFIG command display, proceed to the simple test outlined next.

A Simple Test

Here is a simple way to test the connection. On a Windows 95 client, load a browser such as NetScape and try to access an Internet web page. The request for an Internet web page will be passed to the IntranetWare server, whereupon the SCOM card should make a connection to the ISP. Once the connection is successfully made, the requested web page should be downloaded and passed to the Windows 95 Client's browser. If this test works, your LAN users can now access the Internet.

Note: Novell includes a PING utility with the IPX/IP Gateway protocol on the client.This utility can also be used to test the connection. A simple test is to use the PINGutility to PING the IP Address of the DNS Server at the ISP site. (The DNS IP addressshould have been supplied by the ISP.)

When no data is being requested from the ISP, an Idle Timer (set to 30 seconds during the configuration) will cause the ISDN call to be dropped after 30 seconds. The next time a web page is requested, another ISDN call will be made. This is how an "On Demand" connection to the ISP/Internet is achieved. Thus you are not charged for ISDN usage when no data is being passed.

Testing the ISDN Connection with a Manual Call

If the simple test does not work, the next step is to try a manual connection from the IntranetWare server to the ISP. This will isolate whether the problem is with the LAN itself or due to a failure with the ISDN connection.

Perform the following steps to try to manually make a call to the ISP:

  1. At the IntranetWare server console, type LOADCALLMGR <Enter<.

  2. Press <Insert< and select the ISDN-ISP Call Entry.

  3. Select IP.

  4. Press <Enter< to activate the ISDN call.

    If the call connects correctly, the Status in CALLMGR should show "Out-Connected". If this is the case, the problem is most likely LAN-based. Verify the connection between the Windows 95 workstations and the IntranetWare server. Also check that the IPX/IP Gateway functionality has been enabled on both client and server.

Once the Status displays as "Out-Connected", the ISDN connection to the ISP has been made successfully. You can now do a simple test with the Novell PING.NLM to test that the TCP/IP functionality is now working correctly. This can be done using the following command at the server console:


where X.X.X.X is the DNS IP Address supplied to you by your ISP. If the PING is successful, your IP connection is up and running.

If the attempt to make the manual call does not result in a status of "Out-Connected", the call to the ISP has not been made successfully. This generally means that there is a problem with the ISDN connection or in the PPP negotiation stage. You can debug the connection using several utilities. Two particularly useful utilities are considered next.

Monitoring the ISDN Connection and PPP Negotiation

To monitor the ISDN connection, you can use the Eicon XLOG.NLM utility. (Eicon's Customer Services staff regularly use this utility to see what is happening.) This provides low-level information and diagnostics on ISDN "D" and "B" channel activity. It allows you to determine the progress of the ISDN call and whether the remote location accepted the call. Start this utility by executing the following command at the server console:


This utility echoes all of the ISDN activity to the server console screen. In particular, you should check to see if a B Channel connection was made. If B-channel activity occurs, the ISDN call has been accepted by the ISP's ISDN device. In this instance, and where the ISP supports PPP, you usually find that the PPP negotiation on the B Channel has failed.

To monitor the PPP negotiation, use Novell's PPPTRACE.NLM. To load this, type:


This utility allows you to monitor the PPP negotiation between the IntranetWare server and the ISP. If a connection is not made successfully, you can see where the PPP negotiation may be failing. Common errors are at the Authentication stage where users often have the wrong username/password combination set. Another common problem is the setting of the wrong authentication type.

When problems are encountered, use of these utilities should facilitate correct problem determination. Once the problem has been rectified, you should be able to make a successful connection to the ISP.

Handy Hints

This section contains some useful additional information regarding IP addressing and making faster connections with MultiLink PPP.

How to Determine the IP Address You Are Using

To determine the IP address you are using, do the following at the IntranetWare server console:

  1. Type LOAD TCPCON <Enter<.

  2. Select "Protocol Information".

  3. Select IP.

  4. Select IP Addresses.

Assuming IP is not in use anywhere else but on the ISDN link, the IP Address shown under Host Name in the IP Addresses Table is the IP address that the ISP has assigned to you dynamically. If the Host Name shows "Unspecified", there is no ISDN call active to your ISP. As soon as it becomes active, the Host Name will change to show the IP address that the ISP has dynamically assigned to you.

Note: If the network adapter or anyother card in the IntranetWare server has TCP/IPenabled, it will also appear here.

Using MultiLink PPP

In the tests described in this AppNote, the connection was based on a 64Kbps connection. Use of MLPPP support with an SCOM card allows a 128Kbps connection to an ISP. However, this requires two ISDN calls or two B-Channel connections. Therefore you will be charged for two calls instead of one.

Novell has completed development of MLPPP support for IntranetWare, but at the time of writing it has not been released. However, due to Eicon's special relationship with Novell, this MLPPP support is available now with all Eicon cards listed in the "Eicon Hardware Support" section.

In the event that MLPPP support is required for the Internet connection, contact the ISP first to verify that they provide support for MLPPP connections. Eicon Customer Services will then be able to provide you with complete details on how to apply MLPPP support to your IntranetWare server.

Eicon Hardware Support

The tests in this AppNote are based on the use of the Eicon SCOM ISDN card. In addition, the following Eicon ISDN cards are all fully supported for use in similar environments:

  • Eicon Diva Server BRI

  • Eicon Quadro

  • Eicon S2M

* Originally published in Novell AppNotes


The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.

© Copyright Micro Focus or one of its affiliates