EnterNet for Windows 95/98, NT4.0 and Win 2000 consists of a 32-bit application (the EnterNet "Dialer") and an NDIS 3.0 compliant driver that supports the Windows operating systems.

EnterNet runs over any standard NDIS 3.0 or above compatible Ethernet or DSL Adapter, including USB attached adapters. The Ethernet Adapter is attached by cable to a Local Area Network (LAN). In general, if you're currently able to connect to other Windows systems via LAN, you have sufficient hardware to run EnterNet.

You may already have an Ethernet Adapter installed. If so, you're ready to install EnterNet. If you haven't already installed your Ethernet Adapter, you must do this before installing EnterNet.

Unlike other PPPoE clients, EnterNet does not require the Microsoft dialup (DUN) Adapter, DUN software upgrades, Winsock upgrades or other special Service Packs from Microsoft to accomplish basic connectivity. All you need is an Ethernet adapter, the standard Microsoft TCP/IP protocol, and you're ready to go.

Maybe. During installation of software that makes changes to Windows network properties, the Windows operating system wants to copy files from the Windows installation CD that may already be present on your hard drive. If during EnterNet installation you are prompted for your Windows CD and you don't have it handy, try pointing the installer to the directory where Windows is installed (Usually "Windows", "WIN98", or something similar). If the installer does not find the files there, try directing the installer to look in the "System" subdirectory of your Windows installation directory. You will probably need to bounce back and forth three or four times between these two directories before Windows finds all the files it is looking for.

If the above steps do not work you will need to provide your Windows CD.

Should any of the EnterNet drivers fail to load; the application will fail to connect. The table below shows some of the more common errors and their usual causes.

Yes. First, you may be running an early version of EnterNet. A number of improvements have been made to EnterNet in version 1.41, which includes several improvements for Windows NT 4.x and Windows 2000 systems. Please click on this link to download the latest version of the EnterNet software. In the mean time, here are a few tips to make EnterNet versions earlier than 1.102.006 run more smoothly on Windows NT 4.x systems:

• Assign a static IP configuration to the "real" NIC to prevent DHCP error messages.
• Start DHCP manually to prevent it from trying to get an IP address for the virtual EnterNet NTSPPPOE NIC at boot time.
• Login with administrator privileges.
• Please be sure you have version 1.102.006 or greater.

Upgrading your Windows msdun13.exe will solve this problem.

The initial design of EnterNet did not support for Symmetric Multi-Processing (SMP), or dual-processors. SMP support has been added in EnterNet v1.34 or higher for Windows. You may download version 1.41 from our website now.

Yes. You do this by installing EnterNet on the gateway system, and sharing the other systems as client machines. This normally requires 2 controllers - the first is the gateway to the Internet, and the second Ethernet controller shares access to the other systems.

