Please give me help on how to configure RAS on Novell 5.0 Server. If you know any site which provides documentation on it let me know.

How to Install and Configure NETWARE CONNECT (Last modified: 14JUL1999) This document (10011354) is provided subject to the disclaimer at the end of this document. Printer friendly version of this document Forward this document to a colleague Provide feedback about this document to Novell -------------------------------------------------------------------------------- Goal How to Install and Configure NETWARE CONNECT 2.0 -------------------------------------------------------------------------------- Fact Formerly TID 1006848 Novell NetWare Connect 2.0 -------------------------------------------------------------------------------- Fix Preliminary Reading/Preparation: NetWare Connect 2.0 Installation and Basic Configuration Guide, NetWare Connect 2.0 Administration Guide, NetWare Connect 2.0 User's Guide. Hardware/Software Requirements: One NetWare Server running version 4.1 of NetWare with 24 MB of Memory. One Windows 3.1 or greater workstation. Appropriate communication adapters (ie . . . Digiboard, or standard com ports), Two modems or null modem cables. Other Requirements: Two Analog phone lines. Note: The installation of the server operating system is not a part of this guide and should be completed prior to using this document Overview: This document is designed to give a user a general understanding of the installation and default server configuration of NetWare Connect 2.0 through the following sections. The first section will explain the installation process. The second section will explain the configuration of the server. The third section will explain the DOS and Windows dialer for the RNS/PPP connection. The forth section will explain dialing out with NASI and using the WIN2NCS dialer. The fifth section will explain dialing out with the Macintosh and MAC2NCS. The sixth section will explain dialing in with ARAS. The seventh section contains exercises for using all of the items discussed. Disclaimer: All Products listed in this document are Registered Trademarks of their respective companies. The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Installing NetWare Connect 2.0 From Floppy Drive: From the file server (either NetWare 3.12 or 4.X) that you wish to install NetWare Connect 2.0 on, LOAD INSTALL. In a 3.12 environment choose Product Options and then press insert to install a new product. Give it the proper path to the floppy drive that contains the NetWare Connect 2.0 install diskettes. In a 4.X environment choose Product Options and then select INSTALL A PRODUCT NOT LISTED. Give it the proper path to the floppy drive that contains the NetWare Connect 2.0 install diskettes (ie . . . A:\ or B:\). From the SYS: volume of the NetWare Connect 2.0 server: From a workstation connected to a file server (preferably the one to which you want to install NetWare Connect 2.0 on). Create a directory at the root of the SYS: volume named CONNECT. Under this directory create sub-directories for each diskette, ie . . . DISK1, DISK2, etc . . . EXCEPT for the LICENSE diskette. Then copy from the diskette drive, or CD ROM drive where the NetWare Connect 2.0 install diskettes or CD are located ie . . . XCOPY A:\*.* F:\CONNECT\DISK1 /S/V/E. Once all diskettes have been copied, LOAD INSTALL on the file server. In a 3.12 environment choose Product Options and then press insert to install a new product. Give it the proper path to drive that contains the NetWare Connect 2.0 install diskettes, ie . . .. SYS:CONNECT\DISK1. In a 4.X environment choose PRODUCT OPTIONS and then select INSTALL A PRODUCT NOT LISTED. Give it the proper path to the drive that contains the NetWare Connect 2.0 install diskettes, ie . . . SYS:CONNECT\DISK1 From a CD mounted as a VOLUME: If the CD is mounted as a volume on the server that you plan to install connect on then LOAD INSTALL. In a 3.12 environment choose PRODUCT OPTIONS and then press insert to install a new product. Give it the proper path to drive that contains the NetWare Connect 2.0 install CD, ie . . . NWC20:NWC20\DISK1 In a 4.X environment choose PRODUCT OPTIONS and then select INSTALL A PRODUCT NOT LISTED. Give it the proper path to the drive that contains the NetWare Connect 2.0 install CD, ie . . . NWC20:NWC20\DISK1 If the CD is mounted as a volume on a server other than the one on which NetWare Connect 2.0 will be installed, the install must be done from the source server. You will have to have BTRIEVE loaded on both servers with the proper parameters (-u=1 -p=4096 -f-20 -h=60 -l=20 -c). BSPXCOM will also need to be loaded on both servers. The source server will also need BROUTER loaded. You will need to select "Install to remote servers" and select the destination server from the list. From a CD as a DOS device: From the file server that you wish to install NetWare Connect 2.0 on, LOAD INSTALL. In a 3.12 environment choose PRODUCT OPTIONS and then press insert to install a new product. Give it the proper path to the CD ROM drive that contains the NetWare Connect 2.0 install CD. In a 4.X environment choose PRODUCT OPTIONS and then select INSTALL A PRODUCT NOT LISTED. Give it the proper path to the CD ROM drive that contains the NetWare Connect 2.0 install CD ie . . . D:\NWC20\DISK1 Upgrading from NetWare Connect 1.0 to NetWare Connect 2.0 From the file server that has NetWare Connect 1.0 currently loaded on it, LOAD INSTALL. In a 3.12 environment choose PRODUCT OPTIONS and then press insert to install a new product. Give it the proper path to the CD ROM drive that contains the NetWare Connect 2.0 upgrade CD. In a 4.X environment choose PRODUCT OPTIONS and then select INSTALL A PRODUCT NOT LISTED. Give it the proper path to the CD ROM drive that contains the NetWare Connect 2.0 upgrade CD ie . . . D:\NWC20\DISK1 Install the upgrade for NetWare Connect. When you are prompted for the license diskette, insert the NetWare Connect 2.0 upgrade license. Important: YOU MUST HAVE NETWARE CONNECT 1.0 ALREADY INSTALLED AND CONFIGURED FOR THE UPGRADE PROCESS TO WORK. WE TAKE THE NUMBER OF CURRENTLY INSTALLED NETWARE CONNECT 1.0 LICENSES AND UPGRADE THEM TO NETWARE CONNECT 2.0 LICENSES. Configuring NetWare Connect 2.0 Upon initial installation of NetWare Connect 2.0 and the loading of NWCCON for the initial configuration, you will be prompted to configure your server. If you use this default configuration you will be set up properly. The following configuration information will enable you to re-configure your server back to the initial installation configuration. Load NWCCON From the main NWCCON menu, choose the option SETUP NETWARE CONNECT. Choose MANAGE LICENSES, and verify that you have all of the licenses installed that you should have. ESCAPE and then choose SELECT NETWARE PORTS and verify that all of your defined ports are listed. ESCAPE and then choose DEFINE NETWARE CONNECT PORT USAGE and then choose the option BOTH DIAL-IN AND DIAL-OUT, and verify that all of the defined ports are listed here. ESCAPE and then choose SELECT NETWARE CONNECT SERVICES and verify that you have at least one service selected. The options SET DIRECTORY CONTEXT and SET SERVER INFORMATION are for information only and you may set them to what ever you wish. They do not need to be set to anything. ESCAPE and then choose DEFINE AUDIT TRAIL. The defaults are as follows: Enable Audit Trail is set to yes, Archive Hour is set at 3:00 am, Archive Interval is set to one (1) days, and the Archive Files Retained is set to seven (7). Unless you are running the X.25 protocol and connectivity, you should not have to make any changes to the option CONFIGURE AIOPAD PARAMETERS. ESCAPE back to the main menu of NWCCON. From the main menu of NWCCON, choose the option CONFIGURE NETWARE CONNECT. Choose the option PORTS. Verify that all of your port names are listed and that their status is available. Scroll down the port listing and verify that all of your ports have their proper modem type assigned and that ports without a physical modem are set to a modem type of none. ESCAPE and then choose PORT GROUPS. The ANY_PORT group should be the only group shown. Important: ADDING ADDITIONAL GROUPS TO THIS MENU MAY CAUSE PROBLEMS IN CONNECTING TO THE SERVER USING NETWARE CONNECT. ESCAPE and then choose SECURITY. From this menu choose RESTRICT PORTS BY USER. Verify that each port has the Authorized Users of (ANY USER). ESCAPE and then choose the option RESTRICT SERVICE BY USER. Verify that each loaded service has the Authorized Users of (ANY USER). ESCAPE and then choose the option RESTRICT SERVICE BY PORT. Verify that each loaded service has the Authorized Ports of (ANY PORT). ESCAPE and select the option SET GLOBAL PARAMETERS. The defaults for this screen are as follows: Default Maximum Connect Time is set to -1, Idle Time Before Disconnection is set to -1, Default Dialback Mode is set to No Dialback Allowed, Dialback Wait Time is set to 30 seconds, Dialback Busy Retry count is set to 3 times, Dialback Busy Retry Interval is set to 30 seconds, and Dialout Restrictions are set to and the list contains (Any Number). ESCAPE and then choose SET USER PARAMETERS. Select a user and verify that all of the defaults are as follows: Allow User To Change Remote Client Password is set to no, Disable Remote Client Password After Number Of Days is set to 30, Use Dialback Mode is set to Use Global Default Dialback Mode, and Use Global Dialout Restrictions is set to yes. ESCAPE and then choose SET USER REMOTE CLIENT PASSWORD. Select a user and enter the desired password for Remote Client Access. ESCAPE and then choose SET REMOTE CLIENT PASSWORD RESTRICTIONS. The defaults for this option are as follows: Lockout Password after Number of Failed Logins is set to -1, and Set Minimum Password Length is set to -1. ESCAPE and then choose SERVICES. You will then see a list of all of the services that you have loaded. For ARAS the default configuration is as follows: Set User Zone Restrictions is set to (Any Zone), Set Default Zone Restriction is set to (Any Zone), and Setup Options are: Forward Packet to AppleTalk with CRC Embedded is set to No, Support Apple Remote Access Client Version is set to 2.0 only, Prompt User for Remote Client Password (ver. 2.0) is set to no, and ARAS Greeting (ver. 2.0) is at and the entry screen is blank. ESCAPE and choose NCS. For NCS the default configuration is as follows: General Name List is set to and the list only contains ANY_PORT, the General Name for Shared Dial-in Ports is set to DIALIN, the Modem Independent Group should have no entry, the Alias Server Name is set to the first eight (8) characters of the NetWare Connect Server Name, Enable NCS Dial-in Security is set to yes, Enable NASI Security is set to yes, Command Interrupter Prompt is set to NASI, and the Break Duration is set to 0.550 seconds. ESCAPE and choose PPPRNS. Choose the option CONFIGURE SECURITY. The defaults for this are as follows: Enable Security is set to Enable, NetWare Connect Authentication Protocol is set to yes, Password Authentication Protocol is set to no, Challenge Handshake Authentication Protocol is set to no. ESCAPE and choose SET IPX PARAMETERS. Choose a user and the defaults should be as follows: Specify IPX address is set to no, Home Server is and the list is blank. ESCAPE and choose SET IP PARAMETERS. Choose a user and the defaults should be as follows: Set Domain Information is set to no, and Set Boot Parameters is set to no. This is for BOOTP only. You must have the BOOTP.NLM loaded to use this option. This completes the default configuration for NetWare Connect. This is the Novell recommend configuration for NetWare Connect 2.0. Installing and Configuring the PPPRNS DOS and Windows Dialer's Note: The VLM client files must be installed prior to installing the DOS or Windows dialers. If you have not installed the VLM client on your machine, please do so before continuing. If at anytime you reinstall the VLM client on your machine, you will need to reinstall the dialers. Installing the DOS Dialer from a floppy drive To install the DOS Dialer from the floppy drive you will need to have the first three diskettes of the NetWare Connect Installation. They are labeled as follows: NetWare Connect 2 - Client and Server Install Programs - Disk 1 of 11 NetWare Connect 2 - Remote Client Files - Disk 2 of 11 NetWare Connect 2 - Win2NCS & Modem Script Tools - Disk 3 of 11 From the DOS prompt run A:INSTALL (or B:INSTALL). Specify the path to install the DOS Dial software. The default is C:\NET\BIN. If MS Windows is installed on the system, you will be prompted for the directory where windows is installed. You will then be prompted to give the path to the NetWare Client directory. This should be the directory where you installed the NetWare 4.x client files. Note: If you have not installed the NetWare 4.x client on this machine do not continue this installation until you have done so. You will then be asked to choose the serial port that you will be using and also the appropriate memory manager. This enables the DOS Dial software to know which port it should configure for and which memory manager to use to load the appropriate network drivers into memory. You then need to select the items to install: DOS Remote Client? NO Windows Remote Client? NO Install TCPIP? NO Install IPX? NO NetWare Utilities (Login, NLIST, MAP, etc) ? NO You must install either the DOS or Windows Remote Client, and TCPIP or IPX. Then highlight the last option and press . This will install the selected items. After the installation has been completed you must reboot your machine for the changes to take effect. Installing the DOS Dialer from a network volume To install the DOS Dialer from a network volume, you must be logged in to the system and have access to the SYS:SYSTEM directory. Change to the following path: SYS:SYSTEM\REMOTE and run the install program. Specify the path to install the DOS Dial software. The default is C:\NET\BIN. If MS Windows is installed on the system, you will be prompted for the directory where windows is installed. You will then be prompted to give the path to the NetWare Client directory. This should be the directory where you installed the NetWare 4.x client files. Note: If you have not installed the NetWare 4.x client on this machine do not continue this installation until you have done so. You will then be asked to choose the serial port that you will be using and also the appropriate memory manager. This enables the DOS Dial software to know which port it should configure for and which memory manager to use to load the appropriate network drivers into memory. You then need to select the items to install: DOS Remote Client? NO Windows Remote Client? NO Install TCPIP? NO Install IPX? NO NetWare Utilities (Login, NLIST, MAP, etc) ? NO You must install either the DOS or Windows Remote Client, and TCPIP or IPX. Then highlight the last option and press . This will install the selected items. After the installation has been completed you must reboot your machine for the changes to take effect. Configuring the DOS Dialer Upon loading the DOSDIAL utility the first time you will get the message: DOSDIAL(1650) The DOS Dial program has determined that you need to set the initial configuration. You may continue, or press for more details. Press to continue. Choose YES to proceed with the configuration. Choose the COM port and the modem that is attached to that port. You should not have to make any changes to the advanced options, unless you need to add additional modem parameters to initialize the ports. You will then be asked to create the first entry into the DOSDIAL phone book. Once this is completed you will be able make the dial. Dialing with the DOS Dialer Note: Verify that you have the following drivers loaded and in this order: LSL, NESL, NCOMX, NWREMOTE, IPXODI, and VLM. If these are not loaded reboot your machine and say YES to load remote client software. If you have only one entry in the phone book when you select Dial a Host it will dial the only one that you have. If you have multiple entries in the phone book you will be presented with a list that contains all available entries. Choose the entry that you wish to dial and press and the DOSDIAL program will dial that entry. After DOSDIAL has completed the connection you will see the following message: Operation Successful. Press to continue. After pressing exit the DOSDIAL program by pressing . From the C:\NWCLIENT directory you may then login to the server - LOGIN SERVERNAME/username (with the full context of the user in a 4.x environment). You now have access to the server. Note: DOS Dial also had DOS command line parameters that can be used to establish connections from a batch file or command line. To see a full listing of the options from the DOS prompt type DOSDIAL /? Troubleshooting information for the DOS Dialer If you are on a 3.12 server and are not able to get logged in or attached to the server or are not able to see the F: prompt then check the following: In the C:\NWCLIENT\NET.CFG on the NETWARE PROTOCOL LINE remove the NDS entry. Also verify that you do not have any home servers configured under PPPRNS configuration parameters on the server. Installing the Windows Dialer from a floppy drive To install the Windows Dialer from the floppy drive you will need to have the first three diskettes of the NetWare Connect Installation. They are labeled as follows: NetWare Connect 2 - Client and Server Install Programs - Disk 1 of 11 NetWare Connect 2 - Remote Client Files - Disk 2 of 11 NetWare Connect 2 - Win2NCS & Modem Script Tools - Disk 3 of 11 From Windows choose FILE, RUN and the path is A:SETUP (or B:SETUP). Specify the path to install the Windows Dialer software. The default is C:\NET\BIN. Because MS Windows is installed on the system, you will need to enter the directory where windows is installed. You will then be prompted to give the path to the NetWare Client directory. This should be the directory where you installed the NetWare 4.x client files to. Note: If you have not installed the NetWare 4.x client on this machine do not continue this installation until you have done so. You will then be asked to choose the serial port that you will be using and also the appropriate memory manager. This enables the Windows Dialer software to know which port it should configure for and which memory manager to use to load the appropriate network drivers into memory. You then need to select the items to install: DOS Remote Client? NO Windows Remote Client? NO Install TCPIP? NO Install IPX? NO NetWare Utilities (Login, NLIST, MAP, etc) ? NO You must install either the DOS or Windows Remote Client, and TCPIP or IPX. Click on OK or press enter to install. This will install the selected items. After the installation has been completed you must reboot your machine for the changes to take effect. Installing the Windows Dialer from a network volume To install the Windows Dialer from a network volume, you must be logged in to the system and have access to the SYS:SYSTEM directory. From the Program Manager choose File, Run F:SYSTEM\REMOTE\SETUP.exe Specify the path to install the Windows Dialer software. The default is C:\NET\BIN. Since MS Windows is installed on the system, you must enter the directory where Windows is installed. You will then be prompted to give the path to the NetWare Client directory. This should be the directory where you installed the NetWare 4.x client files to. Note: If you have not installed the NetWare 4.x client on this machine do not continue this installation until you have done so. You will then be asked to choose the serial port that you will be using and also the appropriate memory manager. This enables the Windows Dialer software to know which port it should configure for and which memory manager to use to load the appropriate network drivers into memory. You then need to select the items to install: DOS Remote Client? NO Windows Remote Client? NO Install TCPIP? NO Install IPX? NO NetWare Utilities (Login, NLIST, MAP, etc) ? NO You must install either the DOS or Windows Remote Client, and TCPIP or IPX. Click on OK or press enter to install. This will install the selected items. After the installation has been completed you must reboot your machine for the changes to take effect. Configuring the Windows Dialer When you run the Windows Dialer for the first time you will be prompted to configure for a phone book entry. The first option refers to the type of phone line that you will be using, tone or pulse. The next page will allow you to select the COM port that you will be using and the modem type that is associated with that port. You will then be able to set the default phone book entry. When everything has been entered and configured properly the Save & exit button will no longer be grayed out and is an available option to select. Dialing with the Windows Dialer To dial with the Windows dialer you may either double click on the entry that you wish to dial or highlight the entry and then click on the dial icon. The Windows Dialer will then dial the selected host. When the connection has been successfully completed you will see the following message: The connection has been successfully established! Select the next action to perform: No Action, Minimize, Exit. You may select any of the options. You may then go to a MS DOS prompt from the MAIN group and login to your server from the C:\NWCLIENT directory (LOGIN SERVERNAME/username). You may also use NWUSER to login to your servers and map your drives. You can also exit Windows at this time without breaking the connection and login to the desired servers. Using this option your login script will be processed. You may then proceed to enter Windows again. Troubleshooting information for the Windows Dialer If you are on a 3.12 server and are not able to get logged in or attached to the server or are not able to see the F: prompt then check the following: In the C:\NWCLIENT\NET.CFG on the NETWARE PROTOCOL LINE remove the NDS entry. Also verify that you do not have any home servers configured under PPPRNS configuration parameters on the server. Installing and Configuring the DOS NASI TSR and the Windows Redirector (Win2NCS) Installing and using the DOS NASI TSR The DOS NASI TSR files are found in the SYS:SYSTEM\NCS directory. You can copy the contents of this directory to either a local workstation or to the public directory on the file server. This will allow access to the program. To load NASI in a 3.12 environment, verify that you are logged in to a file server that has access to the NASI TSR, and that the username and password that you are using is valid in the bindery of the server with NetWare Connect loaded on it. To load NASI in a 4.x environment, verify that you are logged in as a user that has rights to the connect object and that you are in the context where that user is found. From the DOS prompt type NASI. You will then be prompted for a password. This is, in the 3.12 environment, the bindery password of the user as found on the server running NetWare Connect, and in the 4.x environment, the NDS password of the user that you are logged in as. Note: NASI has command line parameters that may be used to load the TSR. To get a list of these parameters, type NASI /? at the DOS prompt. To verify that the NASI service is loaded and configured properly, load NAMIBIA at the DOS prompt. You may then List Available NCS Servers and verify that your NetWare Connect server is listed. You may then List Available NCS Ports and verify that you see all of your ports listed here. If you see available NCS ports then you are configured for any NASI supported application to use the NetWare Connect ports. Installing Win2NCS from a floppy drive To install Win2NCS from a floppy drive you will need the following NetWare Connect 2.0 installation diskette labeled: NetWare Connect 2 - Program Files - Disk 4 of 11 From the Windows Program Manager choose File, Run and then the path to the floppy drive where this is located, ie . . . (A:SETUP.EXE or B:SETUP.EXE). Win2NCS will now be installed. Once the installation is completed Win2NCS is ready to use. Installing Win2NCS from a network volume To install Win2NCS from a network volume you will need to have access to the SYS:SYSTEM\WIN2NCS directory. From the Windows Program Manager choose File, Run and run from the following path: F:\SYSTEM\WIN2NCS\SETUP.exe Win2NCS will now be installed. Once the installation is completed Win2NCS is ready to use. Configuring Win2NCS When Win2NCS is first executed, you will be prompted to enter your NASI Security. Once security has been established, then choose OPTIONS, and GLOBAL MAPPING OPTIONS. Under GLOBAL MAPPING OPTIONS set HARDWARE FLOW CONTROL TO ALWAYS and if you are in a 4.x environment set PROMPT USER FOR 4.X CONTEXT to ENABLE. Now you will need to re-set your NASI Security. If you have the context line, place the context of the user in this line with no leading period, ie . . . (nwconnect.services.novell) with out the parenthesis. You may now MAP COMMUNICATIONS PORTS. If you are able to see your server, and your port groups and your ports, then you are configured correctly. Map your server ports to a local COM port. Dialing with Win2NCS Choose an application that supports the standard Windows API calls. Using this application configure to use a modem off of a COM port, ie . . . COM1. When the application is configured, then you make your dial and the call will be redirected to the NASI server ports. Troubleshooting Win2NCS If you are not able to see ports under Win2NCS there is most often a security issue. Verify that you have the proper context entered and that you have the proper rights to use the Connect Object. In a 3.12 environment, verify that the username is valid in the bindery of the server running NetWare Connect. Installing and configuring MAC2NCS Installing MAC2NCS on a Macintosh Insert NetWare Connect MAC Client diskette into the disk drive of the Macintosh workstation. Double click on the disk icon that shows up on the monitor. Then double click on the Installer icon. A message will come up which says Welcome to Mac2NCS Installer !. Click on Continue. From here choose what you wish to install. The best option is to choose Easy Install and then click on Continue. Once installed then click on Restart. The workstation will then reboot. Configuring MAC2NCS Pull down the Apple menu and select Chooser. Find the Mac2NCS icon within the Chooser and click on it to configure Mac2NCS. Select Modem Port and set Redirect to LAN to On, then click on Setup. This will ask for a username and password. Note: If you are in a 4.x environment then the username field will need to have the context with the username. If the network is setup correctly, a selection of servers will appear in the bottom left hand corner. Click on the NetWare Connect server. Put in the username with no leading period. Then put in the password. Do not press enter at this point!! Click on Continue. This will bring up NetWare Connect: Port Selection. At this point a Server, General Name and Specific Name should show up. Select a server, a group for dialing out and a dialout port and select OK. Select on OK at the next screen. MAC2NCS is installed and ready to use. Dialing out with MAC2NCS Using a Macintosh dialout application set up to use a modem with the modem type that is on the port redirected through MAC2NCS, a dialout connection can be made. Troubleshooting MAC2NCS If you are not able to see ports or services, then there may be a problem with the password or username. Dialing in to the NetWare Connect server with ARAS Dialing in with ARAS On your Macintosh you will need to have a modem and indicate your modem setup in the remote access setup. Verify that the username is authorized on the network. Specify the phone number. Select the Apple Remote Access icon and enter your username from the NetWare Server. Note: If you are in a 4.x environment, you must enter the user name with the context of the user. This is type less naming and with out the leading period. You will then be asked for a password. Enter your NetWare Connect password. Note: The password that is entered here is the NetWare Connect Remote Client Password. This is set in the configuration of Security under the NetWare Connect configuration. Enter the telephone number that you wish to call. If you wish to have periodic reminders of your connection, select OPTIONS and set one of the CONNECT REMINDER OPTIONS. Select OK and then CONNECT. ARAS will initialize the modem and establish the connection. Logging in to the network with ARAS Once the connection has been established, you will need to login to have access to the Macintosh resources on the network. In a 4.x environment, open the Macintosh Control Panels folder and select the MACIPX icon. Then select the AppleTalk icon. You should then see a list of zones and IPX gateways. Select the IPX gateway that has a connection to the servers that you wish to access. Exit MACIPX and close the Control Panels folder. (If you are in a 3.12 environment - start here) Next select the AppleShare icon from the Chooser. Select the AppleTalk Zone that your NetWare server belongs to. Select the NetWare server. Login by specifying your username and password. You are then prompted to enter an access method. In a 4.x environment with NDS select Encrypted NetWare Authentication. If you are in a 3.12 environment select Apple Standard VAMS. You should now be connected to your network. Exercises 1- Install NetWare 4.10 and install NetWare Connect 2.0 on that server. 2- Have someone re-configure the NetWare Connect server and then re-set it to defaults. 3- Install, configure and make a DOS and Windows PPPRNS Connection. 4- Install Win2NCS and dialout to a Bulletin Board Service. 5- Use the DOS NASI TSR and make a connection to a Bulletin Board Service. 6- Install and make a CompuServe Connection with MAC2NCS. 7- DIALIN to a NetWare for Mac environment with ARAS. -------------------------------------------------------------------------------- Please select if this document solved your problem. -------------------------------------------------------------------------------- Document Title: How to Install and Configure NETWARE CONNECT Document ID: 10011354