Copyright: Copyright © 1998 Novell, Inc. All Rights Reserved.


1Moab
Authorable button

Banner Base

Base

Bullet (1st Lvl)

Bullet (2nd Lvl)

Bullet Text (1st Lvl)

Bullet Text (2nd Lvl)

Button Bar

Code

Contents Icon

Field Heading (1st Lvl)

Field Heading (2nd Lvl)

Field Text (1st Lvl)

Field Text (2nd Lvl)

Field Text  2 (1st Lvl)

Field Text 2 (2nd Lvl)

Heading (1st Lvl)

Heading (2nd Lvl)

Link (non-scroll)

List (1st Lvl)

List (2nd Lvl)

List Head (1st Lvl)

List Head (2nd Lvl)

List1

List2

List3

Number

Number Alpha

Number Alpha Text

Number Text

Related Topic

Text (1st Lvl)

Topic Title

Trademark


About Dial-Up Connections

In order to dial in to a network via a modem, users double-click a Dial-Up Connection icon in their Windows** 95** Dial-Up Networking folder. These Dial-Up Connections can be defined as follows:

Locally by users.

Centrally by network supervisors. Centrally defined Dial-Up Connections are NDS* objects and are known as Corporate Dial-Up Connections.

Locally by supervisors and then copied to a server as a Corporate Dial-Up Connection.

Note: Corporate Dial-Up Connections can also be configured for Windows** 3.x and then used as Phone Book Dial-in services by remote Windows 3.x users.

* Novell trademark. ** Third party trademark. For more information, see Trademarks.


About Novell IntranetWare Remote Access Dialer
About Novell  Remote Access Dialer

Novell* Remote Access Dialer software provides secure business communication services for dial-up access to the following:

NetWare* networks

The LAN from home, remote offices, customers’ locations, hotel rooms -- from virtually anywhere in the world

The Internet

CompuServe**

Secure corporate networks (LAN to LAN or LAN to WAN)

 Related Topics

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Administration Support

Although the Remote Access Dialer runs on any client workstation with Windows** 95** Dial-Up Networking installed, the snap-in enhancements to NetWare* Administrator which provide the Corporate Dial-Up Connection features require an NDS* network.

So, for example, Corporate Dial-Up Connections are not available with a NetWare 3*-only network.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


An invalid name was entered

Explanation

You tried to create a Dial-Up Connection object but entered an invalid name. Names should be valid NDS* object names and Windows** 95** Dial-Up Connection names.

Action

Change the Dial-Up Connection name to one that meets the above criteria.


Being a Remote Access Dialer Supervisor

A network supervisor has different responsibilities at different times. These include some or all of the following:

Installation planning

Customizing the client installation program before it's installed

Installing components on one or more client workstations

Post installation functions concerning creating and/or updating:

NDS* Schema

Login scripts

Corporate Dial-Up Connections

Troubleshooting and providing user support

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Benefits of Corporate Dial-Up Connections

Novell* Remote Access Dialer allows you to create and administer Corporate Dial-Up Connections centrally on a server.

Users can copy these Corporate Dial-Up Connections into their Windows** 95** Dial-Up Networking folder (using the Update Dial-Up Connections dialog) and use them as they would any Dial-Up Connection they had defined locally themselves. When users want to dial in to a network, they simply select the appropriate corporate connection. They do not need to create individual Dial-Up Connections or know any details about the remote access server they are dialing in to.

If the configuration of a remote access server changes, you simply modify any associated Corporate Dial-Up Connections and then ask your users to update their connections again. The users do not need to know any details about the change.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Can't initialize library ADMAPIxx

Explanation

The ADMAPIxx library has not initialized. This could be due to the absence of Windows** 95** Dial-Up Networking or an incorrect installation.

Action

If Windows 95 Dial-Up Networking is not installed, install it and then reinstall the NWADMN95 snap-ins.

If Windows 95 Dial-Up Networking is already installed, then reinstall the NWADMN95 snap-ins.


Changing Dialing Settings for a Dial-Up Connection

Refer to your Windows** 95** documentation for information about changing the dialing settings.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Changing Properties for a Dial-Up Connection

Refer to your Windows** 95** documentation for information about changing dial-up connection properties.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Client Workstation Prerequisites

