home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Pratica
/
IPRAT_01.iso
/
ASP
/
PWS
/
rasics.cab
/
readme.txt
< prev
next >
Wrap
Text File
|
1997-10-14
|
7KB
|
155 lines
------------------------------------------------------------------------
Microsoft Connection Manager Readme File
August, 1997
------------------------------------------------------------------------
(C) Copyright Microsoft Corporation, 1995-1997
This document contains important, late-breaking information about this
product.
You can view the Readme file in Windows Notepad. To print the
Readme file, open it in Notepad or another word processor, and then use
the Print command on the File menu.
Before installing this product, please review this entire document. The
document contains critical information to ensure proper installation
and use of the product.
----------------------------------------------
Known Issues with Microsoft Connection Manager
----------------------------------------------
* In Windows NT, the "Disconnect if idle for more than" setting
may not work properly.
* Connection Manager requires certain files that are supplied by
Internet Explorer 3.0 or later. If you remove Internet Explorer,
Connection Manager will no longer work.
* Do not install two copies of Microsoft Connection Manager in
two different folders on the same computer. This will cause the
original service profiles to become disassociated with Connection
Manager. To prevent this, install both versions into the same folder.
* In Windows 95, if you try to establish a Dial-Up Networking
connection with your ISP, you might see an error message in the
Microsoft Connection Manager dialog box stating that you need to
type a phone number. If this happens, click Settings. When the
Location Information dialog box appears, follow the instructions,
and then click OK.
* In Windows NT, if you try to establish more than one connection,
you might see the message, "The modem is not configured properly. "
This sometimes happens if you try to dial too quickly, or if you start
Microsoft Connection Manager when a connection has already been
established using Dial-Up Networking. Disregard the message.
Use one connection at a time.
* In Windows NT, you might have problems with Remote Access
Services (RAS), which is automatically installed by the
Connection Manager service profile. Make sure RAS is
configured to use a manual startup type,
and that you have privileges to start RAS.
To do this,
1. Click Start, point to Settings, click Control Panel,
and then double-click Services.
2. In the Services list, double-click Remote Access Service.
3. In the Service dialog box, click Manual, and then click OK.
* In Windows NT, if you change the Disconnect if idle for more
than setting, the change you made will not take effect until
you quit Microsoft Connection Manager and then restart it.
* If you type or edit the phone number in the Dialing tab of
the Connection Settings dialog box, make sure you use the
proper form for the phone number. If you do not, the
Connection Manager will not use the Dialing Properties
that you have set up when dialing the telephone number.
The proper form is as follows:
+[country code] (area code) phone number
For example, if your country code is 1, your area code is 800,
and your phone number is 555-1212, you should type the phone
number as follows, making sure to include the "+" sign, spaces, and
parentheses:
+1 (800) 5551212
If you do not use this form, make sure you enter the
number exactly as it is to be dialed.
* If you are using Microsoft Dial-Up Networking 1.2, and the
following message appears, disregard it:
This DHCP client was unable to obtain an IP network
address from a DHCP server. Do you want to see future
DHCP messages?
* Microsoft Connection Manager does not work on Windows NT 4.0
with some internal ISDN network adapters, including the
Diamond Supra NetCommander ISDN Modem.
* Connection Manager supports using single-channel ISDN. You can
manually configure Connection Manager to to use dual-channel ISDN.
If you are running Windows 95, use the following steps to set up
dual-channel ISDN:
1. Click Start, then point to Programs, then point to Accessories,
and then click Dial-Up Networking.
2. Right-click the connection icon for your ISP and then click
Properties.
3. Click the Multilink tab.
4. Click Use additional devices, and then click Add.
5. In the Edit Extra Device dialog box, select the device for
your extra ISDN channel, and then type the phone number for
that device.
If you want to use dual-channel for your backup connection icon,
repeat the above steps for your backup connection icon.
Once you have used this technique to set up a dual-channel connection
icon for use with Connection Manager, if you change either your primary
or backup phone number, you will also have to edit the multilink phone
number that you entered in step 5.
If you are running Windows NT, see your Windows NT documentation for
information on setting up dual-channel ISDN connections.
* Connection Manager will automatically install the TCP-IP protocol,
but no other protocols. If you use a service profile that requires
a protocol other than TCP-IP, make sure you install it before attempting
to connect to your ISP. To do this:
1. Click Start, point to Settings, click Control Panel,
and then double-click Network.
2. Click the Services tab, then click Remote Access Service, and then
click Properties.
3. Click the modem or VPN adapter, and then click Network.
4. In the Dial out Protocol list, click the protocol that your
service profile uses.
* If you are running Windows NT and using Connection Manager to
establish a Dial-up Networking connection, Connection Manager does
not support popping up a terminal window after dialing. (Bringing up
a terminal window before dialing, however, is supported.) If your ISP requires
that your connection causes a terminal window to pop up after you connect,
contact your ISP and ask for a dial-up script that will bring up the terminal
window.
* If you are running Windows NT and using a Connection Manager service profile
that requires Dial Up Scripting, you must install Windows NT Service Pack 3.
* Windows 95 users may see problems in Connection Manager displays,
resulting from the installation of a service profile that uses a
different language than the one configured for use by the operating
system.
* Numbers typed in a double-byte character set (DBCS) are not accepted.
To type numbers on a DBCS version of Windows 95 or Windows NT,
use an Input Method Editor (IME) set up to produce single-byte
character set (SBCS) numbers.
Examples of DBCS versions include, but are not limited to, Japanese
and Hangeul.