Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Microsoft Network Client Version 2.2: User's Guide for MS-DOS Clients > Appendix E Using Remote Access Service

Troubleshooting

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

This section explains how to solve common problems and provides a complete list of error codes.

Common Problems

Network Access Problems

If you are denied access to your network, contact your network administrator. You may not have a valid user account on your Windows NT or LAN Manager network, or you may not have permission to dial in.

Connection and Response Problems

If the RAS server is not responding, one or more of the following may be true:

  • The RAS server is not running. Contact your network administrator.

  • You are using an incompatible version of the RAS software. Contact your net work administrator.

  • The modem on the RAS server has been turned off. Contact your network admin istrator.

  • Your modem and/or modem configurations are incompatible with the modem on the RAS server. Contact your network administrator.

  • Your hotel room telephone line cannot accommodate your current modem speed. Use a lower baud rate, or contact the hotel manager to request a direct line.

  • You specified the wrong telephone number. Update your Phone Book entry and redial.

  • You did not specify a special number that gives you an outside line. For example, some businesses and hotels require you to dial 9 before dialing your number.

  • There is static on the telephone line. Contact your phone service provider. u

  • The RAS server does not call back as expected. Your account may not be prop erly configured, or your modem setting may be incorrect on the server. Contact your network administrator.

  • You cannot access network resources even though the connection appears intact. Contact your system administrator.

  • You are disconnected from the network when you start Microsoft Windows ver sion 3.0. When running MS-DOS and Microsoft Windows version 3.0 and using a serial mouse, be sure to start the Windows operating system before connecting. Alternatively, you can upgrade to Microsoft Mouse version 8.0 or later. When us ing the version 8.0 mouse driver, change the second line in the MOUSE.INI file from AUTOMATIC SEARCH to SERIAL1 or SERIAL2, depending on which serial port the mouse is attached to. Contact Microsoft Product Support Services for information on upgrading mouse drivers.

Modem Problems

If your modem is not responding properly, one of the following may be true:

  • Your modem has been turned off or unplugged.

  • Your modem is not properly connected to your computer.

  • Your modem is in an inconsistent state. Restart or reset your modem and redial.

  • Your modem and/or modem cables are defective. Contact your network admin istrator to make sure you have the correct modem cable for RAS.

  • Your modem type is not supported by RAS, or it is not a fully compatible version of the modem type you selected. Contact your network administrator.

  • Your modem is not configured correctly. See your modem user guide, or contact your network administrator.

  • If your modem connects at a lower baud rate than you specified, the RAS server may have a modem type different from what you are using. Contact your network administrator.

Display Problems

If your screen blacks out when running MS-DOS and the version 7.0.4 mouse driver, upgrade your mouse driver to version 8.0 or later.

Loading and Unloading Problems

If you encounter problems when loading the RAS drivers, one of the following may be true:

  • The RAS drivers are already loaded.

  • There is insufficient MS-DOS memory available. Unload some TSR) programs and try again.

  • There is insufficient storage space on your hard disk. Ensure that your hard disk has a least 1MB of free space.

If you encounter problems when unloading the RAS drivers, one of the following may be true:

  • A telephone connection still exists. Drivers will not unload if a telephone connection exists. This protects you from accidentally hanging up a connection and losing data. Save your data files, disconnect the phone line, and then try the rasload /u command again.

  • You have an incorrect TSR unloading order. Before unloading RAS, you must unload all TSR programs that were loaded after RAS was loaded. For example, if you loaded DOSKEY after loading RAS, you must unload DOSKEY prior to unloading RAS. Typing net start workstation after typing the rasload command also causes a TSR unloading error. Restart and then unload the RAS drivers.

Performance Problems

If you encounter poor performance while using RAS, one of the following may be true:

  • If you encounter errors on the line and poor performance, contact your network administrator.

  • If it takes a long time to log on to your network after you establish a connection, you may have many persistent network connections. You could remove all persistent connections by typing net use /persistent=no at the command line, or add autorestore=no and saveconnections=no in the [netshell] section of LANMAN.INI, or you could save only the connections you set up at login by typing net use /persistent:save. If this doesn't improve logon performance, check with your network administrator.