Remote Access Dialer for Windows** 95** uses the Dial-Up Networking features provided by Windows 95. For example, Windows 95 automatically finds the modem parameters of a connection from the system.

Important:  Windows 95 Dial-Up Networking must be installed and active on a client workstation before the user can dial in to a server.

Note:  If you intend to use scripts, the Windows 95 Dial-Up Scripting tool must also be installed.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Contents_1
Novell Remote Access Dialer Administrator Help Contents

Overview

About Novell Remote Access Dialer

Components Overview

Server Prerequisites

Client Workstation Prerequisites

About Dial-Up Connections

Administration Support

Post-Installation Issues

Starting NWADMN95 for the First Time

Migrating NetWare Mobile for Windows 3.x Phone Book Entries

Administering Corporate Dial-Up Connections

How Corporate Dial-Up Connections are Used

Creating Corporate Dial-Up Connections

Using Dial-Up Scripting

Security Considerations

Managing Corporate Dial-Up Connections

User Changes to Corporate Dial-Up Connections

Troubleshooting

Dialing - Basic Checks

Purging the NDS schema

Reference

Trademarks


Corporate Dial-Up Connection

A Dial-Up Connection is a collection of information that enables a user to dial in to a remote network. It contains information such as the telephone number, area code, and modem details of the dial-up point on the network that they are dialing in to.

Corporate Dial-Up Connections are created and maintained centrally by the network supervisor. Users access them by running the Update Corporate Dial-Up Connections dialog. This copies the Corporate Dial-Up Connections into their local Dial-Up Networking folders.


Creating Corporate Dial-Up Connections

Note: To create a Dial-Up Connection object you must have the Create right to the container object that you want to create it in. The rules for creating a Dial-Up Connection (such as naming conventions) are the same as for any other type of leaf object.

To create a Corporate Dial-Up Connection:

1.	Double-click the NetWare* Administrator icon.

2.	Select the container object that you want to contain the new Dial-Up Connection, using the Browser if required.

3.	Click Object > Create.

4.	In the New Object dialog box, click Dial-Up Connection > OK.

The Create Dial-Up Connection dialog is displayed.

5.	Complete the settings you require for the new Dial-Up Connection.

Click the Help buttons within the dialog for help on any of the settings.

All Remote Access Dialer users with the Browse object right and the Read property right to the container that you created the Dial-Up Connection in can now copy it to their Windows** 95** Dial-Up Networking folder by using Update Dial-Up Connections.

Hint:  By creating a Dial-Up Connection on your local computer, you can try out the connection before you copy it to the server for access by other users.

 Related Topics

* Novell trademark. ** Third party trademark. For more information, see Trademarks.


Dial-Up Connection

A collection of information that enables you to dial in to a remote network. It contains information such as the telephone number, area code, and modem details of the network server you are dialing in to.

Double-clicking a Dial-Up Connection in your Windows** 95** Dial-Up Networking folder initiates the connection.

Corporate Dial-Up Connections are created and maintained centrally by the network supervisor. Users access them by running the Update Corporate Dial-Up Connections dialog. This copies the Corporate Dial-Up Connections into their local Dial-Up Networking folders.


Dialing - basic checks
Dialing -- Basic Checks

If you experience problems when dialing in, make the following basic checks:

Check the hardware. Make sure you are using the correct phone jack.

Check the cables. Make sure you are using the correct modem cable.

Check the software settings (for example, the modem settings).

Check for a signal. Make sure the speaker for the modem is turned up and listen for a dial tone or the modem's dial tones.

Try changing the baud rate to a lower setting. Consult the documentation that came with the modem.

Try the Windows** 95** Phone Dialer. If necessary, consult the Windows 95 online help or documentation.

If you get an error message when dialing, refer to the online help.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Dialing a Connection

To dial in to a computer or network, you need a Dial-Up Connection configured for the network server you are dialing in to. This can be either one you have created yourself or a Corporate Dial-Up Connection that your network supervisor has created.

Make sure you have your modem and software settings correctly set up before dialing. Refer to Preparing to Dial in to the Network.

To dial in:

1.	 Open your Windows** 95** Dial-Up Networking folder.

2.	 Do one of the following to initiate the dialing connection:

Double-click the appropriate Dial-Up Connection icon.

Select the appropriate Dial-Up Connection icon and then click File > Connect.

The Connect To dialog box is displayed. For help on an item in this dialog box, click ? and then click the item.

 Related Topics

* Novell trademark. ** Third-party trademark. For more information, see Trademarks


Dialing a Connection Manually

Refer to your Windows** 95** documentation for information about dialing a connection manually

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Dll: There is a problem loading the library dll is the name of the module (usually ADMAPI32.dll) in which error occurred
Dll: There is a problem loading the library library. dll is the name of the module (usually ADMAPI32.DLL) in which the error occurred. library is the name of the problem library.

Explanation

The named module (usually ADMAPI32.DLL) cannot find a DLL. It expects the DLL to be in the same directory as itself (the default is \NOVELL\CLIENT32).

Action

Check that the named module and library are in the same directory. If they are not, then reinstall.


Dll: There is a problem with the library. The library may be corrupt or out of date
Dll: There is a problem with the library library. The library may be corrupt or out of date.

Explanation

The library might be corrupted or outdated.

Action

Check that the library is the current version, or reinstall.


How Corporate Dial-Up Connections are Used
Administering Corporate Dial-Up Connections

1.	Each dial-in point on the network is set up as a Dial-Up Connection object using NetWare* Administrator. For more information, see Creating a Corporate Dial-Up Connection.

2.	Users can then copy these Corporate Dial-Up Connections to their client workstations by running the Update Dial-Up Connections dialog. (Click Start > Programs > Novell >Dialup > Update Dial-Up Connections.)

For more information, see Updating Corporate Dial-Up Connections.

The Update Dial-Up Connections dialog searches for Corporate Dial-Up Connection objects and copies them into the user's Windows** 95** Dial-Up Networking folder. Each connection is displayed as a separate icon in the folder.

Users can use the copied Corporate Dial-Up Connections as they would a dial-up connection that they had defined themselves.

3.	Users dial in by double-clicking the appropriate dial-up connection icon in the Dial-Up Networking folder. For more information, see Dialing a Connection.

Note:  Corporate Dial-Up Connections can also be configured for Windows** 3x and then used as Phone Book dial-in services by remote Windows 3x users.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Introduction

About Novell Remote Access Dialer

Software Overview

Administration Support

Remote Access Dialer Components


Managing Corporate Dial-Up Connections

To change the properties of an existing Dial-Up Connection, you must have the Create right to its container object.

To delete a Dial-Up Connection, you must have the Delete right to the object itself or the container.

Note:  You cannot "undo" a deletion. To reinstate a deleted Dial-Up Connection, you must re-create it.

You can search for, move, and rename Dial-Up Connections in the same way as any other type of NDS* leaf object.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Migrating NetWare Mobile for Windows 3.x Phone Book Entries

Any NetWare* Mobile* for Windows** 3.x personal phone book entries on a client workstation are automatically converted to Dial-Up Connection icons in the user's Windows 95** Dial-Up Networking folder. They can be used in the same way as Dial-Up Connections created within the Remote Access Dialer.

The NetWare Connect* version on the server must be Windows 95 compatible.

Note:  NetWare Mobile 1 type phone book entries are automatically migrated to PPP server type entries.

* Novell trademark. ** Third party trademark. For more information, see Trademarks.


NetWare/IP Settings in Dial-Up Connections

To work with NetWare*/IP* program settings for a dial-up connection:

1.	Select the appropriate Dial-Up Connection and open the Windows** 95** Properties dialog.

2.	Select Server Type.

3.	Select PPP as the Type of Dial-Up Server.

4.	Click NetWare/IP to open the NetWare/IP Properties dialog box and specify the settings you require.

For help on a setting, click ? at the top of the dialog box, and then click the setting.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


No NDS trees can be found. This could be due to invalid logon, network failure or insufficient rights
No NDS trees can be found. This could be due to an invalid login, network failure or insufficient rights.

Explanation

No NDS* Directory trees could be found on the network.

Action

Check that you have a working network connection and that you are using the correct login username and password. If the problem persists, check with your network supervisor that you have sufficient Read and Write access rights to NDS.


Novell Client Remote Access Dialer System Messages


