4005 Error (SpeedStream 3060 and 4060 only)
Cause: Modem drivers not installed properly, or corrupt registry entries.
See the SpeedStream 3060 or 4060 page for driver removal and re-install instructions.
Be sure to run the Enclean utility after removal and before reboot.

5002 Error: Manufacturing Block Verification Failed (SpeedStream 3060)
Cause: This error indicates a bad EPROM, and a replacement PCI Modem card may be required.
Try modem card in another PCI slot. It must be a Bus Mastering slot.
If this does not resolve this problem, modem will need to be replaced.

5004 Error (external modem)
Cause: Unknown
A complete reinstall of the networking components fixes it. It's also possible the modem is overheating.
Let the modem cool off, and make sure it's well ventilated around it.

5004 SAR Error (internal 3060 modem)
Cause: Eprom failure on the board.
Reseating the PCI card and re-installing the drivers for it will fix it but the error will return on the next boot.
Internal modem must be replaced with an external.

5006 Error (SpeedStream 3060)
Cause: a bad PCI modem or PCI Slot
Try modem card in another PCI slot. It must be a Bus Mastering slot.
If this does not resolve this problem, modem will need to be replaced.

A connection to the Internet is not available... Work Offline / Try Again
Cause: An incorrect default registry setting and/or bug in IE5.x
Fix #1
1 Edit the following key value...
2 HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WebCheck
3 Change the LoadLCE and the LoadSens values from "yes" to "auto"
4 The computer must be rebooted for the changes to take effect.
If these values get changed back by themselves after a reboot, then check the Run key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
If you find an entry called "loadwc", delete it and reboot again.
Fix #2
Upgrade to IE5.01 or later, which already has the change incorporated.  http://www.microsoft.com/windows/ie
Fix #3
Run the IE5 repair tool and reboot.
Fix #4
Rename the three files associated with System Event Notification Service.
These files are named Sens.dll, Sensapi.dll, and Senscfg.dll and must be renamed in DOS.
1 Reboot in DOS mode, and change to C:\Windows\System
2 Rename all three files (ie: sensdll.old, etc.)
2 Type exit to reboot

Adapter not available in list  (Windows NT)
Cause: The software on the MindSpring 4.0 CD-ROM has truncated the OEMNADNTSPPPOE.INF file.
Download Enternet 100 from http://download.mindspring.com/maxdsl
An alternative would be to copy the PPPoE folder to the harddrive and rename the file.

DHCP errors in Windows NT
Cause: NT may be looking for a DHCP server at bootup
Open Control Panel - Services, and highlight DCHP Client
Click on the Startup button and change Startup Type to Manual or Disabled.
A better alternative would be to use EnterNet 100 v1.31 as NT DHCP problems were corrected in this version.

Error starting program, the enternetfolder.exe is linked to missing export MFC42.dll 6597
Cause: Unknown
Removing and re-installing the Enternet 100 software will fix it.

Failed to load TAP
Cause: NTS PPPoE adapter not installed in Network Control Panel.
1 Open the Network Control Panel and click on Add, then Adapter, then Add again.
2 Choose Network TeleSystems for the Manufacturer.
3 Choose the Network TeleSystems P.P.P.o.E. Adapter (NTSP3).
4 Make sure NTS PPPoE Adapter is bound to TCP/IP and click OK
5 It will copy files from the Windows CD. Reboot when prompted.
If customer still gets this error when trying to connect, uninstall and reinstall EnterNet 100.
(on a Windows 95 computer using the Internal 3060 modem, hardcoding the IP and Subnet may also work).

Microsoft Dial-up Networking is either not installed on this computer or is not configured properly, Ethernet Dial-up Demand will be disabled.
Dial-on-Demand is not required for the EnterNet 100 software to function. It is safe to ignore this message.
If a customer wants to enable Dial-on-Demand, consult the Tips and Tricks page for the correct method to enable it.