Error Codes

This section lists the error codes sent by rasdial, the command-line version of Remote Access service. If you are calling from the MS-DOS command line, you can use the error level returned to look up the cause of the error in the following table. Error codes that are not self-explanatory are followed by a description.

Error Code

Error Level

Description

ERR_USEDPORT

612

The port is already in use.

ERR_BADBAUD

615

The baud rate cannot be set for the port.

ERR_NOPORT

620

The port is already in use.

ERR_CONNECTION_TIMEOUT

631

A timeout occurred while trying to establish a connection.

ERR_REMOTE_DISCONNECTED

632

The remote side has been disconnected.

ERR_HARDWARE_FAILURE

633

Hardware (the modem most probably) has failed.

ERR_MODEM_NOT_RESPONDING

640

The modem did not echo back the string or did not respond to the string with something like OK.

ERR_MODEMS_INI_FILE_CORRUPTED

642

ERR_UNEXPECTED_MODEM_STRING

643

A modem string not listed in the MODEMS.INF file was returned.

ERR_COULD_NOT_OPEN_MODEMS_INI

644

ERR_INVALID_MODEM_COMMAND

645

ERR_NULL_PHONENUMBER

646

ERR_SYNTAX_ERROR

648

ERR_WANTSR_NOT_LOADED

652

Because rasload was not executed before attempting a connection, a TSR program required by RAS was not loaded.

ERR_INVALID_USERNAME

653

ERR_INVALID_PASSWORD

654

ERR_WKSTA_NOT_STARTED

664

ERR_PHONEBOOK_EMPTY

665

ERR_CANNOT_GET_LANA

669

A configuration problem exists. Run Setup again.

ERR_INVALID_PHONE_NUMBER

668

ERR_CANNOT_BIND_LANA

670

A configuration problem exists. Unload NetBEUI and start again. If the problem persists, reinstall RAS.

ERR_CANNOT_UNBIND_LANA

671

ERR_NOT_AUTHENTICATED

672

ERR_COULD_NOT_OPEN_COMDEV_INI

675

ERR_COULD_NOT_OPEN_PHONE_INI

676

ERR_CORRUPT_COMDEVINI_ENTRY

677

ERR_CORRUPT_PHONEINI_ENTRY

678

ERR_ENTRY_NOT_FOUND

682

ERR_CORRUPT_COMDEVINI

683

ERR_CONNECTION_EXISTS

684

ERR_SERVER_NOT_RESPONDING

685

ERR_TOO_MANY_INITIAL_NAMES

686

ERR_CANNOT_GET_COMPUTERNAME

687

The user is running a LAN Manager Basic workstation. Either install LAN Manager Enhanced or specify the computer name when starting the Workstation service.

ERR_MSG_ALIAS_NOT_ADDED

689

ERR_NAME_OUT_OF_RESOURCES

690

The RAS server does not have enough resources to add all the NetBIOS names for the client machine. Ask the network administrator to increase NetBIOS resources on the server.

ERR_NAME_ADD_CONFLICT

692

ERR_NO_DIALIN_PERM

694

ERR_LISTEN_TIMEOUT

695

MODEM_RC_NO_CARRIER

6101

MODEM_RC_NO_DIALTONE

6102

MODEM_RC_NO_ANSWER

6103

MODEM_RC_BUSY

6104

MODEM_RC_LOOP

6105

MODEM_RC_ERROR

6106

Your modem returned a generic error code. Redial.

ERR_CANNOT_OPEN_PAD_INI

6112

ERR_PAD_INI_FILE_CORRUPTED

6113

ERR_UNEXPECTED_PAD_STRING

6114

The PAD responded with a string not recognized by RAS.

ERR_PAD_NOT_RESPONDING

6115

ERR_NULL_X25ADD

6116

No X.25 address was supplied to make the connection.

PAD_RC_ERROR

6117

The PAD returned a string denoting an error condition.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1996 Hewlett-Packard Development Company, L.P.