|
Troubleshooting Dial-Up Networking |
1st, any or all of these files may be corrupted, so I always recommend that you rename the old one and extract new non-corrupted files to the directories shown;
RNAAPP.EXE Module Dependency List
ADVAPI32.DLL c:\windows\system\
GDI32.DLL c:\windows\system\
KERNEL32.DLL c:\windows\system\
MPR.DLL c:\windows\system\
MSPWL32.DLL c:\windows\system\
MSVCRT20.DLL c:\windows\system\
NETAPI32.DLL c:\windows\system\
NETBIOS.DLL c:\windows\system\
RASAPI32.DLL c:\windows\system\
RNAAPP.EXE c:\windows\system\
SECUR32.DLL c:\windows\system\
SVRAPI.DLL c:\windows\system\
TAPI32.DLL c:\windows\system\
UMDM32.DLL c:\windows\system\
USER32.DLL c:\windows\system\
You must set Dial-Up Networking Server to allow caller access options.
1. In Dial-Up Networking, click the Connections menu, and then click
Dial Up Server.
2. In the the Dial-Up Server properties, click Allow Caller Access,
if this is not already selected, and then view the User name list to ensure
the user’s name appears.
The User name list appears only if you have chosen user-level security
for the dial-up server. The type of security is selected in the Network
option in Control Panel.
If the dial-up client is also running File and Printer Services for
NetWare Networks, the File and Printer Sharing service automatically becomes
the default server, but it cannot receive the information needed to find
the remote servers.
Disable File and Printer Sharing Service for NetWare Networks when you make the dial-up connection.
Check the settings for the dial-up server type and software compression.
1. In the Connections menu, click Dial-Up Server.
2. Click the Server Type button and verify that the correct type of
dial-up server is selected.
3. Check that Enable Software Compression is selected. Compression
will occur only if the dial-up client and server have enabled it.
Check the modem configuration; change the configuration if necessary.
Verify all parameters, such as access codes, area code, and country
code.
Try choosing the driver for Generic Modem Drivers.
If you are using an external modem, check the cable and verify that
it is connected correctly.
Check the COM port configuration in Device Manager.
For more information, see the troubleshooting section in Modems and
Communications Tools.
1. Disable Allow Caller Access and shut down the computer. Turn off
the computer to reset the COM port. If the modem is external,
turn off the modem. Turn the computer back on and reconfigure the Dial-Up
Networking server, and then try again.
2. If these steps fail, disable Allow Caller Access and see if any
modem software can manually answer the incoming call.
3. If you are using an external modem, check the cable and verify that
it is connected correctly.
4. If you are using an internal modem with a nonstandard IRQ selection,
use Device Manager to check the IRQ setting for the COM port and change
it if necessary.
5. Try choosing the Generic Modem Drivers on the dial-up server.
The password for the Dial-Up Networking server is stored in the RNA.PWL file. However, simply deleting this file or removing and reinstalling Dial-Up Networking may not remove the password. If you set the Dial-Up Networking server to monitor for calls, then delete the RNA.PWL file, the password is not removed because it is stored in memory. If you shut down Windows 95 at this point, the RNA.PWL file is recreated with the password in memory.
To replace a forgotten password in a Dial-Up Networking Server
1. Disable Allow Caller Access, and then shut down and restart Windows
95.
2. Delete the RNA.PWL file, and then restart the Dial-Up Networking.
NOTE: When you first connect to the Dial-Up Networking server, an error message states that the password file is missing or corrupt for every modem device you have installed. If you have any null modem devices installed (for example, when you run Direct Cable Connection it installs a modem device for every COM and LPT port you have), this error message also appears.
The problem can be caused by any of the following:
Password caching is disabled.
One or more of the files associated with Dial-Up Networking is missing
or damaged.
Your password list (.pwl) file is damaged.
The Rna.pwl file (if it exists) is damaged.
NOTE: This problem has been known to occur after installing the Windows
95 Password List Update that is included with Microsoft Windows 95 Service
Pack 1. See article #Q143003 in the Microsoft Knowledge Base.
To resolve the problem try the following steps, and after step, check
to see if the issue has been resolved.
1. Verify that password caching is enabled. To do so, examine the following
registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\ CurrentVersion\
Policies\Network\DisablePwdCaching
If password caching is disabled, this registry value is present with
a value of 1.
NOTE: You can edit the registry using System Policy Editor (Poledit.exe)
or Registry Editor (Regedit.exe).
System Policy Editor (Poledit.exe) is available in the Admin\Apptools\Poledit
folder on the Windows 95 CD-ROM.
Use the Add/Remove Programs tool inControl Panel to install System
Policy Editor.
NOTE: System Policy Editor is not included in the floppy disk version of Windows 95. You can download Policy.exe, a self-extracting file containing Poledit.exe, from online services.
If password caching is disabled on your computer, use the following
steps to edit the registry with System Policy Editor and enable password
caching in Windows 95:
a. Click the Start button, and then click Run.
b. Type "poledit" (without quotation marks) in the Open box, and then
click OK.
c. On the File menu, click Open Registry, and then double-click Local
Computer.
d. Double-click Network to expand it, and then double-click Passwords.
e. Click the Disable Password Caching check box to clear it, and then
click OK.
f. Save the changes to the registry, quit System Policy Editor, and
then restart Windows 95.
2. Remove Dial-Up Networking, and then reinstall it. To do so, follow
these steps:
a. In Control Panel, double-click Add/Remove Programs.
b. Click the Windows Setup tab.
c. Click Communications, and then click Details.
d. Click the Dial-Up Networking check box to clear it, click OK, and
then restart your computer if you are prompted to do so.
e. Repeat steps A-C.
f. Click the Dial-Up Networking check box to select it, and then click
OK.
3. Rename your .pwl file. To do so, type the following line at a command
prompt, and then press ENTER
ren c:\windows\username.pwl username.xxx
where "windows" is the name of your Windows folder and <username>
is the user name you use to log on to Windows 95. After renaming your .pwl
file, restart your computer. When the Enter Network Password or Welcome
To Windows dialog box appears, type the password that you normally use,
and then click OK. When you are prompted to confirm the password that you
entered, type the password again in the Confirm New Password box, and then
click OK.
NOTE: If there are no .pwl files present on the drive (for example,
the user pressed the ESC key when prompted for a password as Windows 95
starts) password caching will not be enabled. The user must first log on
to the network in order to create a .pwl file.
4. Rename the Rna.pwl file in the Windows folder. To do so, type the
following line at a command prompt, and then press ENTER: ren c:\windows\rna.pwl
rna.xxx
Where "windows" is the name of your Windows folder. After renaming
the Rna.pwl file, restart your computer.
NOTE: The Rna.pwl file may not exist on your computer. This file is
not required in some configurations.
What You Need
Here a list of information you need to get from your ISP (Internet
Service Provider) before you can use Dial-Up Networking. If you don't yet
have an ISP, see the Special Considerations section for some tips in selecting
one.
1. A local phone number (make sure it is a local number and supports
the highest speed of your modem).
2. Your username and password.
3. The domain name of your ISP (usually company_name.com).
4. Your host name (can also just be your username).
5. The following IP addressses (each with four numbers separated by
periods; i.e. 123.456.789.12):
6. Subnet Mask
7. DNS Address (Domain Name Server; sometimes there are two of these).
8. Gateway Address
9. Whether your ISP supports PPP or SLIP (if you get both, PPP is better):
10. Any special connection instructions, if your ISP doesn't support
standard PPP.
11. Any Windows95-compatible modem of at least 14,400 baud, installed
and functioning. Make sure it's configured correctly by double-clicking
on the Modems icon in Control Panel.
Installing Drivers
Take the following steps to insure you have the proper drivers installed:
Part 1:
1. Double-click on the Add/Remove Programs icon in Control Panel.
2. Click on the Windows Setup tab, highlight Communications in the
list of components, and click Details.
3 Make sure you have a checkmark next to the Dial-Up Networking component.
If not, check it now, and press OK; you'll be asked to restart your computer
at this point.
Part 2:
1. Double-click on the Network icon in Control Panel.
2. You'll need the following network components installed:
3. Client for Microsoft Networks
4. Dial-Up Adapter
5. TCP/IP
6. File and printer sharing for Microsoft Networks (optional) 7. If
you don't have any or all of these installed, click Add... to add them
to your list. Notes: TCP/IP is known as a "protocol," and File and printer
sharing is known as a "service." All of these components can be found by
selecting "Microsoft" in the "Manufacturers" list.
8. Note: if you have other adapters installed, such as a network card,
make sure TCP/IP is installed for the dial-up adapter.
9. If you made any changes here, you'll have to restart Windows.
Configuration
Once you've obtained the necessary information, and have installed
the correct drivers, you can configure Dial-Up Networking to work with
your ISP.
Part 1:
1. Double-click on the Network icon in Control Panel.
2. Highlight TCP/IP in the components list, and click Properties.
3. In the IP Address tab, select Obtain an IP address automatically.
4. In the WINS Configuration tab, select Disable WINS Resolution.
5. In the Gateway tab, type in the Gateway IP address obtained from
your ISP, and click Add so that it is listed in Installed gateways.
6. In the Bindings tab, check Client for Microsoft Networks only.
7. Don't do anything in the Advanced tab.
8. In the DNS Configuration tab, select Enable DNS. Type in your domain
name in both the Domain field and Domain Suffix field, and type your hostname
in the Host field. Lastly, type in your DNS (or both, if you have two),
and click the Add button. All this information can be obtained from your
ISP.
9. Click OK when you're done.
10. While still in the Network window, click on the Identification
tab. Type in your username in the Computer name field.
11. Click OK when you're done - you'll probably have to restart Windows
at this point.
Part 2:
1. Double-click on the Dial-Up Networking icon in My Computer.
2. Double-click on Make New Connection, if you don't already have one.
3. Enter a name for this connection (it doesn't really matter), and
select the correct modem from the list.
4. Click Configure, to make sure your modem is configured correctly.
Set the maximum speed to 57,600 for 14.4 modems and 115,200 for 28.8 modems.
You might want to turn up the volume until you're sure the connection works.
Make sure Only connect at this speed is not checked, and click OK when
you're done.
5. Click Next, and then type in the phone number obtained from your
ISP.
6. Click Next, and then Finish.
7. You can change any of these settings later on by right-clicking
on the connection and selecing Properties.
Part 3:
1. Double-click on the connection to connect!
Special Considerations
Since there are so many different kinds of connections, it can be difficult
to get Windows95 to work with your particular circumstances. Here are some
tips for non-standard connections:
1. Scripting - some connections have a complicated login procedure, requiring you to Add Scripting to Dial-up Networking. Once you've obtained the correct scripting utility (there are a few from which to choose), you'll need to determine your login procedure. Here's how you do it:
2. Double-click on the Dial-Up Networking icon in My Computer.
3. Right-click on your connection, and choose Properties.
4. In the Connect using portion, click Configure, and then click on
the Options tab.
5. Turn on the Bring up terminal window after dialing option, and click
OK to close all the windows.
6. Start your connection by double-clicking on the connection icon.
7. After you've dialed, a window will appear, allowing you to type
any necessary commands. You must contact your ISP to obtain any special
login procedure.
8. Write down all the prompts you see (noting all capitalization since
everything is case-sensitive), as well as all commands you type.
9. Once you've determined your exact login procedure, enter your commands
into the scripting utility you've chosen (the syntax will vary; consult
the documentation).
10. Once you have it working, you'll hopefully never need to do this
again!
1. SLIP - although less commonly used than PPP, and not as well supported, a SLIP connection is possible with Windows95. You'll need to download SLIP and Scripting for Dial-Up Networking.
2. Multiple Connections - if you have more than one phone number for your account, or more than one account, you can add additional connections using the configuration instructions above (see part 2). When you've added another icon to Dial-Up Networking, right-click on it, and select Properties. Click Server Type, and then TCP/IP Settings to change the settings for each individual connection. If you do set up multiple connections, make sure that you specify the settings here instead of in Control Panel - just clear all your DNS, gateway, and IP settings in Control Panel so that Windows95 will use the settings in your individual connections.
1. Call Back - if your ISP uses a call-back procedure (where another
machine calls your computer to connect), try these suggestions:
2. Obtain and install Trumpet Winsock for Windows95 (not a true 32-bit
application, but it uses a 32-bit dll layer so all of your 32-bit winsock
applications will work). Follow the included installation instructions,
but in your Windows directory, rename WINSOCK.DLL to WINSOCK.MS, and in
your Windows\System directory, rename WSOCK32.DLL to WSOCK32.MS. - submitted
by Philippe Steindl
1. Commercial Services - if you use Compuserve, or another non-internet commerical service, you might be able to use Dial-Up Networking with it as long as you have an Internet icon in Control Panel. Downlaod the latest version of Internet Explorer if you don't have this item.
1. Selecting an ISP - if you don't yet have an Internet Service Provider,
or your university is about to kick you off their system, here are some
things to look for:
2. No hourly rate - hourly rates are a rip-off, plain and simple. Some
ISPs give you a few free hours per month; don't settle for less than 50
(they go quicker than you think). Many providers now sell a flat-rate service
(no hourly charges whatsoever) for around $20 per month.
3. Local Number - don't let the phone company profit from your internet
access. If you dial a local number, you can still connect to anywhere in
the world, but not on your dime (see the previous tip).
4. Private Provider - dealing with a small, local provider (look in
the phone book) will probably mean lower rates, as well as better service
and support. Unless you travel frequently and need local access around
the country (or the world), forget the national providers and their proprietary
software.
1. Distributing a Connection - say you're an ISP, and would like to
send your customers a file with all of your connection information, rather
than spending hours on the phone walking them through the setup process.
Here's how to do it:
1. Run the Registry Editor (REGEDIT.EXE).
2. Open HKEY_CURRENT_USER\ RemoteAccess\ Profile, and select the key
associated with the desired connection (there may be only one, or many).
3. Select Export Registry File from the File menu, and save this branch
in a file on your hard disk.
4. Then, go up one level to HKEY_CURRENT_USER\ RemoteAccess\Addresses
- this key contains values for all of the connections, rather than keys,
meaning that if you export this key, all of the values will go with it.
5. Again, select Export Registry File from the File menu, and save
this branch in another file on your hard disk - this file will contain
entries for all of connections, so if you have more than one connection
here, you must edit the second Registry file manually with a text editor
and remove the unwanted entries.
6. At this point, you can merge the two registry files (using a text
editor, such as Notepad, and making sure the word "REGEDIT4" appears only
once).
7. When you're finished, you should have a single Registry file (*.REG),
on which a user can simply double-click to add the connection to their
system.
Note: This process doesn't include the installation of the drivers,
however, or any special provisions for scripting - those you'll have to
handle on your own. Make sure you specify all of the settings for the connection
(DNS, etc.) in the connection's properties sheet (Server Type), rather
than in Control Panel.
1. ISDN - or Integrated Services Digital Network, gives internet users
a connection speed of up to 128kbps. Here are some tips and links for ISDN
users:
2. See Dan Kegel's ISDN Page for a comprehensive and exhaustive collection
of hardware and software information.
3. If you have an internal ISDN adapter, you'll need Microsoft's ISDN
Accelerator Pack (not necessary for external ISDN adapters).
4. A new service by Microsoft, Get ISDN for Microsoft Windows, will
supposedly help you get your ISDN service up and running.
5. If you're experiencing performance problems, such as all communications
halting temporarily every few minutes, try specifying a value of 576 for
your MTU. See Change the MTU and RWIN Settings in Dial-Up Networking for
more information.
If your connection (or any of your Internet applications) don't work, or you're experiencing poor performance, the problem could be caused by any number of things. Here are a few possibilities:
1. If you were using another Internet dialer previously (such as Trumpet
Winsock), check the following:
2. Make sure you don't have any other winsock stacks in your path (specified
in AUTOEXEC.BAT).
3. Search your entire system for files named WINSOCK.DLL, and delete
or rename any copies that aren't dated 7/11/95 (the one that comes with
Windows95). If you can't find one dated 7/11/95, then you'll have to retreive
it from the distribution disks. (more information)
1. It could an ISP problem:
2. Dial the number manually with your telephone and see if you hear
beeps on the other end, and not an answering machine, a busy signal, or
a Chinese restaurant.
3. The information obtained from your ISP is incorrect - make sure
all your IP addresses are correct, and check your settings for typos. Make
sure you hit Add when necessary after entering IP addresses.
4. If your ISP doesn't support standard PPP, you might need to Add
Scripting to Dial-up Networking - contact your ISP's technical support
for details and assistance.
5. Make sure your ISP account is actually functioning - it can take
up to several days after you subscribe before you can use your account.
6. If all else fails, contact your ISP for help - since many folks
use Windows95, they'll probably be able to diagnose and solve the problem
easily. Some ISP's require special settings!
1. Don't rule out hardware problems:
2. Make sure your modem is turned on, functioning correctly, and configured
correctly by using HyperTerminal to connect to the same number. Note: if
you don't use a true Windows95 communications program, you're not testing
the modem configuration!
3. If you're connecting, but not at a satisfactory speed, try replacing
the phone cord.
4. Try restarting Windows95 to see if that helps, and make sure there
aren't any other programs trying to use your modem or communications port.
5. If all else fails, you'll have to contact the manufacturer of your
modem for technical support and possibly a driver or bios update.
1. If things are just too slow:
2. Try specifying a value of 576 for your MTU (especially for ISDN
connections) - an indicator of this problem is if communications seem to
halt temporarily every few minutes. See Change the MTU and RWIN Settings
in Dial-Up Networking for more information.
3. Newer drivers (obtained from the manufacturer of your modem can
improve performance.
4. Noisy phone lines can slow connections because your modem is spending
more time with error correction; try replacing your phone cables.
5. Test your throughput by transferring a binary file (text files aren't
a reliable indicator, due to compression).
After you've done the math, you should experience about
1. 6 kilobytes/second with a 14,400 connection,
3.4 kilobytes/second with a 28,800 connection, and
12 kilobytes/second with an ISDN connection.
Related Information
Here is a list of other information on Windows95 Annoyances that may
help to troubleshoot as well as improve performance with your connection:
http://www.creativelement.com/win95ann/intro.html
1. Add Scripting to Dial-up Networking
2. Turning on Auto-redial in Dial-Up Networking
3. Bypass the "Connect To" Dialog Box
4. Use Dial-Up Networking over a LAN
5. Speed Up Dial-Up Networking Initialization
6. Change the MTU and RWIN Settings in Dial-Up Networking
7. Enabling Autodial with Dial-Up Networking
8. Get Rid of the Little Flashing Modem in the Tray
Q182108
Availability of Windows Sockets 2.0 for Windows 95
TCP/IP was modified to reset the running timer value so that the packet with the correct sequence number is sent immediately.
Microsoft has confirmed this to be a problem in Microsoft Windows 95 and OEM Service Release 2 (OSR2). An update to address this problem is now available, but is not fully regression tested and should be applied only to computers experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft does not recommend implementing this update at this time. Contact Microsoft Technical Support for additional information about the availability of this update.
This issue is resolved in Microsoft Windows 98.
For additional information about the ARP cache, please refer to RFC 1122.
For additional information about issues resolved by updates to this component, please see the following articles in the Microsoft Knowledge Base:
Q178022 NetBIOS SEND WAIT Over TCP/IP Completes Without NetBIOS RECEIVE
Q177539 Windows 95 Stops Responding Because of Land Attack
Q170791 Windows 95 TCP Clients Run Out of Ports
Q168747
Update to Windows 95 TCP/IP to Address Out-of-Band Issue
For additional information about Windows 95 updates, please see the following article in the Microsoft Knowledge Base:
Q161020
Implementing Windows 95 Updates
Unable to Negotiate Network Protocols
To fix this problem, go through the following steps.
1.Open your MY COMPUTER ICON
2.Open CONTROL PANEL
3.Open your NETWORK ICON
4.In this window you will see
5. If your computer is all by itself (Not connected to other computers
on a Network) you should only have the following three Components Installed:
Client for Microsoft Networks
Dial Up Adapter
TCP/IP
6. If you have any other Components such as
Client for Netware Networks
IPX/SPX Compatible Protocol
NetBEUI Compatible Protocol
You will need to click on the Component one time and then click on the
REMOVE button. This will remove the component from you computer. These
other components / protocols can interfere when connecting to Your ISP.
If the top three are the only components installed skip down to 7.
If by chance you remove the wrong component you can click on the ADD
button and follow the menus to re-install the components. Windows may ask
you to insert your Windows95 CD-ROM or diskettes upon re-installing components
or protocols.
After following the above steps, Click OK in your Network window. Windows95
will prompt you to restart your computer at this time. TELL IT NO, DO NOT
RESTART THE COMPUTER. Go to 7.
7. Close your Control Panel window and go back into your MY COMPUTER window. Double click on the DIAL-UP NETWORKING icon. You should now see two icons, Make New Connection and the Icon you use to connect to Your ISP. ( It may not be called "Your ISP")
8. Place your mouse cursor on top of the Your ISP Icon and click the RIGHT Mouse Button. A menu will pop up, scroll down to "Properties" and click the left mouse button on it.
You will now be in your Your ISP window. In the bottom right corner of the Your ISP window, click on the SERVER TYPE button, a new window called Server Types will pop up. Make sure ONLY THE FOLLOWING are checked:
These options SHOULD be checked
Under the Advanced Options
Log onto Network
Enable Software Compression
Under Allowed Network Protocols
TCP/IP
These options should NOT be checked
Under the Advanced Options
Require encrypted password
Under Allowed Network Protocols
NetBEUI
IPX/SPX Compatible
9. Now click on the TCP/IP Settings button in the Server Types window.
You should ave the following options Checked.
Server assigned IP address
Server assigned Name Server addresses
Use IP header compression
Use default gateway on remote network
10. Click OK in all of the Windows that you have open.
Close any open windows
Go to your Start menu, Shutdown, Restart the Computer.
Click Ok to restart your Computer.
Your computer will now shutdown and restart itself with your modified settings in place. I hope this works:)
Your ISP will not accept your password
This Problem is primarly caused by incorrectly entering your username
and password. Look at the following Example to see how your username and
password should look This is only an example, your username and password
will be different.
Username=What Ever you have chosen
Password=What Ever you have chosen
If you enter you 'BILL' instead of 'bill' our computer will not accept it. These are CASE SENSITIVE. It sees a Capital 'A' and a Lowercase 'a' as being two completley different characters. By default everything in your username and password should be entered in lowercase letters.
- Error: port in use
- OpenComm: Port already open
The reason for this behavior is that Rnaapp.exe is active in memory.
You can work around this issue by performing the following steps, however
there's no formal fix at this point:
1. Press CTRL+ALT+DELETE to open the Close Program dialog box.
2. Click Rnaapp to select it, and then click End Task.
3. Start your communications program.
When you finish using a communications program and close the connection,
Rnaapp.exe is still running and the port remains unavailable to non-TAPI
programs. Rnaapp.exe is left in memory to allow TAPI programs to open faster.
Rnaapp.exe is eventually unloaded from memory (unless Dial-Up Networking
Server is set to allow caller access), but it may take 10-15 minutes. Sorry,
but MS hasn't found a fis for this one yet though!
RNAAPP AND UTILITIES
Another involves the installation of a program called Pipeline.
PIPELINE
After you install Pipeline version 3.5, you may not be able to connect
to MSN, The Microsoft Network. When you click Connect, all the boxes on
the Sign In screen, except Cancel, may be unavailable and the telephone
number may not be dialed.
This is caused by Pipeline version 3.5 installing its own version of
the Wsock32.dll file in the Windows\System folder. This file is 57K in
size. The original Wsock32.dll file (which is 65K in size) installed by
MSN is renamed to Wsock32.ms.
You can fix this by using the Pipeline Switcher Program. The Pipeline
Switcher program lets you switch between the two Wsock32.dll files.
To use this program, follow these steps:
1. Close the Sign In screen and all Winsock programs.
2. Run the Pipeline TCP/IP Switcher program.
3. Click "Switch to using the original 32-bit Winsock." If the switch
is successful, you see the message "The original Winsock has now been installed."
If you receive an error message, Wsock32.dll is still in memory. Check
the task list to make sure no Winsock programs are listed. If Rnaapp is
listed, click Rnaapp and then click End Task. Then, try the Switcher program
again.
If the Pipeline TCP/IP Switcher program is not functioning properly,
you can manually switch the Wsock32.dll files by following these steps:
1. Rename the Wsock32.dll file in the Windows\System folder to Wsock32.old.
2. Rename the Wsock32.ms file in the Windows\System folder to Wsock32.dll.
When you try to connect to an online service in Money, you receive
the following error message before the modem dials:
MONEY
In Money 5.0: There was an unexpected error communicating with Online
Services. Please try your call again.
In Money 4.0: There was a problem with the file being received from
Online Services. Please call Online Services Customer Support.
This sometimes occurs if you are using the Windows 95 Direct Cable
Connection. If you receive this error after the modem dials, please see
the article Q148522 in the Microsoft Knowledge Base, which is titled, "Money:
Errors Downloading Bank Statement Information".This is due to the fact
that Money is trying to use Windows 95 Direct Cable Connection (DCC) to
make the online call instead of using your modem.
This can be fixed though, as follows:
In the Modem area of the Call Online Services section, select your
modem from the list of choices. Do not select any of the Parallel or Serial
Cable choices.
1. In Money 5.0, go to the Home Banking area, in Money 4.0 go to the
Online Services area.
2. In the Connect tab, click the Connect button. In Money 4.0 click
the Call button.
3. If you have never made a successful connection, you will be prompted
to change your PIN number. Change it, and then click OK.
4. The Call Online Services dialog appears. Click the Modem list and
select the choice that corresponds to your actual modem by clicking on
the name of the modem. Do not select a COM or Parallel port listing.
5. If you did not change your PIN in step 3, enter your PIN now and
click the Connect button.
If this does not resolve the problem, follow the steps in the section
below to remove the Direct Cable devices from Windows.
Direct Cable Connection is a feature of Windows 95 that allows two
computers to communicate via parallel or serial-port cables. It is part
of the Windows 95 Dial-Up Networking option.
The Windows 95 Control Panel Modems Properties sheet may only list
your actual Modem(s), while Money can list further "modem" choices, including
Parallel Cable On LPT1, Serial Cable On COM1, or Serial Cable On COM2.
It is normal for 32-bit communications programs using Windows 95 Telephony
Application Programming Interface (TAPI), like Money or HyperTerminal,
to list the various DCC options. Typically these programs will list Parallel
and Serial Cable choices along with your actual modems. Money 95, however,
requires you to select an actual modem for use with online banking.
To remove Direct Cable Devices From Windows
If you have selected the correct modem in the Money Call Online Services
dialog and you are still experiencing the error message, you may need to
remove Direct Cable from Windows 95. Use the following steps:
1. Click the Start button, point to Settings, and then click Control
Panel.
2. Double-click System, and then click the Device Manager tab.
3. In Device Manager, double-click Modems.
4. Click the serial or parallel cable device, and then click the Remove
button.
5. Click OK when warned about removing this device.
6. Repeat steps 4 and 5 for each cable device listed.
7. Click Close.
Microsoft has released the Dial-Up Networking 1.3 Upgrade.
The Dial-Up Networking 1.3 Upgrade (DUN 1.3) provides additional features for the Dial-Up Networking components that were first introduced in Windows 95. DUN 1.3 includes all of the features of the 1.2 and 1.2b releases, and all of the features of the earlier Integrated Services Digital Network (ISDN) 1.1 release. These features include support for internal ISDN adapters, multilink support for binding two ISDN channels, connection-time scripting to automate non-standard login connections, and Point-to-Point Tunneling protocol (PPTP) client support.
The following file is available for download from the Microsoft Software Library:
Get it at http://support.microsoft.com/support/kb/articles/q191/4/94.asp
Msdun13.exe (size: 2355976 bytes)
A separate utility (Dun128.exe) is available which will modify an MSDUN 1.3 installation to enable use of 128-bit encryption. This utility can be obtained from the web site below.
http://mssecure.www.conxion.com/cgi-bin/ntitar.pl
Go to Control Panel>> Add/Remove Programs>> Windows Setup and uncheck
the Dial-up Networking to remove it and OK your way out.
Go back and check Dial-up Networking and press OK ( you will need your
Win98 CD).
Finally make sure you uncheck the option "Connect Automaticlly" in
Control Panel>> Internet>> Connection>> Settings.
If you want the connection to be closed after a specific idle time,
go the same place as above and check "disconnect automaticlly after