Overview of Dialing In

When you work at remote locations where a physical connection to the network is not possible, you can dial in to the network (via a server on the network) in order to access files and other network resources. To do this, a modem must be connected and configured on both your computer and the network server that you are dialing in to.

Dialing in is simplified by the use of Dial-Up Connections. A Dial-Up Connection contains all the necessary dialing information about the connection you want to dial, such as the remote server's telephone number and other dialing requirements. Dial-Up Connections are stored in your Windows** 95** Dial-Up Networking folder.

Corporate Dial-Up Connections

You do not have to create and configure your own Dial-Up Connections. To make it easier for you to dial in, your network supervisor can create Corporate Dial-Up Connections on the network. You can then copy these connections to your Dial-Up Networking folder and use them to dial in.

To copy Corporate Dial-Up Connections to your networking folder, you run the Update Dial-Up Connections dialog. You should run this dialog periodically in order to update your Dial-Up Networking folder with the latest Corporate Dial-Up Connection entries.

Using Dial-Up Scripts to Automate Dialing In

Often when you dial in, you have to provide information such as your username and password. You can create a dial-up script to provide this information automatically, so that you do not have to enter it each time you dial in. For more information, refer to "Automating a Dial-Up Connection" in the Windows 95 help.

 Related Topics

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Preparing to Dial In to a Network

Before dialing in to a network, you need to do the following:

Make sure you have the Windows** 95** Dial-Up Networking component installed on your workstation. (Refer to your Windows 95 documentation for more information.) If you use scripts when you dial, you must also have the Windows 95 Dial-Up Scripting Tool installed.

Install a modem and connect it to the telephone line.

Set up a Dial-Up Connection in your Dial-Up Networking folder for the remote network server that you want to dial in to (you can create your own Dial-Up Connections or use Corporate Dial-Up Connections created by your network supervisor).

 Related Topics

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Purging the NDS Schema

If you want to remove the Dial-Up Connection object class from the NDS* schema, run the NDSPUR32.EXE purge program.

NDSPUR32.EXE searches the current tree for existing Dial-Up Connections and deletes them. Then the Dial-Up Connection object class is removed.

In order to use NDSPUR32.EXE. you must have the Supervisor right to the entire tree. If you have the Supervisor right to only part of the tree, NDSPUR32.EXE removes objects at and below that level of the tree, but it is not able to remove the object class.

Note: NDSPUR32.EXE is in the Remote Access Dialer directory (C:\NOVELL\CLIENT32 by default).

If you are using Remote Access Dialer with more than one tree, do not forget to purge them all.

To run NDSPUR32.EXE:

1.	Open the directory which contains the Remote Access Dialer (C:\NOVELL\CLIENT32 by default).

2.	Double-click the NDSPUR32.EXE icon.