Failed on Create Device NTSPPP3 or NTS Failed to Create NTSPPPOE3 or Unable to Create Device PPP3
Cause: NTS PPPoE adapter not installed in Network Control Panel
1 Open the Network Control Panel and click on Add, then Adapter, then Add again.
2 Choose Network TeleSystems for the Manufacturer
3 Choose the Network TeleSystems P.P.P.o.E. Adapter (NTSP3).
4 Make sure NTS PPPoE Adapter is bound to TCP/IP and click OK
5 It will copy files from the Windows CD. Reboot when prompted.
If user still gets this error when trying to connect, uninstall and reinstall EnterNet 100.

Failed on Create Device NTSPPPOE5 (Windows NT)
Cause: Multiple NTS PPPoE adapters listed in Network Control Panel
Remove the extra adapters, reboot and try again.
Complete removal and re-install of EnterNet 100 will be required if the above does not correct the error.

Failed on Create Device NTSPPPOE19 (Windows NT)
Cause: Occurs when the user currently logged on does not have administrator rights.
Upgrade to EnterNet v1.31. This version will install as a service, thus allowing all users access to the DSL connection.

PPP Establish Failed
Cause: Unknown
Remove and re-install the EnterNet 100 software.

PPPoE Server not responding  (Mac)
1 Check cable connections and check for sync.
2 Make sure AppleTalk is active and set to Ethernet.
3 Make sure EnterNet 100 is set to connect via Ethernet
4 Make sure TCP/IP is set to connect via EnterNet
5 Use the OT Tool and ping the NIC and router
6 Remove and reinstall EnterNet 100
7 May also be due to user not being on correct circuit - Contact ISP if above steps do not help.

rmdr.iq Not Found
Cause: Error is caused by some HP OfficeJet drivers, known to occur with the OfficeJet 600.
Removing and re-installing the HP drivers (Add/Remove in Control Panel) should fix it.

Server Communication Error
Cause: TCP/IP is not bound to the NTS PPPoE Adapter
Open Network Control Panel and add TCP/IP -> Network TeleSystems PPPoE Adapter (NTSPPP3)

Tap Driver is not ready, status:1. Unable to complete the connection.
Cause: NTS PPPoE adapter not installed in Network Control Panel
1 Open the Network Control Panel and click on Add, then Adapter, then Add again.
2 Choose Network TeleSystems for the Manufacturer
3 Choose the Network TeleSystems P.P.P.o.E. Adapter (NTSP3).
4 Make sure NTS PPPoE Adapter is bound to TCP/IP and click OK
5 It will copy files from the Windows CD. Reboot when prompted.
If user still gets this error when trying to connect, uninstall and reinstall EnterNet 100.
(on a Windows 95 computer, hardcoding the IP and Subnet may also work).

TAP driver not loaded
Cause: Multiple NICs are installed and the wrong one is selected for use in the EnterNet 100 software.
Check the Properties of the connectoid in the Enternet 100 software.
1 On the menu, click on View - Details to see an Explorer style dialog box.
2 One of the columns is called Adapter Name, see which adapter is selected.
3 Change the properties to select the correct NIC.

This DHCP client was unable to obtain an IP network address (Windows 95/98)
Cause: DHCP Server is not present.
To get around this error, either click No to "Do you want to see future messages?" or hard code the appropriate IP and Subnet in the TCP/IP settings of the Ethernet adapter. IP and Subnet settings are found on the individual modem/router pages.

The Ordinal 6907 Could Not Be Located in File Mfc42.dll  (Windows NT)
Upgrade to Service Pack 4, 5, or 6a. Do not use Service Pack 6 or anything earlier than SP4.

When Running DHCP Server, System Requires Static IP For Adapter  (Windows NT)
Disable the DHCP server in Control Panel - Services
Can also try upgrading to EnterNet 100 v1.31 as this release corrected some DHCP problems in NT 
 

 
2 NIC's Installed
This can cause a variety of errors from not being able to open PPPoE or connect. The PPPoE software will use the default NIC. The default NIC is determined by (the first card listed in the registry or the lowest MAC Address). Try disabling the second NIC. (You need to restart to do this). If this still does not work uninstall the second NIC and cancel the hardware install on reboot. Users that have installed a NIC while using the internal modem have hosed the entire software pack. It is not our responsibility to help a customer configure a network. If we can get it working without a NIC, that is all we need.