1. Install the EnterNet 300 software (version 1.34 or later) on the Gateway system for the Internet access. Under Connections -> Settings, click the Advanced button. Under IP Configuration, change from the default "Private API" to "Use DHCP".
   
   
2. Add the Internet Connection Sharing (ICS) software on your gateway machine (the computer that will connect and share your Internet connection to the client systems (other computers).
   
   • You do this by clicking "Start -> settings -> control panel ->Add/Remove Programs".
   • Click "windows setup".
   • Under "components tab", double-click on the "internet tools" category.
   • Check the "Internet connection sharing" and click on "ok" to install. Note: You will need to go step by step through the Internet sharing setup until it asks the kind of connection. Choose the option for "cable or dsl".
   • Continue and it will prompt you for the device. Select the "Efficient Networks (or NTS) PPPoE. adapter".
   • You will then be prompted to make a setup disk for the client machines. This is not always necessary to share the connection.
   • You will be asked to restart the Gateway system.
     
3. If desired, install the setup disk on the client machines. Make sure they have an Ethernet adapter with a TCP/IP protocol and are configured for DHCP (not static) addressing.
   
   
4. On the gateway system, start a connection and then use the ICS application on the client machines. You will be updated with new private addresses, by the gateway system. At this point you should be connected.

Yes. The EnterNet 300 version allows you to select an Ethernet interface at any time or configure different profiles with different adapters.

In some cases during Installation on NT and Windows 2000, and rare cases on Windows 95/98 systems, an application will fail to bind the NTS PPPoE adapter into the Network Properties. When this error occurs, you will need to add the adapter by hand. Follow this procedure:

• Click Start ->Settings -> Control Panel -> Networks
• From the Configuration Tab, click Add -> Adapter
• Select Manufacturers = Network TeleSystems -> Network TeleSystems PPPoE Adapter (NTSP3)
• Click OK, wait for completion, then reboot.

If you are using Windows 2000, the Add Adapter dialog has been moved to the Add/Remove Hardware icon in the Control Panel Settings.

EnterNet for Windows Version 1.41 has been released. You can download the latest version of the software here.

Beginning with version 1.3, EnterNet 300 can be configured as a restartable service on NT. Follow the instructions in the Help to configure this from the Control Panel. Be aware that logging into NT Domains over a PPPoE session normally requires a VPN connection to the NT network.

This is an error message from the Microsoft DHCP component, mainly on Windows95 and 98 systems when a DHCP server is not present. To get around this error, either click No to "Do you want to see future messages?" or else configure manually a private address to the TCP/IP protocol over the Ethernet adapter, such as 192.192.192.2 with a subnet mask of 255.255.255.0. Do NOT assign a Gateway address to the Ethernet adapter; it will prevent the connection from routing correctly.

This warning occurs when you install most software on Windows2000. EnterNet version 1.41 was enhanced to include our registered digital signature, so you will not see this error on later versions of EnterNet.

Clicking on the Try again button will solve this problem until you close the Explorer. This error does not occur with other browsers. This warning is from the Internet Explorer 5.0's sensing of the auto-connect feature not having tested with all types of connection-based software.

 

When this warning occurs, make sure you have installed at least version 1.41, which includes an enhancement to work around the warning. Also, make sure that the Control Panel -> Internet Options -> Connections tab is set to "Never dial a connection".

 

In some cases, this may not be enough. Users have reported two methods for getting around this error:

• Some users have found that you can alleviate this warning by disabling the Loadwc.exe file. Be aware that this file may be required by other applications. We are including this unsupported workaround for users to try. Use this workaround at your own risk: Using your File Explorer, in the \Windows\System directory:
  Rename the file loadwc.exe to DoNotloadwc.exe
  
• Using your Regedit, change the following entries from "Yes" or "Auto" to "No": HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WebCheck
  "LoadSens"="No"
  "LoadLCE"="No"

Be aware that other problems may occur from other Microsoft files requiring this file. In that case, you may need to return it to its original name.

Many users express surprise to find that the File and Print sharing for Microsoft Networks component becomes enabled when adding the EnterNet software. This is actually enabled by Windows when the Ethernet adapter is added. When EnterNet is installed, these services will also bind over the EnterNet adapter (as they will over any adapter).

 

This is usually not as serious a security risk as one would think, since the NetBIOS and SMB your network routers normally discard packets that comprise the File sharing. They are a concern for performance reasons, and if possible should be removed for that reason. How to do this?

 

From your Control Panel -> Networks, verify the service "File and Printer Sharing for Microsoft Networks" is not configured. If it is, remove it. If you require this service (for sharing over a second Ethernet card), Select the TCP/IP -> Network TeleSystems. PPPoE Adapter, click Properties, and uncheck any services in the Bindings tab.

 

For Windows98 systems, you may want to consider replacing the "Client for Microsoft Networks" with the "Windows Family Login" client. This will prevent unnecessary broadcasts over the Ethernet card.

Packet Logging is a new feature added into EnterNet 300 version 1.4. From the Profiles folder, click Connections -> Settings (you can also do this by right-clicking the EnterNet icon from the system tray, then click Applications Settings). Check the checkboxes for detailed logging and Packet Log.

 

When you restart the EnterNet application and click Connect, a warning message will be displayed that the connection will be slower due to the logging. After capturing the problem, right click the EnterNet icon in the system tray. Click the Advanced menu. Then click File -> Save Report, save the file to your desktop, and send the file, with your problem description, to your Service Provider.

Typically this is done using VPN software in connection with EnterNet. Our EnterNet for Windows supports most VPN clients, including Microsoft PPTP.

No. Uninstall the Ivasion software before installing EnterNet. The WinPoet or MacPoet drivers interfere with the Enternet software's ability to receive packets.

There are several conditions that apply to these features:

• You should normally avoid using hibernate mode while your system is connected. The problem is that the PPPoE protocol requires the EnterNet driver to respond to echo heartbeat packets every minute. Starting with version 1.4, a warning will be posted that EnterNet will disconnect and exit before going into sleep mode.
  
• With Windows 2000, hibernate mode was not supported before version 1.4.
  
• Persistent connection support, from the Advanced Settings menu on EnterNet 300, is not very persistent. EnterNet 300 will retry the connection a few times after the server disconnects, and then report the connection was dropped.
  
• Persistent connection support is not available in EnterNet 100 or EnterNet for Mac OS.
  
• EnterNet uses the SNMP component to update changes to the TCP/IP. There is a known bug in Microsoft's SNMP related to standby mode which could cause delays after reawakening. This is described in the MS Knowledge Base article Q152569. Although the article doesn't mention it, the same behavior has also been seen on Millennium and Windows2000.

Internet-sharing software such as WinProxy, Avirt, Microsoft Proxy, WinRoute, Sygate and WinGate should work fine with EnterNet. Sharing is usually done with two Ethernet cards, the first one being your internet connection (using EnterNet), and the second providing the routing to your private network.

We are unable to provide support for these products, but try setting them up with EnterNet running on the gateway Ethernet card.

If it fails to work in default mode, try setting the Connection-> Application Settings -> Advanced button to use DHCP, for IP Configuration, and/or Network Access using the Protocol Driver.

You will also have more success if you lower the MRU size for the adapter (Network Properties -> Select NTS PPPoE adapter. Click the Advanced tab, and change the MaxFramesize to 1300 or lower).

If you experience memory crashes after several hours of activity, try increasing your virtual memory on the NT. Also try setting it up as a desktop and not a file server. (Virtual memory settings).

When installing Windows Me, it will detect whether an older version of the NTS EnterNet software is installed.

EnterNet 300 version 1.4, currently from our web site, supports Millennium without any modifications. You can download ver. 1.41 here.

We always recommend uninstalling EnterNet before installing or upgrading any Operating System (be sure you know your username and password before doing this). After verifying that all hardware and networking devices are functioning correctly, install EnterNet version 1.41.

Another bug in the Microsoft Me installer has been detected when upgrading EnterNet from version 1.34 to version 1.4, where Windows will mistakenly think that an older version of EnterNet is still installed even after upgrading EnterNet to version 1.4. That information can be found in the following registry location using REGEDIT:

HKEY_LOCAL_MACHINE\Software\NTS\EnterNet 300

Delete any keys that are older than 1.40 and this will avoid the Windows Install warning.

EnterNet 300, version 1.34, will run on Windows Millennium, but you will need to remove the NTS PPPoE adapter before upgrading the Operating System and re-install it after the OS upgrade is complete. You will also need to use the Settings -> Advanced button to change the default IP Configuration from Private API to use DHCP, and change the Network Access method from Filter to use the Protocol Driver. If you do not make this change, you can get a blue screen when you reboot. To get out of this blue screen, reboot, wait for the Starting Windows 9x message, and then hit F8 quickly. Choose the Safe Boot option. Then change the Settings.

When installing on NT or Win2000, you need to have Administrator capability to bind the drivers to the network properties or to change the Service properties from the Control panel. The installer will normally check for this and report it's unable to install until you login with an Administrator privilege. After installation is complete, you can log on with normal access. The Installer will also check on NT 4.0 to verify that the adequate service pack is installed (service pack 3 is minimum).

We understand! Networking software often brings surprises. Since EnterNet adds the icon prominently on your desktop, it's natural to assume that we're the cause of all your problems. But networking is seldom that easy.

1. If it doesn't work, try to identify the exact error message or behavior.
   
2. READ the FAQs one more time, very closely!.
   
3. Try upgrading to a the newest version of the EnterNet software (ver 1.41)
   
4. Try changing the Connections -> Settings -> Advanced to use DHCP and the Protocol Driver if the default fails.
   
5. Contact Mycybernet. Please do not try to contact Efficient Networks. In most cases, we've never seen our customers' networks or routers; often they've modified our software for their own specific network requirements.
   Still doesn't work? Here's the last resort to try, in the following order:
   
6. Be sure to uninstall the EnterNet software completely and re-boot before re-installing.
   
7. Try eliminating any non-essential networking software (but be sure to leave at least one Ethernet adapter and TCP/IP protocol).
   
8. Try eliminating any non-essential applications that start automatically from your System Tray. Disable Antiviruses, personal web or firewall services, network utilities, etc. Use the MS Information tool to stop apps from loading automatically.
   
9. If the system is unable to restart, or freezes after installing EnterNet, try rebooting using the safe mode. For NT, try booting from the last known working system (hit space bar). Remove the Efficient Networks PPPoE adapter from the Control Panel -> Network Properties, then reboot and do a full uninstall before re-installing.
   
10. Install an ISA (black slots on motherboard) Ethernet controller. They're cheap, and they have a better statitistical chance of working with most systems than the PCI (white slots on motherboard) controllers.
    
11. Next to last resort (This has been known to resolve cases where a Microsoft DLL or Vxd was corrupted)
    
    
    • Remove all Networking drivers (be sure to have your Windows CD-ROM and network adapter disks before doing this!) from your Control Panel Network Properties.
    • Re-add the Ethernet adapters, TCP/IP protocol, and Windows Clients.
    • Verify that the Ethernet TCP stack is functional (adapter diagnostics, Winipcfg, etc.).
    • On NT, save the Hardware Profile from your Control Panel-> System properties.
    • On Windows98, save the configuration using the Accessories-> System Information -> Configuration tool.
    • Re-install (the latest version you can get of) EnterNet, reboot, and try again.
      
12. If it still doesn't work, the final resort is to uninstall EnterNet and re-install Windows. This should save your current system configuration. You should not have to re-format your disk. In almost every case, this has been enough to get most systems working. Always contact Mycybernet when you're having problems.

No. The Netware drivers are incompatible with EnterNet. The only workaround is to use the Microsoft Netware clients.

EnterNet 1.41 supports Windows Internet Connection Sharing on Windows 98 Second Edition. Some users have been successful using any of several the Proxy servers to share their EnterNet connection with other systems. Mycybernet is unable to provide support with system sharing.

Verify the following:

• From the System tray, right click the Advanced menu. From the Diagnostics tab, verify that the DNS addresses are green (accessible using PING). If not, contact your service provider.
• You can ping a system by entering it's DNS name or IP Address in the field by typing over the name "Network" and clicking the Test button. If you can ping IP Addresses but not names, then your DNS server isn't working.
• In some cases you may need to change the EnterNet IP Configuration. Click Connections -> Settings -> Advanced button. Change from the default Private API setting to DHCP. Restart the connection.
• You can also manually enter the DNS server addresses in the EnterNet software

In some cases on Windows98, and possibly WIndows2000, the Automatic Skip Driver Agent will detect a problem and disable the Ethernet Adapter, the NTS PPPoE Adapter, or both. Use the agent to enable the drivers by clicking Start -> Programs -> Accessories -> System Tools -> System Information. Then click the Tools Menu to bring up the Automatic Skip Driver utility. If it displays the adapters as disabled, re-enable them and reboot.

return to top of page

Error: EnterNet freezes or blue screens on NT shortly after authentication

In rare cases on Windows NT and 2000, EnterNet will freeze shortly after the connection is established. This is due to a problem updating the TCP/IP stack with the new addresses. This is fixed in the 1.41 release. For a workaround, start your EnterNet folder; click the Connections -> Settings menu, then the Advanced button. Change the IP configuration from Private API to Use DHCP.

In pre 1.4 versions, selecting the auto-connect from the settings panel would cause this problem. Auto-connect is supported differently on Windows NT/2000. The PPPoE service can be configured via the Control Panel to auto-connect. In 1.4, the auto-connect option is disabled (grayed-out).

Check your Control Panel -> Internet Options. Click the Connections tab. Click on the radial for "Never dial a connection".

This is a visual error only, which has been fixed in version 1.41. They are related to the Message of the Moment (MOTM) data sent by the server. It is not a source of memory "leaks" as some users have assumed. The Messages tab is mainly for informational purposes, and will report errors occasionally but they can be ignored, as the EnterNet software normally works around them. If a substantive error occurs, you will be notified by an error Popup message window.

A fix to the Filter driver has been released with version 1.41. You can download the latest version of the EnterNet software from the Mycybernet website

If you have an older version of the software please contact Mycybernet to receive the latest version.

If you're experiencing slow performance with EnterNet, it usually has nothing to do with the EnterNet application by itself. Some things can affect performance:

• From EnterNet Connections -> Settings menu, ensure that Detailed and Packet logging checkboxes are cleared.
• From EnterNet Connections -> Settings menu, click the Advanced button. Make sure it's set for "Use Private API"
• From Control panel -> Internet Options menu, Connections tab, click LAN settings, verify that all proxy-related checkboxes are cleared. Be sure to clear the default setting for auto-proxy detection, it will add an extra 15 seconds with each connection after a reboot.
• Dial-on-Demand can slow performance with frequent connections. Make sure the Internet Options Connections tab is set to Never Dial a connection.

If you've tried everything and are still finding poor performance, check out other user's systems. You might have a service pack, driver or software that needs updating.

Occasionally we receive reports that EnterNet is suspected of memory consumption that over time causes the application to crash. This is usually related to Windows NT or 2000. We have not been able to reproduce this behavior. We suspect that most of these problems can be resolved by doing some of the following memory enhancements on NT:

• Turn off all packet logging and detailed logging within EnterNet.
• Change the NT/W2k memory settings from a Network Server based model to a Desktop based model. This changes the caching allocation considerably.
• Increase the Virtual Memory available for the system.
• Run the Performance monitors and watch the memory allocation for the different processes and see if the problem is caused by something else.
• As a rule, upgrade to the latest version of EnterNet when doing any testing.

Some users have occasionally run into this problem when installing the EnterNet 300 version 1.41. When this happens, click on the EnterNet desktop icon to bring up the Profiles application. Click on Connections -> Settings, followed by the Advanced button. Change from the default Filter driver to the Protocol driver.

Restart the EnterNet application and the problem should go away. The Protocol driver setting is optimal for most users.

This bug was fixed in the Filter driver in version 1.41.

You can also try to re-install the EnterNet software to correct the problem if changing the protocol driver didn't work.

In rare cases where the resolution has changed, the window positioning for the EnterNet applications can become corrupted. When this happens, close the EnterNet applications, and search for the file called "Enternet.ini". Edit the file, and delete the following sections and the lines immediately underneath them:
[MainWindow Size]
[Window Size]
Save the file and restart the EnterNet application. It should revert to the default window size. You can also try to reinstall the EnterNet software to resolve the issue.

Auto-launch is grayed out on NT because the feature is controlled from the PPPoE services. By default it loads at startup. If you wish to change this behavior, from the Control Panel, click PPPoE services. Click both the icons and make sure that the Subservice loads checkbox is cleared. It doesn't always catch so verify by closing and re-opening the PPPoE services after changing them.

This is a feature that Windows 98 and later supports, called IPAutoconfiguration. It is a feature of the Microsoft TCP/IP protocol that allows it to assign a private address when no DHCP server is available, which is common with PPPoE networks.

In any effect, it should not cause problems with EnterNet. The Ethernet adapter's TCP/IP address is decremented in the routing table so that the negotiated address from your connection will take precedent.

There is no configuration for the client to determine the authentication method. This is the responsibility of the server. Whichever method the server requests, EnterNet will accept. This is normally issued when the server is passing off requests to a RADIUS server, which usually requires PAP authentication. If the BRAS server is set for CHAP, EnterNet will accept CHAP and not negotiate down for PAP. If this is an issue, consult the server vendor on how to configure the correct authentication method.

NO, Windows XP has it's own built in PPPoE drivers which are compatible with the Mycybernet Highspeed service.

You can simply uninstall the EnterNet software using the uninstall wizard under the EnterNet menu in the programs menu. If during the un-installation it asks if you want to remove shared files. It is important that you say "NO". Otherwise this may cause connection problems when trying to create a new PPPoE dialup connection.

You can create a new PPPoE connection incase the old one is corrupted, also disable the Windows connection firewall which is enabled by default during the creation of a PPPoE connection.