Note:  NDSPUR32.EXE can also be used to reset any administration dialogs that you have switched off (for example, the Dial-Up Networking Administration Schema Update dialog is switched off if you check the Don't Show This Dialog Again check box).

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Remote Access Dialer Components

Remote Access Dialer comprises the following components:

Client programs

These must be installed on each client workstation used for Remote Access Dialer networking. They include the following utilities:

Update Corporate Dial-Up Connections

Remote Access Passwords

Supervisor programs

These are network supervisor program snap-ins (additions) to NWADMN95. They are automatically added to the Windows** 95** Registry when you install the Dialer Administration component of the Novell Client. The snap-ins are required only on computers that you use to maintain the network.

Note:  Novell Client for Windows 95 must be installed on each client workstation used to dial in to the network.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Remote Access Dialer Software Overview
Software Overview

Remote Access Dialer for Windows** 95** is a set of client programs which provide the following extensions to Windows 95 Dial-Up Networking services:

Extended Dial-Up Networking functionality, including NetWare*/IP* and NWCAP support.

A Remote Access Password utility which allows users who are required to provide a password when dialing in, to verify or change their password.

Snap-in enhancements to NWADMN95 which allow network supervisors to maintain Corporate Dial-Up Connection definitions in NDS*. This means that users do not have to configure their own definitions. Corporate Dial-Up Connections can be configured for use on both Windows 95 and Windows** 3.x remote clients.

The Remote Access Dialer can be used on any client workstation running Windows 95 Dial-Up Networking. However, Corporate Dial-Up Connections are available only on NDS networks.

Notes:

If the Remote Access Dialer is installed on a workstation that previously ran NetWare Mobile* for Windows 3.x software, then any existing NetWare Mobile for Windows 3.x dial-in services are automatically migrated to Dial-Up Connections in the Windows 95 Dial-Up Networking folder.

If you previously ran Novell* Mobile Services for Windows 95, existing Mobile Services Dial-Up Connections remain unchanged and can be used with the Remote Access Dialer.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Security Considerations

If you implement security for remote dialing, when a dial-up connection is initiated the client workstation and remote server negotiate to use one of the available Authentication Protocols:

PAP (Password Authentication Protocol)

CHAP (Challenge Handshake Authentication Protocol)

NWCAP (NetWare Connect* Authentication Protocol)

CHAP and NWCAP support password encryption; PAP does not.

Authentication Protocol Defaults

By default, the Authentication Protocol used for a remote client connection is the first one (in the order listed above) that is supported by the remote server. So, if the server is configured to support all three protocols, PAP is used. If the server is configured to support CHAP and NWCAP only, then CHAP is used. If the server is configured for NWCAP only, then NWCAP must be used (in this case, because this is a NetWare* protocol, the connection will fail if the client does not have Novell* Client* installed).

Overriding the Defaults

To override the default protocol order and make a particular protocol available for a connection, follow the appropriate procedure below:

PAP

Do not select password encryption in the Dial-Up Connection server properties.

Ensure the remote access server configuration includes PAP.

CHAP

Select password encryption in the Dial-Up Connection server properties.

Ensure the remote access server configuration includes CHAP.

NWCAP

Select password encryption in the Dial-Up Connection server properties.

Ensure the remote access server configuration includes NWCAP (it must be a NIAS or NetWare* server).

If the server is configured for both CHAP and NWCAP, you must change the default protocol order. To do this, type the following command at the server console:

SET PPPTSM NWCAPfirst=ON

(The default is OFF.)

This changes the default order to NWCAP first; then CHAP; then PAP.

 Related Topics

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Server Prerequisites

Dial-up connections can be made to NIAS and NetWare* Connect* servers, as well as to all other PPP server types.

To create a Corporate Dial-Up Connection, NDS* must be installed on the server and you must have the Create right to the connection's container object.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Setting Up a Dial-Up Connection

Note:  You must have Dial-Up Networking installed on your workstation. Refer to your Windows** 95** documentation for information about how to install it.

A Dial-Up Connection is required for the remote computer or network that you want to dial in to. You can create your own Dial-Up Connections using Dial-Up Networking, or you can use Corporate Dial-Up Connections created and administered centrally by your network supervisor.

In either case, the Dial-Up Connections are stored in your Windows 95 Dial-Up Networking folder.

Using Dial-Up Networking

Follow the instructions in the Windows 95 documentation. For information about NetWare*/IP* properties for Dial-Up Connections, see NetWare/IPSettings.

Using Corporate Dial-Up Connections

Copy the Corporate Dial-Up Connections created by your network supervisor into your Windows 95 Dial-Up Networking folder. To do this, use the Update Dial-Up Connections dialog.

 Related Topics

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Specifying a Calling Card to Use

Refer to your Windows** 95** documentation for information about specifying a calling card.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Starting NWADMN95 for the First Time

Remote Access Dialer uses the Dial-Up Connection NDS* object class. The first time that you run the administration program after installation, the snap-ins check the NDS schema for the presence of the new object class on all Directory trees. You are prompted with a list of any trees that have not been updated with the new class. To update the schema, select the required trees and click Update.

Note:  To update the schema, you must have the Supervisor right to the root object of each selected tree.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


The Dial-Up Connection is incomplete, an area code is required on the General page
The Dial-Up Connection is incomplete, an area code is required on the General page.

Explanation

An area code has not been entered for the Dial-Up Connection. This is required if the "Use country code and area code" check box is checked.

Action

Do one of the following:

Enter the appropriate area code.

Uncheck the "Use country code and area code" check box.

Click Cancel.


The Dial-Up Connection name is incorrect. The name may not contain the following characters:

Description

An invalid name was entered.

Action

Remove the invalid characters from the name. The error message lists all characters which are invalid in Dial-Up Connection names.


The file COUNTRY.INI is missing or corrupt
The file COUNTRY.INI is missing or corrupt.

Explanation

The ADMAPIxx module could not find the COUNTRY.INI file. The file has to be in the same directory as ADMAPIxx.

Action

Check that COUNTRY.INI is in the same directory as ADMAPIxx.INI. If it is in the same directory, or if it is not present at all, then reinstall the NWADM95 snap-ins.


The file COUNTRY.INI is out-of-date or corrupt
The file COUNTRY.INI is out of date or corrupt

Explanation

The ADMAPIxx module could not read COUNTRY.INI because it was an incorrect version. The correct version of COUNTRY.INI is shown at the start of the .INI file and can be read with any text editor.

Action

Locate COUNTRY.INI and check that it is the correct version. If the correct version is not available, reinstall the NWADMN95 snap-ins.


The schema for the NDS trees listed could not be read. There are no NDS trees available with the updated schema
The schema for the NDS trees listed could not be read. This may be due to network failure or insufficient rights. There are no NDS trees available with the updated schema.

Explanation

The schema update failed because the schema could not be read. The program could not find any Directory trees to register itself with.

Action

Check that you have a working network connection and the Supervisor right to the root object of the Directory trees shown.


The schema for the NDS trees listed could not be read. This may be due to network failure or insufficient rights
The schema for the NDS trees listed could not be read. This may be due to network failure or insufficient rights.

Explanation

The schema update failed because the schema could not be read.

Action

Check that you have a working network connection and the Supervisor right to the root object of the Directory trees shown.


The schema for the NDS trees listed could not be updated. This may be due to insufficient rights
The schema for the NDS trees listed could not be updated. This may be due to insufficient rights.

Explanation

The schema update failed. The most likely cause is lack of rights.

Action

Check that you have the Supervisor right to the root object of the Directory trees shown.


The schema for the NDS trees listed do not contain the latest Dial-Up Connection administration signon changes
The schema for the NDS trees listed do not contain the latest Dial-Up Connection administration signon changes.

Explanation

The NDS* schema of the trees shown in the listbox have not been updated by this version of the snap-in.

Action

If you want to use Dial-Up Connection objects on any of the trees shown, select the relevant trees and click Modify to update the schema. You must have the Supervisor right to the root object of each selected tree.


The specified script file is too large
The specified script file is too large.

Explanation

The script file is more than 4095 bytes long.

Action

Edit the script file to reduce its length.


Trademarks, Copyright, and Patents
Trademarks, Copyright, Disclaimer, and Patents

Copyright © 1994-1998, Novell, Inc. All rights reserved. No part of this online documentation may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

U.S Patent Nos. 5,349,642; 5,594,863; 5,633,931; and 5,692,129.  U.S. and International Patents Pending.

Disclaimer

Novell, Inc. makes no representations or warranties with respect to the contents or use of this online Help system, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.  Further, Novell, Inc. reserves the right to revise this online Help system and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.  Further, Novell, Inc. reserves the right to make changes to any and all parts of NetWare software, at any time, without any obligation to notify any person or entity of such changes.

Novell Trademarks

Internetwork Packet Exchange and IPX are trademarks of Novell, Inc.

NDS is a trademark of Novell, Inc.

NetWare is a registered trademark of Novell, Inc. in the United States and other countries.

NetWare 3 is a trademark of Novell, Inc.

NetWare Connect is a registered trademark of Novell, Inc. in the United States and other countries.

NetWare Mobile is a trademark of Novell, Inc.

NetWare/IP is a trademark of Novell, Inc.

Novell is a registered trademark of Novell, Inc. in the United States and other countries.

Third Party Trademarks

CompuServe is a registered trademark of CompuServe Incorporated.

Windows is a registered trademark of Microsoft Corporation.

Windows 95 is a registered trademark of Microsoft Corporation.


Troubleshooting

Dialing -- Basic Checks

Purging the NDS Schema

Troubleshooting Dial-Up Networking Problems


Unable to browse for script file
Unable to browse for script file.

Explanation

The system File-Open dialog box failed to display. This could be due to insufficient resources.

Action

Close all other active applications and try to browse again. If this does not work, close all applications and reboot. Then retry.


Unable to create a new object
Unable to create a new object.

Explanation

You tried to create a Dial-Up Connection object but NDS* could not create it. This action requires the Create object right to the NDS container you want to create the object in.

Action

Check that you have the create object right to the NDS container.


Unable to read script file
Unable to read script file.

Explanation

The specified script file cannot be read. This could be due to a lack of the Read right or a system failure.

Action

Check you have the Read right to the script file.


Updating Corporate Dial-Up Connections

Corporate Dial-Up Connections are maintained centrally by your network supervisor so that you do not have to create and maintain your own Dial-Up Connections.

To use Corporate Dial-Up Connections, you copy them into your Windows** 95** Networking folder by running the Update Dial-Up Connections dialog.

You should run the Update Dial-Up Connections dialog periodically to update your Networking folder with the current Corporate Dial-Up Connections (you can choose to not update connections that you have modified locally in your Networking folder).

To open the Update Dial-Up Connections dialog:

1.	From the Start menu, click Programs > Novell > Dial-Up > Update Dial-Up Connections.

Hint:  For help on an item, click ? at the top of the dialog box, and then click the item.

 Related Topics

* Novell trademark. ** Third party trademark. For more information, see Trademarks.


User Modifications to Corporate Dial-Up Connections

Users can modify Corporate Dial-Up Connections which they have copied to their Windows** 95** Networking folder.

When users run the Update Dial-Up Connections dialog, they can choose to have modified connections either overwritten by the current corporate definitions or excluded from the update and kept unchanged.

This means that supervisor changes to a Corporate Dial-Up Connection are not copied to a user's Networking folder if the user has modified that connection and chooses the option to not overwrite.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Using Dial-Up Networking to Connect to a Computer or Network

Refer to your Windows** 95** documentation for information about using dial-up networking.

*Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Using Dial-Up Scripts

If you have the Windows** 95** Scripting Tool installed, you can define Dial-Up scripts for your Corporate Dial-Up Connections.

A script defined in a Corporate Dial-Up Connection is run whenever a user selects that connection to dial in with.

Scripts are defined in the Dial-Up Scripting page of Create Dial-Up Connections.

* Novell trademark. ** Third party trademark. For more information, see Trademarks.


Using Phone Dialer to Dial from Your Computer

Refer to your Windows** 95** documentation for information about using Phone Dialer.

*Novell trademark. ** Third-party trademark. For more information, see Trademarks.


Working with Remote Access Passwords

When you use a Dial-Up Connection to dial in to a remote network, you access the network via a particular dial-in point. Depending on the configuration of the dial-in point, you might be required to enter a password. If so, you can use the Remote Access Password dialog to manage your dial-in (remote) password.

Important:  This dialog does not apply to your network password. It only applies if you use a separate dial-in password. If you do not use a dial-in password, or if you use your network password as your dial-in password (NWCAP Advanced NetWare* security enabled), do not use this dialog. Check with your network supervisor if you are unsure which password you should be using.

The Remote Access Password dialog lets you

Query your remote password

Change your remote password

Querying Your Remote Password

Generally, you are required to change your remote password at specified intervals set by your network supervisor. You can check when your current password will expire (in days). If your password has already expired, a message informs you of how many grace logins you have available to change your password before you are locked out.

Changing Your Remote Password

Unless your network supervisor has specified otherwise, you can change your password at any time, and you must change it if the specified interval for your current password has expired.

To run the Remote Access Password dialog:

Dial-in

From the Start menu, click Programs > Novell > Dial-Up > Remote Access Password.

* Novell trademark. ** Third-party trademark. For more information, see Trademarks.


dial in

To initiate a connection to a remote network. The connection is always made to a "dial-in point" on the network. A dial-in point is a piece of equipment on the network (often but not always a server) which controls remote requests to dial in to the network. Both your workstation and the network dial-in point must have appropriate dialing equipment attached (such as a modem and telephone line).


dial-in point

A piece of equipment on the network (often but not always a server) which controls remote requests to dial in to the network.


Dynamic Host Configuration Protocol (DHCP)

The rules by which an IP address can be assigned to a workstation when the workstation requests one.