Autodial connectoid is missing in Dial-Up Networking
See the Tips and Tricks page for information on this feature and how to create the connection.

Computer Locks Up After Connecting and Opening a TCP/IP Application
Check the IP Address of the Speedstream or the NIC. Specify one if there is not one already.
(Use the appropriate NIC IP and Subnet Mask for whichever router they are using)

Driver not loaded (from Speedstream Status icon in the Systray)
Cause: Adapters have lost the bindings
Remove and re-install the modem drivers.

DSL Transmitting but Not Receiving
VPI numbers may be wrong, escalate to Tier II.

Enternet 100 or 300 does not work on mutilple processor machines
Customers need to be using WinPoet v2.0 if they have a multiple processor machine.
SMP support will be included in EnterNet 100 v1.34 

Throughput stalls for a minute, then goes back to normal
Cause #1 - IE or Netscape is looking for a proxy and not finding one.
In IE, go to Tools - Internet Options - Connection tab
Click the LAN Settings button...all checkboxes should be unchecked
Verify these are unchecked for any dial-up connections as well.
Do this if they are using Netscape too and also verify that proxy is not enabled in Netscape.

Cause #2 - Computer is looking for a DHCP server and not finding one.
Win9x:
Hard code the appropriate IP and Subnet Mask into the TCP/IP properties of the NIC. Disable WINS and DNS. Add the router's IP address to the Installed Gateways. You will find the IP's and Subnet on the router pages.
Windows NT4:
Go to Control Panel->Services. Find the DHCP Client and disable it.

Slow Throughput
1 In some cases, deprovisioning and re-provisioning will fix it.
2 Overclocking, if done incorrectly, can cause a slowdown in throughput. Turning down the PCI bus multiplier from 1/3 to 1/4 has fixed this.
3 Incorrect MaxMTU and RcvWindow settings.
4 Using a RJ-11 cable in a RJ-45 jack.

Internal Modem and NIC Conflict in Windows 98SE
If user has Windows 98SE with NIC installed and can connect, but no throughput.
Go to the Device Manager, remove the NIC driver and restart. When the wizard asks to find the drivers cancel through, (we are not installing the NIC driver at this time). Try to connect and check for throughput. If so, then customer can't use the NIC.
No known fix yet. The reason this needs to be done is that the NTS software is using the lowest Mac Address as an adapter even though it asks you which adapter to connect with.

Packet Loss (severe)
Check MTU and RcvWindow settings. RcvWindow may be set too high.

PPPoE hangs on Beginning Negotiation with Timeout Error Window
Check for sync. Check for proper cables and connections.
Uninstall, reboot, reinstall, and reboot again. Make sure the user's cross-connect has been built and is set for correct ISP's circuit.

PPPoE Hangs While Adding the Adapter to System
Disable any Norton products. Remove the TCP/IP stack, reboot, and readd TCP/IP stack for the PPPoE adapter.
Verify that the PPPoE adapter exists using winipcfg or ipconfig.

PPPoE Timeout  (Mac)
Enable AppleTalk. Select Ethernet for Connect via in AppleTalk.

PPPoE listed as "Not Responding" under Close Programs
Go into the Network Control Panel and remove TCP/IP for the NTS adaptor and the other adaptors. This may cause the NTS PPPoE Adaptor to be removed also, but that is fine. Reinstall TCP/IP and then reinstall the NTS PPPoE adaptor. Click on Add>Adaptors>NTS> then highlight the adaptor on the right.

Stuffit Does Not Recognize Software Archive
Install Stuffit 5.0 from the MindSpring CD.

Timeouts and trouble staying connected (win95a and win95b only)
Download the DUN1.3 Upgrade from Microsoft home page. http://download.microsoft.com/msdownload/msdun/patch/1.3ug/en/MSDUN13.EXE