Del Mar College
CIS 306 - Managing NOVELL® Networks
Instructor: Michael P. HarrisIntranetWare 4.11
![]()
![]()
IntranetWare Administration Guide
7. Setting Up Modem and Internet Access with NetWare Connect
About NetWare Connect
IntranetWareTM for Small Business includes a software program called NetWare ConnectTM that allows users to share modems that are attached to the server (as opposed to individual workstations). You will need to install NetWare Connect if users will be
- Dialing in to the network from home or the field through modems attached to the server's COM ports or a communications adapter. The laptop or remote computer functions as if it were an actual workstation (node) on the network.
- Dialing in to the network to remotely control one of the workstations on the network via a workstation at a remote site. Processing is done by the workstation on the network (this solution requires additional third-party applications such as pcANYWHERE*, Carbon Copy*, ReachOut*, CloseUP*, LapLink*, etc.).
- Dialing out of the network to remote services such as bulletin boards or an Internet Service Provider's (ISP) host server.
- Using Apple Computer's Apple Remote Access* (ARAS) software to dial in and become a remote node.
NetWare Connect supports the industry standard Point-to-Point Protocol (PPP). Remote nodes can use the dialers provided or any compatible third-party PPP dialers to establish an IP (Internet Protocol) or an IPXTM (Internet Packet ExchangeTM ) connection with the NetWare Connect server.
Security can be enabled or disabled globally or on a per user basis for a NetWare Connect service. The default allows all users complete access; however, the administrator can use the NetWare Connect Configuration utility (NWCCON) to restrict users to specific telephone numbers when they dial out or to restrict modem port access to the server.
The administrator can also configure NetWare Connect to require Remote Client passwords. Users calling in will be required to supply this password, in addition to their network log in passwords, to establish a connection with the NetWare Connect server.
To set up NetWare Connect, you must install and configure software both on the server and on workstations that will take advantage of NetWare Connect services.
Server. You will need to set up modems and other communications devices on the server, install NetWare Connect on a Small Business server, and then set up connection services for your particular needs.
Workstations. You will need to install the NetWareŽ Asynchronous Services InterfaceTM (NASITM ) and a dialer on each remote workstation or laptop needing to dial in to the server via a modem or on each network workstation needing to dial out to the Internet. Procedures for setting up workstations differ depending on whether the workstation uses Windows* 3.x* or Windows 95*. For example, Windows 95 includes a built in dial-up adapter that is not available in earlier Windows products.
This document provides basic information about installing and configuring a default setup that should be sufficient in most Small Business environments. If you need additional information, refer to the NetWare Connect online documentation included with this product. Cross-references to complete explanations are included at strategic points throughout this document.
Setting Up the Server
Setting up NetWare Connect on the server includes the following:
- Installing modems and other communications hardware
- Installing NetWare Connect on a Small Business server
- Configuring NetWare Connect
Setting Up Modems and Other Communications Devices
Before you install NetWare Connect, set up the server modems and other communications devices.
A modem can be configured to provide dial-in, dial-out, or both dial-in and dial-out capability. While a single modem will be sufficient for some networks, you will need additional server modems in any of the following situations:
- If you use other programs such as GroupWiseTM Remote, an uninterrupted power supply (UPS), or a fax system, for example, that also require dedicated modems (NetWare Connect does not share modems with other applications).
- If you have users who need guaranteed access to critical applications and need a 1:1 port-to-user ratio; otherwise, one port can generally support five users.
- If several users will consistently need simultaneous access to the modem (only one person can access a particular modem at a time).
To set up the server modems, complete the following steps.
Procedure
Set the modem's dip switches.
Refer to the modem manufacturer's documentation for recommended settings.
Make sure the I/O port address and RAM buffer address do not conflict with those being used other adapters in the NetWare Connect server.
Insert internal modems into an available slot or plug external modems into the computer's COM port according to the modem manufacturer's instructions.
Any built in PC* serial port (COM port) can be used with NetWare Connect. The COM ports are controlled through a COM driver NLMTM file (AIOCOMX.NLM) that is provided with the product.
To improve performance or to provide additional ports, you may want to purchase a multi-port communications adapter. These adapters feature separate, independent processors and data buffers to allow speeds and reliability greater than the PC's COM ports provide. Each communications adapter requires a related AIO (Asynchronous Input/Output) driver that is shipped with the adapter.
Novell certifies third-party communications adapters and drivers for use with NetWare Connect. For your convenience, the AIO drivers for some certified adapters are supplied with the product. For an updated list, contact the Novell Labs FAX Back system. For U.S. customers, the number is 1-800-414-LABS; for customers outside the U.S., the number is 801-861-2776, extension 2.
We also recommend installing applications on the remote workstation and not on the network. Running applications from the server can be quite slow.
Turn the modems on.
NOTE: For additional information about modems, communications adapters, phone lines, or other communications equipment, refer to " Preparing for the Installation" in the NetWare Connect 2.0 Installation and Basic Configuration Guide (NetWare Connect online documentation).
Installing NetWare Connect
NetWare Connect needs to be installed on only one network server. Before you begin, make sure the NetWare Connect server meets the following minimum requirements:
- Server software has been installed according to the instructions in "Install Server Software" in the Installation Guide em> (Small Business online documentation).
- At least 24 MB of memory is available. NetWare Connect needs 8 MB in addition to that needed by the server.
- Appropriate communications adapters (digiboard or standard COM ports) are available and installed as needed.
- Analog phone lines are available.
To install NetWare Connect, complete the following steps.
Procedure
Connect all hardware (communications adapters, modems, phone lines) before you begin the install.
Insert the NetWare Connect CD-ROM into the server's CD-ROM drive.
Mount the CD-ROM as a NetWare volume. At the server's console prompt, enter the following commands:
LOAD CDROM <Enter>
CD MOUNT NWC20 <Enter>
NWC20 is the volume name assigned to the NetWare Connect CD-ROM.
At the server's console prompt, type
LOAD INSTALL <Enter>
From the Installation Options menu, select Product Options.
Select Choose an item or product listed above.
Select Install NetWare Connect v2.0.
A screen appears that provides instructions for both floppy diskette and CD-ROM installations. For CD-ROM installations, the path should be NWC20:\NWC20\DISK1 .
Supply a path to the NetWare Connect CD-ROM.
- If you have not changed the default path, press <Enter> to continue.
- If you have changed the default path, press <F3> and type in the new path.
Log in to Novell Directory ServicesTM when prompted.
The ADMINs current NDS login name is displayed (CN=Admin. O=server_name).
Press <Enter> to continue.
Enter the current ADMIN password.
Unless you have changed the default since installing the server, ADMIN has no password.
Press <Enter> to continue.
Indicate where to install NetWare Connect. Select Install on this Server.
Files will be copied from the CD-ROM to the server.
Install licenses.
When prompted, insert the license diskette (the diskette distributed with IntranetWare for Small Business) in an available floppy drive and press <Enter>.
When you are notified that the license has been successfully installed, Press < Enter> .
Remove the license diskette from the floppy drive.
Complete the install. Press <Enter> when you are notified that the installation has been completed successfully.
The program returns to the Other Installation Actions menu.
Exit Install by pressing <Esc> twice and selecting Yes.
Reboot the server.
At the server's console prompt, type
DOWN <Enter>
EXIT <Enter>
The program returns to the C:\NWSERVER directory.
At the C:\NWSERVER prompt, type
SERVER <Enter>
The software reloads the NetWare Connect server and returns to the server's console prompt.
Configuring NetWare Connect
The first time you configure NetWare Connect, an automated configuration program is available to you. This automated configuration helps you identify and load communications (AIO) installed on the server, select modem types, and modify the AUTOEXEC.NCF file so that you do not (NetWare Connect online documentation) for complete information about changing NetWare Connect parameters.
To configure NetWare Connect, complete the following steps.
Procedure
Start the automated configuration. At the server's console prompt, type
LOAD NWCCON
Create the Novell Directory Services Connect object.
At the "Directory Services login/authentication" screen, accept the default settings for Connect Rights level (root) and Administrator's Name so that user ADMIN will have rights to manage NetWare Connect. This can be changed later if necessary.
Enter the current password for user ADMIN, if any.
The program creates the object (Connect_servername) and then continues with the configuration.
(Optional) View instructions.
Indicate whether you want to view instructions as you complete the rest of the configuration setup.
If you select Yes an instruction screen appears. Press <Esc> and then <Enter> to return to the configuration program. To access these instructions during the configuration process, press <F8> .
NOTE: Context-sensitive help is also available to explain options on most screens. To access help, highlight the option or entry box, press <Enter> and then press <F1> .
(Optional) Add additional licenses.
Indicate whether you want to install additional licenses. Additional licenses can also be installed later using NWCCON.
NOTE: Each Small Business server includes two NetWare Connect port licenses. If you have purchased other servers, you can use their NetWare Connect licenses as "additional" licenses. (We recommend that you install NetWare Connect on only one server.)
To install these additional licenses, insert the diskette that came with the other servers when prompted for a license diskette. The licenses will be added to this NetWare Connect server. A screen is displayed listing the total number of licenses and the serial number for each license. To continue, press <Esc> and confirm your changes.
Load the AIO (Asynchronous Input/Output) drivers for the modem or communications adapters you are using.
Select Yes to define AIO ports and press <Enter> .
From the list that is displayed, select the serial adapter you are using or the type of port the modem or communications adapter is connected to.
- To support a modem or an adapter installed in the server, select Built-in serial port (COMx), and press <Enter> .
- To support an external communications adapter or an external modem, select the adapter or modem you are using from the list that is presented.
If you have not changed the adapter's factory settings, the configuration program automatically loads the AIO driver and maintains its factory default settings.
If you have changed the factory default settings, you will be prompted to supply a name for the adapter (enter any name that distinguishes this adapter from others in your system), along with I/O and Memory Base addresses, as needed. Supply the information requested, press <Esc> , and confirm your changes.
When prompted to load additional drivers, select Yes if you are using more than one adapter or modem. Other wise, select No and skip to Step 6.
(Conditional) Repeat Steps 5b and 5c to load additional drivers.
For example, if a modem is using COM1, load an AIO driver for COM1; if a second modem or communications adapter is using COM2, load an AIO driver for COM2, and so on.
COM ports generally default to following values:
LOAD AIOCOM1 PORT=3F8 INT=4 LOAD AIOCOM2 PORT=2F8 INT=3 LOAD AIOCOM3 PORT=3E8 INT=4 LOAD AIOCOM4 PORT=2E8 INT=3
When all drivers have been loaded, continue by selecting No at the prompt to load more drivers.
A screen appears displaying the AUTOEXEC.NCF file and prompting you to update the file.
Update the AUTOEXEC.NCF file.
Position your cursor in the AUTOEXEC.NCF file and press <Insert> . All AIO drivers you specified in Step 5 are inserted into the file.
NOTE: Commands for the AIO drivers should be inserted after the LOAD commands for the LAN drivers. Placing the commands in the AUTOEXEC.NCF file automatically loads the adapters whenever the server is rebooted.
Press <Esc> and confirm your changes.
Identify Modems.
NetWare Connect will try to autodetect any modems connected to the server's ports.
Follow the screen prompts to configure your modems.
- If the modems can be autodetected, a form appears identifying the ports that have modems attached and listing the number of licensed ports.
Make sure all of your ports have been discovered. In addition, make sure the total number of ports found (plus the x.25 ports) is less than or equal to the modems found on licensed ports. If the total number of ports found exceeds the number of licensed ports, you will need to add additional licenses.- If the modem cannot be autodetected, the computer beeps to warn you. Do the following:
Press <Enter> to clear the warning message.
From the list of modem and port assignments, select any modem for which None is listed and press <Enter> .
From the list of manufacturers and models presented, select your modem.
Repeat this process for any other modems that were not detected.
If your modem isn't listed, you can generally use a generic Hayes*- compatible modem that has the same speed as the modem you are configuring. Be aware, however, that some modems don't respond well to generic scripts. Another alternative is to pick a model from the same manufacturer that has similar characteristics and speed.NOTE: The list of supported modems is constantly being updated. Scripts for new modems are available on the NovellŽ web site at Novell.com\technical support. Search for NWCMOD.EXE files. The files are self-extracting zip files that contain two files with an .MDC extension. These files need to be copied into the SYSTEM\AIO directory on the server. An accompanying text file provides instructions.
When all modems have been detected or added to the list, press <Escape> and then choose Continue with Automated setup.
Select needed services.
Enabling the services below will allow users to access the server's modem for both dialing in and out. Doing so centralizes and controls all asynchronous connections to or from a site so that workstation communications applications such as pcANYWHERE, LapLink, Internet Dialers, and many other applications have access to dial-in or dial-out capabilities from the centralized modem or modem pool attached to the server.
On the server side, you will need to set both NCS (the server's NASI Connection Service) and PPPRNS (Point-to-Point Protocol Remote Node Service) to Yes and configure at least an IPX connection. In addition, you will need to install NASI software on the workstation so that the workstation can establish a connection to the server. Refer to "Install Win2NCS."
Service Activate If NCS Dialing out. Allows any LAN workstation to dial out to remote host computers or bulletin boards.
Dialing in. Allows users to remotely control a workstation on the LAN. Allows remote PC's to dial in using third-party remote-control applications (such as pcAnywhere) to access a dedicated host PC or application server on the LAN.PPPRNS Dialing in from remote nodes. Allows users to dial in to the server's modem from a modem in a remote node (laptop or workstation) using IPX or IP connections. DOS and Windows workstations are supported. ARAS Dial-in and dial-out services for AppleTalk*.
Highlight NCS, as needed, and press <Enter> .
You are prompted to activate the service. No configuration is necessary.
Highlight PPRNS, as needed, and press <Enter> .
The List of Protocols for Service menu appears listing IPX and IP options.
Protocol Configuration Options IP Should be configured if users will be using applications that require IP connections or if the server maintains a direct connection to the Internet. IPX Should be configured if users need to log in to and access the NetWareŽ server from a remote node.
Highlight the IP option, as needed, and press <Enter> .
IMPORTANT: In most instances, you will not need to set IP parameters unless this NetWare Connect server will connect to the Internet. In this case, only your Internet Service Provider can supply appropriate addresses.
If you are setting up local IP addresses for only your own company and are not connecting to the Internet, you can define your own IP addressing scheme (press <F1> for help on parameters).
Set the IP parameters as indicated below. Press <Esc> twice to save changes and exit the window.
Local IP Address. This address is usually provided by your Internet Service Provider.
Subnet Mask. Accept the default setting (255.255.255.0) unless your Internet Service Provider specifies otherwise.
Specify Client Address Range (Optional). To change the default (No) and specify a range of addresses to be used by clients, highlight the Specify Client Address Range field and type Y , then enter starting and ending points for the range in the Client Address Range Start and End fields.
NOTE: If you decide to specify a range, TCP/IP addresses within the range are reserved for users dialing in from remote workstations; such addresses are dynamically allocated when the remote connection is made.
Use Header Compression. Header compression reduces the size of the IP packets. This is useful if you are using Novell's dialer with Windows 3.x; however, the Windows 95 dialer uses a different compression mechanism, so setting Header Compression here has no effect.
Highlight the IPX option, as needed, and press <Enter> .
Type a unique network address (different from any other IPX address on the LAN) in the entry field. To continue, Press <Enter> , press <Esc>, and confirm your changes.
NOTE: The network address you specify here must be different than the IPX internal network number (the computer's IPX address) or the LAN protocol (the network board's IPX address). The system treats the IPX address for PPPRNS as if it were a second network board or "virtual" LAN.
To view IPX numbers already assigned, press <Alt > <Esc> to return to the console prompt. Type config. The currently assigned IPX internal network address and the LAN protocol address will be listed. To return to the configuration program, press <Alt> <Esc> twice.
To complete the configuration process, press <Esc> and save your current settings to a file.
Press <Esc> to view a summary screen of the configuration just completed. Press < Enter> to return to the NetWare Connect Options menu.
Reset Idle Time Before Disconnect.
From the "NetWare Connect Options" menu, select Configure NetWare Connect, then Security, and then Set Global Parameters .
Set the Idle Time Before Disconnect to a positive value (5 or 10 minutes) , as preferred.
The connection will be disconnected when no data has been transmitted for the amount of time you specify. This prevents users from inadvertently leaving a modem connected when no data is being transferred.
Set remote passwords for users.
Unless you require passwords, your system is not secure; anyone could access the server even though they could not log in without knowing a network password. If you are using the Windows 95 Dial-Up adapter, remote client passwords are required.
From the "NetWare Connect Options" menu, Select Configure NetWare Connect, then Security, then Set User Remote Password.
Select the context (server and NDS tree) you need and press <Enter> to access a list of network users.
Select the user and enter a password (one to eight alphanumeric characters).
Verify the password by retyping it.
Repeat Steps 13b and 13c to specify passwords for other users.
Tell users their passwords.
(Optional) Automatically reload NetWare Connect.
NetWare Connect can be activated manually by typing NWCSTART at the server's console prompt or automatically by adding the same command to the server's AUTOEXEC.NCF file. When the server is rebooted, NetWare Connect is automatically activated as well.
To load NetWare Connect automatically, do the following.
At the server's console prompt type
LOAD INSTALL
Select NCF files options, and then Edit AUTOEXEC.NCF.
The AUTOEXEC.NCF file is displayed.
Add the following command to the file:
NWCSTART
Press <F10> to exit the file.
Confirm your changes and press <Esc> to exit Install.
Loading TCP/IP on the Server
If remote workstations will be dialing in to the NetWare Connect server, you will need to configure the server as an IP router. Complete the following steps.
Procedure
At the server's console prompt, type
LOAD INSTALL <Enter>
Select NCF files options.
Select Edit AUTOEXEC.NCF.
Add the following commands to the AUTOEXEC.NCF file in the order specified.
LOAD TCPIP FORWARD=YES
LOAD network board name FRAME=ETHERNET_II NAME= ipnet
BIND IP TO ipnet ADDR= ip_address MASK= mask
Replace the following variables with the information specific to your environment.
Replace With network board name The name of the network board in your server. For example, if you are using an NE2000 network board, replace the variable with NE2000. ipnet A configuration name of your choice. The name must be unique. Use the same name in both the load and bind lines. Ip_address The local IP address associated with the network bound to this interface. Each address on an IP internetwork must be unique and is usually provided by an Internet Service Provider. mask (optional) The subnet mask of the network bound to this interface. This setting must match the mask used by the other nodes on the network. If you do not specify the mask, IP assumes that the network is not divided into subnets.
Press <F10> and confirm your changes to the file. Press <Alt> <F10> or press <Esc> several times to exit Install and return to the server's console prompt.
Your NetWare Connect server setup is complete. However, you will still need to set up workstations so that they can access the services you've configured.
Selected NetWare Connect Tasks
Access paths for frequently used NetWare Connect tasks are supplied in Table 7-1. For complete information, see the NetWare Connect online documentation.
Context-specific <F1 > help is also available for the NetWare Connect Configuration (NWCCON) utility. To access help, highlight a screen field, press <Enter> , and then press <F1> .
Setting Up Workstations
How you configure laptops and workstations for use with the NetWare Connect server depends on which operating system is installed on the laptop or workstation that will connect to the NetWare Connect server and whether the workstation is (1) dialing in to the server as a remote node, (2) using the server to dial out to bulletin boards and the Internet, or (3) both.
Outlined below are the basic steps necessary to prepare Windows 95 and Windows 3.x workstations. Workstations running DOS and Macintosh* operating systems can also be set up to work with NetWare Connect. See the NetWare Connect online documentation for complete instructions.
You will need to install the NetWare Asynchronous Services InterfaceTM (NASITM ) and a dialer on each workstation or laptop needing to dial in to the server via a modem or needing to connect to bulletin boards or the Internet.
Setting Up Windows 95 Workstations
Follow the procedures in this section to set up Windows 95 workstations to take advantage of NetWare Connect services.
To complete the workstation setup, you must activate password authentication on the server, install a compatible client, install and configure dial-up software, and load and configure TCP/IP protocols.
Prerequisite
Make sure NetWare Client 32 for Windows 95 is already installed. See "Installing Client Workstations " in the Installation Guide (Small Business online documentation).
Activate Password Authentication
In addition to installing and configuring NetWare Connect on the server (see instructions above), some additional setup procedures need to be completed at the server in order to connect to PPPRNS from Windows 95. If you did not set remote client passwords for users when you configured the NetWare Connect server, do so now and then turn on the Password Authentication Protocol (PAP).
To set Remote Client Passwords for users, complete the following steps.
Procedure
Start NetWare Connect, if necessary, by entering the following at the server's console prompt:
NWCSTART
Access NWCCON by entering the following at the server's console prompt:
LOAD NWCCON
Select Configure NetWare Connect, then Security, and then Set User Remote Password.
Select the context you need and press <Enter> to access a list of network users.
Select the user and enter a password (one to eight alphanumeric characters).
Verify the password by retyping it.
Repeat Steps 5 and 6 to specify passwords for other users.
Tell users their passwords.
To activate the Password Authentication Protocol (PAP), complete the following steps.
Procedure
From the NWCCON Configuration Options menu, select Services.
Select PPPRNS.
Select Configure Security.
At the PPPRNS Security Configuration menu, make sure security is enabled and set PAP to Yes.
Install Win2NCS
This section describes how to use the Win2NCS version of the NetWare Asynchronous Services Interface (NASI) interface to dial out from the network to access bulletin boards, host computers, or other resources or to dial in and remotely control a dedicated network workstation using third-party communications applications.
Win2NCS allows you to "redirect" data to and from a Windows communication port. Instead of going through a modem connected to the workstation's COM port, data is routed through a NetWare Connect port controlled by the NASI Connection Service (NCS) on the server. To activate NCS services on the server, refer to "Configuring NetWare Connect"
You can use Win2NCS connections for both dialing out from the network and dialing in to the network to remotely control a dedicated network workstation.
- To dial out using Win2NCS, you need to install Win2NCS and a Windows communications application on the network workstation.
- To dial in using Win2NCS, you need to install a supported third-party application on both the network workstation and on the remote PC.
To install Win2NCS on Windows workstations and redirect calls from Windows to NetWare Connect Services (NCS) on the server, complete the following steps.
Procedure
From the Windows workstation, log in to the server as ADMIN or as a user who has temporarily been granted ADMIN rights.
Only user ADMIN has rights to the SYSTEM directory where Win2NCS setup files are stored. Use NEAT to temporarily grant users Full rights to the SYSTEM directory. Refer to "Granting Rights" on page xxx.
Select Start and then Run.
Use Browse to select (or type in) the following path, and then click OK.
F:\SYSTEM\WIN2NCS\SETUP.EXE
The Win2NCS (NASI Redirector) setup program appears.
![]()
Follow the screen prompts to set up the NASI redirector, making sure the following are set as indicated.
Installation options "Configuration file is created the installed directory" Destination directory C:\WIN2NCS
Review the modem assignments Win2NCS displays.
Modems assigned to NASI are indicated. Some local COM ports are reserved for printers and other devices needing COM ports.
Select OK to complete the Win2NCS setup.
An icon is added to the Win2NCS program group.
To configure Win2NCS, complete the following steps.
Procedure
Select the Win2NCS icon just created.
From the Options pull-down, select Set NASI Security and enter your username and password and then select OK.
From the Options pull-down, select Define Server Restrictions.
This option displays a list of servers so that you can select the one you want to connect to. If you define restrictions, you won't have to wait while the program tries to find other NetWare Connect servers.
From the Options pull-down, select Map Communications Ports. The program detects any NetWare Connect servers and displays any ports previously configured at the server in a window similar to the following:
![]()
Highlight the first port on the list (at the top of the screen) that is not grayed out.
Options that are not supported by the desktop operating system you are configuring will be grayed out. For example, Windows 3.x can share a local port with communications applications. This is not true with Windows 95.
Highlight ser/gen (server/general) name.
This specifies the server and the group name; you can choose any available port within the group.
Select one of the following:
- If you are configuring a dial-out port, select the server entry for ANY _PORT.
- If you are configuring a dial-in port, select a Dial in port group.
Select Map.
Repeat this procedure if you have other ports you want to map.
Select Save to save your mappings and exit.
The program returns to the "Current Assignments/Connections" window. You can close this window or leave it open. Either way, the connection is active whenever you are logged in to the server.
Set Up Modems
Use the following procedure to add and configure any modem, whether it is cabled to your workstation or laptop or cabled to the NetWare Connect server. This step is unnecessary for Windows 3.x workstations. Modems must be configured from within the modem application you are using to dial out.
To add or configure a modem, complete the following steps.
Procedure
Make sure the modem is turned on.
Select Start, then Settings, and then Control Panel.
Double-click the Modems icon.
If no modems have been previously defined, the Install New Modem wizard appears. Otherwise, the General tab appears. In this case, click Add.
![]()
Uncheck Don't detect...
The program attempts to detect any modems and displays the result.
Verify that the correct modem has been detected and take one of the following actions.
If correct Select Next. If incorrect Select Change to specify the correct manufacturer and model. If no modem is detected Follow the screen prompts to specify the modem manufacturer and model. NOTE: If you are selecting a modem to dial in to an Internet Service Provider (ISP), select the type specified by your ISP, in most cases, Standard Modem Type. Select the speed that matches the speed of the modem you are using.
Select Finish to return to the Modem Properties window.
At the General tab, select Dialing Properties and enter the telephone numbers indicated.
Select OK and then Close.
Install the Dial-Up Software
To install and configure Windows Dial-Up software, complete the following steps.
Procedure
From the Control Panel, double-click Add/Remove Programs.
Click the Setup tab.
Double-click the Communications group (or click on Properties).
Check the box for Dial-Up Networking; then click OK.
Click Apply and insert the Windows 95 media as requested.
Follow the screen prompts to install the Dial-Up software.
Click OK to exit.
To configure the dial-up software, complete the following steps.
Procedure
Double-click on My Computer, and then click Dial-Up Networking.
Double-click Make New Connection.
Follow the steps on the screen to create the icon.
Right-click on the new icon and select Properties.
Click Server Type.
Set the Type of Dial-Up Server to PPP: Windows 95, Windows NT* 3.5, or Internet.
Uncheck NetBEUI and any other protocols that are not needed.
If the server has not yet been configured to supply IP addresses, click on TCP/IP Settings to configure TCP/IP protocol parameters.
Click OK twice to exit.
Configure TCP/IP Support
To configure the workstation for TCP/IP support, complete the following steps.
Procedure
Select Start, then Settings, and then Control Panel.
Double-click Network to display the Configuration Tab.
If a TCP/IP protocol for the Novell client you are using
- Is listed, skip to Step 6.
- Is not listed, select Add and continue with Step 4.
Highlight Protocol and select Add.
Select Microsoft from the "Manufacturer's" list and TCP/IP from the Network Protocols" list, and then select OK.
You are returned to the Configuration tab.
Highlight the TCP/IP protocol just added and select Properties.
Enter your IP address and other site-specific information as applicable.
Select OK to save your changes and return to the Network tab.
Review the Configuration
To verify that all Windows 95 components have been installed, complete the following steps.
Procedure
At the Network Components tab, verify that all necessary components have been installed.
For an IPX connection
- Novell NetWare Client 32TM for Windows 95
- Dial-Up Adapter
- IPX 32-bit Protocol for Novell NetWare Client 32
- IPX/SPXTM -compatible protocol
For an IP connection
- Novell NetWare Client 32 for Windows 95
- Dial-Up Adapter
- TCP-IP
Dial in and connect to the NetWare Connect server or your ISP by double-clicking on the Dial-up networking icon.
Repeat the procedures above to create additional icons and configurations for different situations (one for dialing out to the Internet, one for dialing in to the NetWare Connect server, etc.).
Setting Up Windows 3.x Workstations
If users will be dialing in to the NetWare Connect server's PPPRNS service from a remote node (PC or laptop) running Windows 3.x, you will need to install and configure Novell's DOS/WIN (VLMTM ) client for Windows on the remote workstation and install and configure a dialer.
IMPORTANT: These procedures are only needed if users are dialing in to the NetWare Connect server from a remote workstation or laptop. If users are dialing out to bulletin boards or services provided by an Internet Service Provider, dial-out functionality is available using
Adding the ability to dial in to the NetWare Connect server from a Windows 3.x workstation includes several steps:
- Setting remote client passwords on the server. See "Activate Password Authentication"
- Installing the NetWare 16-bit DOS/WIN Virtual Loadable ModuleTM (VLM) client
- Installing the NetWare Connect 2.0 Remote client (includes a Windows 3.x dialer)
- Starting and configuring the dialer
- Setting up at least one phone book entry
- Installing Win2NCS (if users will be dialing out to bulletin boards or to services provided by an Internet Service Provider)
Install the NetWare DOS/WIN (VLM) Client
Windows 3.x remote workstations that will dial in to a NetWare Connect server must be running the NetWare DOS/Windows Virtual Loadable Module (VLM) Client. This client is a 16-bit client.
IMPORTANT: Even if the client will not connect to the network, you still need to install the VLM client. The remote client does not need a network board if it will never be cabled to the network. However, the Installation program will not proceed unless you provide needed parameters. In this situation, complete the install as if the network board is inserted into the computer. Keep the default board settings for an NE2000 board.
To install the client, refer to "Install NetWare DOS/Windows Virtual Loadable Module (VLM) Client" in Chapter 5 of the Installation Guide for installation instructions.
Install and Configure the NetWare Connect 2.0 Remote Client
To dial in to the NetWare Connect server (PPPRNS service) from a remote workstation, you need to install the NetWare Connect 2.0 Remote Client on the remote workstation. This client includes the Windows Dialer. The Windows Dialer supports the IP and IPX network protocols and the PPP and SLIP transport protocols.
When you use the Windows Dialer, you establish a remote node connection. Your remote workstation functions as if it were an actual node on the network. Because all data is transferred back and forth over the remote link, we recommend that you run your applications from the remote PC or laptop rather than the network.
IMPORTANT: You must install the NetWare DOS/Windows VLM Client before installing the NetWare Connect Remote client, even if the client will never be physically cabled to the network. If you have not already installed this client on your machine, do so before continuing. See "Install NetWare DOS/Windows Virtual Loadable Module (VLM) Client" in Chapter 5 of the Installation Guide for installation instructions.
If you re-install the VLM client at some future date, you will also need to reinstall the NetWare Connect Remote client.
To install the NetWare Connect 2.0 Remote Client from a CD-ROM drive or from diskettes complete the following steps.
Procedure
(Conditional) If your workstation does not have a CD-ROM drive, complete the following steps to create installation diskettes.
Log in to a Small Business server from a workstation connected to the network.
Change to the following directory:
F:\NWC20
Change to the DISK1 directory.
Insert a formatted floppy diskette into drive A:
Copy the DISK1 directory to drive A:, by entering the following command:
XCOPY /s *.* A: <Enter>
Remove the diskette and label it DISK1.
Change to the DISK2 directory by entering the following command:
CD..\ DISK2 <Enter>
Repeat Steps 1d through 1g to copy the files in Disks 2 through 4 to floppy diskettes.
Insert the NetWare Connect CD-ROM or Disk 1 of the Dialer diskettes created in Step 1 into the appropriate CD-ROM or diskette drive.
Start Windows, choose File, and then Run.
At the Run menu, click the Browse button.
Use Browse to locate the drive in which you inserted the remote client installation media.
For example, if the CD-ROM drive is D:, browse for the following path:
D: NWC20\DISK1\SETUP.EXE
If the diskette drive is A:, browse for the following path:
A: \INSTALL.EXE
From the File Name list, select SETUP.EXE.
Click OK.
The setup program initializes and displays the main screen.
Click Continue.
A menu similar to the following appears:
![]()
Set the destination path (target directory) to C:\NET.
Enter the path to the NetWare client directory (C:\NWCLIENT unless you changed the default when you installed the client). See "Install the NetWare DOS/WIN (VLM) Client"
Indicate which serial (COM) port you will be using to dial in to the network from the remote workstation.
You can select any of the ports listed in Table 7-2. Table 7-2 also lists the default interrupts and I/O addresses used by each port driver.
Table 7-2. Serial Ports
Port Interrupt I/O Address COM1 4 0x3F8 COM2 3 0x2F8 COM3 4 0x3E8 COM4 3 0x2F8 Custom 5 0x2F8 If you select Custom, list boxes appear that allow you to set the port address and interrupt used by the custom serial adapter.
You can change the interrupt and I/O address used by a Custom port, but you cannot change the settings used by COM1 through COM4.
Make sure that the port you select does not have settings that conflict with those used by other devices installed in the remote workstation (your mouse, for example).
(Conditional) If you select Custom, specify the interrupt and port address used by the custom serial adapter.
Refer to your custom serial port documentation for instructions on setting the interrupts and addresses used by the adapter. Make sure that the values you specify match the actual values specified in the serial adapter configurations and do not conflict with the interrupts and port addresses used by other devices installed in the PC.
If you are using a memory manager, pull down the Memory Manager list box and select your memory manager from the list. If yours is not listed, select None.
Click the Select Modules to Install box to indicate which modules to install. If disk space allows, we recommend installing all modules except the DOS remote client.
The SETUP program can install core NetWare workstation utilities (LOGIN, NLIST, SLIST, CAPTURE, MAP and CX, etc.) on the workstation. Running these utilities from the workstation rather than the network will significantly improve performance.
Click OK or press <Enter> to accept the selections you have made and to install the Remote client software.
The SETUP program copies the selected software to the target directory.
Reboot the workstation to activate the changes.
Install adds a NetWare Remote Client 2.0 program group to your Windows 3.x desktop.
Each time you start your computer, you are prompted to load the NetWare Connect remote client software. If your laptop or PC is not connected to the network and you need to dial in to the network during the session, enter Y. Otherwise, enter N.
Configure the Windows 3.x Dialer
The first time you run the Dialer, an initial configuration program steps you through the process of setting up your first connection. The Dialer creates an initial entry in the Phone Book based on this information. The Phone Book entry can be changed, as needed.
You can configure the Dialer to dial in to the network automatically, or you can enter the information you need each time you dial in.
To configure the Dialer, complete the following steps.
Procedure
Start Windows.
Select the NetWare Remote Client 2.0 program group.
Double-click the Remote Client Dialer icon.
(Conditional) If this is your first dial in, provide the information you are prompted for:
Phone line. Indicate whether the phone you will be using is tone or pulse.
COM port. Indicate which COM port the modem is attached to.
Modem type . Indicate the type of modem associated with the COM port (which modem you will be using to make the call).
Follow the guided configuration process to complete your setup.
Select Save & Exit.
(This button is not available until you provide the information the software needs to complete the call.)
The "Dialer" window is displayed.
Set up additional Phone Book entries as needed.
The Phone Book displays a summary of your entries and stores information the Dialer uses to connect you to the network, other dial-in services, or remote modems that you contact. If you make use of more than one such service, or dial in from more than one location, you can create a Phone Book entry for each location.
NOTE: Additional information about using and configuring the Phone book---how to place an operator assisted call, how to dial manually, how to set advanced options---can be found in "Using the Phone Book" in the NetWare Connect 2.0 User's Guide (NetWare Connect online documentation). Help also explains necessary procedures.
Dial In with the Windows Dialer
To dial in to the network with the Windows dialer, complete the following steps.
Procedure
Plug the telephone line into your workstation modem.
Start Windows, if necessary.
Select the NetWare Remote Client 2.0 program group.
Double-click the Remote Client Dialer icon.The "Phone Book" window appears.
Double-click the entry that you wish to dial (or highlight the entry and click Dial).The Windows Dialer will then dial the selected host.
6.When the connection has been successfully completed, you will be notified.
You can then exit the Dialer application or minimize it.
Log in to the NetWare Connect server in either of the following ways.
- Use NWUSER. This utility was added to a NetWare program group when you installed the DOS/WIN client. Use the utility to log in, connect to servers, map drives, and set up network printing; however, if you have a user login script that you want to run, you must log in from the command line (see below).
- Use the command line. Exit Windows, and from the C:\NWCLIENT directory type LOGIN servername/username. Using this procedure allows you to run your user login script, if any. Re-enter Windows after you have logged in.
Dial Out with the Windows Redirector (Win2NCS)
To dial out to a Bulletin Board Service or to services provided by an Internet Service Provider, you will need to install and configure Win2NCS on the Windows PC you are using to dial out. The steps for installing Win2NCS on a Windows 3.x workstation are identical to those for Windows 95 workstations. See "Install Win2NCS"
Prior Main Index Next This page is maintained by: Michael P. Harris
viking.delmar.edu
Last Updated: Sep 20mpharris@surf.delmar.edu
Copyright © 1998