 |
 |
Q:
What network interface does EnterNet require? or
Q: Does EnterNet
support USB attached ethernet or DSL adapters?
A: EnterNet for Windows 95/98 and NT 4.0 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 and the Microsoft TCP/IP protocol bound to the adapter. If so, you're ready to install EnterNet. If you haven't already installed your Ethernet Adapter, you must do this before installing EnterNet. The Microsoft TCP/IP protocol should also be bound to the Ethernet Adapter.
Q: Does EnterNet require Microsoft Dial-up Networking (DUN)?
A: 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.
However, if you wish to allow your Internet aware applications to use the Dial-On-Demand feature described in the EnterNet Help file, you will need to configure Dial-Up Networking.
In cases where you already have an application that uses the Microsoft DUN API and configuration parameters, ask about our EnterNet DUN product.
Q: Do I really need my Windows CD to install EnterNet?
A:Maybe. During installation of software that makes changes to Windows network properties (as does EnterNet), 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.
Q:Can I use Microsoft VPN with EnterNet?
A: Yes. In addition, EnterNet 500 nicely integrates VPN into EnterNet, so you no longer need two applications (EnterNet and MS VPN) to establish a VPN connection. Also, EnterNet 500 resolves some of Microsoft's routing problems. Your service provider may offer this option. Currently EnterNet 500 is not available for end-user purchase.
Q: Can EnterNet and TunnelBuilder co-exist on the same computer?
A: No. You must remove one before installing the other. To get the same effect that having EnterNet and TunnelBuilder provides, install EnterNet 500 which has all the features of both products.
Q: I get an error message when I try to connect. What's wrong?
A: 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.
| Unable
to Create Device NTSPPPoE03 (or)
NTSPPPoE19 |
This
was a problem with earlier (pre 1.34) versions of EnterNet. It still
occurs occasionally on Windows 2000 and rarely on Windows 95/98.
When this happens, you need to add
the NTSPPPoE adapter by hand.
You can also get this error if EnterNet was installed on NT without Administrator privileges. |
| Tap failed to load | Upgrading to the latest version will alleviate some cases of this error.
A bug in version 1.41 can sometimes cause this error It has been discovered that some PCI (white slots on the motherboard) based Ethernet adapters fail to identify to the PCI bus master. We recommend installing an ISA (black slots) Ethernet adapter to get around this problem. In some cases you may need to change to using the Protocol Driver |
| Server Communication
Failure (or)
Timeout while connecting to server |
Ethernet cable not connected
Network Server or service identified in Properties didnÕt respond to Discovery Request DSL modem or network connection is not working IP Addresses not exchanged from Server Driver has been disabled by Automatic Skip Driver Agent on Windows 98 |
| Authentication failed | User
Name or Password not entered correctly (check for case-sensitive)
User has selected the wrong server or service to connect with from the Profile -> Services tab. Server has been changed at the central office, and the user has saved the old server's name in the connection profile. If this happens, create a new connection profile. On version 1.5, EnterNet will detect this and prompt for a new configuration. Connection was made to the wrong service. Each Service has it's own user database to authenticate - choose the one that you subscribed with your ISP. Required Service was not selected, user broadcasted to first available server which had no record of your user name. |
| Connection Cancelled by User | Cancel button was hit during Connection establishment |
Q: EnterNet seems troublesome on my Windows NT4.x computer. Any suggestions?
A:Yes. First, you may be running an early version of EnterNet. A number of improvements have been made to EnterNet in version 1.34, which includes several improvements for Windows NT 4.x and Windows 2000 systems. Version 1.34 has been released to your service provider. If they haven't distributed it, you can obtain a 30 day trial from our website.
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:
Q: Does EnterNet 500's PPTP (VPN) shut down better than Microsoft's PPTP (VPN)?
A: Yes. The trouble is that Microsoft PPTP sometimes does not properly release the TCP connection with a TCP Reset. Sometimes a connection cannot be reestablished for several hours or even days (the 629 error).
EnterNet 500 issues a TermReq, the server responds with a TermAck, the server then terminates the TCP circuit with a Final bit, the client responds with the TCP reset bit. The server then knows that the TCP connection is free and available for incoming connections. All of this adds up to quick, dependable disconnects from your VPN server.
Q: Does EnterNet 500 support Server and Service Selection?
A: Yes. Check to make sure that the Protocol on the configuration tab is set to PPPoE. Otherwise the Service tab isn't displayed, and Server / Service Selection won't be possible.
Q: I've been using EnterNet on Windows 95 1st edition for some time, and it seems to have become unstable. Can I fix this?
A: Upgrading your Windows msdun13.exe will solve this problem. Upgrading the InterNet Explorer browser to 4.x will also help.
Q: Does EnterNet support multi-processor Windows NT systems?
A: The initial design of EnterNet did not support for Symetric Multi-Processing (SMP), or dual-processors. SMP support has been added in EnterNet v1.34 for Windows.
Q: Is EnterNet compatible with Microsoft Internet Connection Sharing (ICS in Win98 R2)?
A: 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.
- 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) P.P.P.o.E. 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.
Q: How do I configure multiple simultaneous PPPoE sessions?
A: Check out our Advanced Configuration page.
Q: Does EnterNet work with multiple Ethernet cards installed?
A: Yes. The 100 version allows you to select the adapter at install. The 300 and 500 versions allow you to select an Ethernet interface at any time or configure different profiles with different adapters.
Q: What about EnterNet PPTP and L2TP support?
A: EnterNet 500 for Windows shares PPTP and L2TP capabilities with the TunnelBuilder VPN client, see the TunnelBuilder FAQ for more information. EnterNet 500 is currently only available in bulk licenses. For now, Windows users should use the standard VPN clients supported by EnterNet for Windows.
There is no VPN software for the Mac that will run over PPPoE currently. However you can use TunnelBuilder for Mac over dialup if this required.
Q: Install SU Reg Create Key failed during Installation, or,
Q: Failed on Create Device: NTSPPP3
A: 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:
Q: EnterNet for Windows Release Notes
A: EnterNet for Windows Version 1.5 is the current supported release. It has been shipped to all our contracted customers. They may still be in their own testing phase or cutting cds for distribution. You should contact your ISP for this latest version: Efficient Networks is unable to distribute releases directly to end users.
Release Notes for EnterNet for Windows Version 1.41 is also available.
Q: Can EnterNet run as a restartable service on NT?
A: Beginning with version 1.3, EnterNet 300 and 500 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.
Error: This DHCP client was unable to obtain an IP network address
A: 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.
Q: The software you are about to install does not contain a Microsoft digital signature
A: This warning occurs when you install most software on Windows2000. EnterNet version 1.41a was enhanced to include our registered digital signature, so you will not see this error on later versions of EnterNet.
Q: Internet Explorer 5.x warns that the connection isn't available, Try again.
A: 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.34, 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:
Using your File Explorer, in the \Windows\System directory:
Rename the file loadwc.exe to DoNotloadwc.exe
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WebCheck
"LoadSens"="No"
"LoadLCE"="No"
Q: Trial version has expired, enter code to unlock
A: The evaluation software that you downloaded expires after 30 days. There is actually no passcode that will unlock it. You will be unable to run this software again, until you install a licensed version. Uninstalling and re-installing the evaluation will not get around this message, nor will changing the timestamp on your system.
Contact your service provider for the licensed product, or purchase it directly from our website. Try purchasing and downloading over an analog modem or from another computer, or contact your ISP for the version that they distribute. Please do not contact Efficient Networks for help, we cannot help you get internet access after your software expires.
Q: How do I disable File sharing and Print services from EnterNet? Is this a security risk?
A: 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 or DSL 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 packets that comprise the File sharing are normally discarded by your network routers. 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 that 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.
Q: How can I get to my office network using EnterNet?
A: Typically this is done using VPN software in connection with EnterNet. Our EnterNet for Windows supports most VPN clients, including Microsoft PPTP. A list of the VPN clients supported by EnterNet can be found here.
Q: What VPN (IPSec) clients are supported by EnterNet for Windows?
A: The list is below. When using VPN clients, follow these procedures:
| Company | Product | Version |
| Efficient Networks | EnterNet 500 (PPTP/L2TP client) | 1.5 |
| Intel/Shiva | Shiva VPN IPSec Client * | 6.7 |
| CheckPoint | VPN-1 SecuRemote IPSec | 4.0** |
| Nortel (Bay) | Contivity Extranet IPSec Client | 2.5 |
| TimeStep | PERMIT/Client IPSec | > 1.20.004 |
| Microsoft | PPTP/L2TP Adapter | 95/98/NT/2000 |
| Aventail | Aventail Connect | 3.21*** |
| VPNet | VPNremote | 3.026+ |
| Cisco / Altiga | VPN 3000 Client | 2.5.2++++ |
| Cisco/ IRE | IRE | unknown**** |
| AT&T | Global Network Dialer | 4.26.4++ |
| Lucent | IPSec client | 3.2.112+++ |
| VPN clients that are not supported: | ||
| Compatible Systems | Cisco 5000 | ( IPSec only) |
Efficient Networks has worked with some of the above VPN products to confirm their products are compatible with our Windows EnterNet 1.34 client or later. Several of these vendors updated their own software to resolve problems, so you may need to contact them for the latest version. In all cases, contact your VPN vendor for client support, Efficient Networks is unable to provide help for VPN clients..
* In order for the Intel Shiva client to work over EnterNet, change the Settings to Use DHCP. For further assistance, request help through your available Intel/Shiva support channels.
** SecuRemote requires 4.1 build 4118 to work with Windows 2000/NT. SecuRemote changed the interface in version 4150 and will require the 1.41 version of EnterNet.
*** Aventail requires EnterNet version 1.34. You will also need to exclude the EnterNet application from the Aventail client to prevent the EnterNet application from crashing. From the Aventail Advanced tab, click the Modify List button and add the Enternet.exe application to the list.
**** Cisco IRE requires EnterNet version 1.4. Change the Settings to Protocol Driver. Add the following 2 lines at the end of the Enternet.ini file:
[ExtraProtocols]
protocol1=DNEPRO
+ VPNet VPNRemote on Windows 2k. Change the Settings to Protocol Driver. Add the following 2 lines at the end of the Enternet.ini file:
[ExtraProtocols]
protocol1=VPNMINI
++ AT&T Global Network Dialer version 4.26.4 and later will work with EnterNet version 1.5 on NT and Windows 2000. The current version 5.0 of AT&T GND does not support EnterNet on Windows 95/98 platforms.
+++ Lucent IPSec Client version 3.2.112 or later will work on version 1.4 of EnterNet except for Windows 2000 and NT. For those platforms, install EnterNet version 1.5. Set the Settings to Protocol Driver, and add the following information in the EnterNet.ini file:
[ExtraProtocols]
protocol1=LUIPSEC
++++ Cisco 3000 VPN client version 3.0 and above is reported not to work with EnterNet. Contact Cisco for help.
The Efficient Networks EnterNet 500 client (1.3) offers an integrated PPTP/L2TP over Ethernet, dial-up, or PPPoE with multiple concurrent sessions - it may be used to simplify VPN access over broadband.
The integrated EnterNet 500 VPN client does not support IPSec and will not work with any IPSec servers, but will work with most PPTP/L2TP servers. You can however use the above listed IPSec clients over an Enternet 300 or 500 PPPoE session.
Q: How do I get Dial-on-Demand to work?
A: Dial-On-Demand is a feature that is normally disabled by default, although it is described in the Help file. It can be enabled by your ISP or by the user before installing. Most users that want this feature will be satisfied with the always-on feature by selecting these items from the Settings menu:
If your ISP chose to enable Dial-On-Demand, you will be prompted whether you would like to install it or not. If you choose to install it, you will notice an extra menu in the Start -> Programs > Enternet group, called Enable Dial-on-Demand. Click that icon to configure and follow the instructions in the help file and readme.
- Launch EnterNet 300 at Windows Startup
- Auto-Connect
- Persistent Connections
To enable Dial-On-Demand, you must edit the Setup.ini file BEFORE running the Install.
In the section under [CustomOptions], add this line:
InstallDoD=1
A description follows:
Default = 0 (false). If during install you want to provide the user the option to install EnterNet's Dial-on-Demand feature, set this value to 1 (true). The installer will present to the user a dialogue asking if the user would like to activate the DoD feature. If InstallDOD is true, and the user elects not to activate Dial-on-Demand at install time, the installer will place an item in the EnterNet Windows Start menu folder named 'Activate DoD'. The user may run this utility at a future time to activate DoD in accordance with instructions in the EnterNet Help file.Note: Dial-on-Demand does not work with Netscape Navigator and other IP applications on NT and doesn't work at all on Windows 2000.If 'InstallDOD' is true, and the user elects to activate Dial-on-Demand at install time, the 'Activate DoD' Start menu item will not be added.
This feature is unsupported and may not work with your version of browser.
Q: Does EnterNet coexist with Ivasion's MacPoet or WinPoet?
A: No. Uninstall the Ivasion software before installing EnterNet. The WinPoet or MacPoet drivers interfere with the Enternet software's ability to receive packets.
Q: Error: EnterNet does not recover from standby, sleep, or hibernate mode
A: There are several conditions that apply to these features:
Q: Does EnterNet support WinProxy, MSProxy, Wingate, Avirt or WinRoute proxy sharing?
A: 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, change the setting to use DHCP and 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).
Q:
Windows has detected an older version of EnterNet that is not supported
with Windows Me. or,
Q:
Does EnterNet support Windows Millenium (Windows ME)?
A: In all cases, you can avoid potential problems if you uninstall EnterNet (or your ISP's variant of EnterNet) before upgrading to Windows Me. After upgrading, you can reinstall EnterNet (or the ISP's variant) as long as it is version 1.4 or later.
When installing Windows Me, it will detect whether an older version of the NTS EnterNet software is installed. Unfortunately, the Microsoft Me installer was unaware that our EnterNet product is resold by many different service providers, who change the name of the product. Thus, the check will not detect if the product is installed with a different name than EnterNet.
EnterNet 300 version 1.4, currently shipping and available for purchase from our web-site, supports Millenium without any modifications. We do not offer free upgrades for users of previous versions, but you might try contacting your ISP for the latest version. We have supplied all our ISPs with version 1.4 on August 2nd, 2000.
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.4 or later.
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 Millenium, 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 change the Settings to use DHCP and 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, then hit F8 quickly. Choose the Safe Boot option. Then change the Settings.
EnterNet 100 will not support Windows Millenium.
Q: Installation issues on NT or Windows 2000
A: 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).
EnterNet supports all variants of Windows 2000 Professional, Server, and Advanced Server. EnterNet has been tested with service packs 1 and 2. Microsoft recommends that all Windows 2000 users upgrade to the latest service pack.
Q: I've tried everything, but nothing works! What should I do?
A: 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.
Your
local service provider (ISP) is busily staffing up to meet demand
for their customers, but in many cases they've been overwhelmed.
We wish we could do more, but for now this is all we can recommend:
Q: Does EnterNet work with the Novell Netware 3.2 client?
A: No. The Netware drivers are incompatible with EnterNet. The only workaround is to use the Microsoft Netware clients.
Q: How can I share my EnterNet connection with other systems at home?
A: EnterNet 1.34 supports Windows Internet Connection Sharing on Windows 98 Second Edition. Some users have been successful using any of several Proxy servers to share their enternet connection with other systems. Efficient Networks is unable to provide support with system sharing.
Error: EnterNet Connection is established but my browser won't connect to anything.
A: Verify the following:
Error: Server Communication Failure
A: In some cases on Windows98, and possibly WIndows2000, the Automatic Skip Driver Agent will detect a problem and disable either 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.
Error: EnterNet freezes or blue screens on NT shortly after authentication
A: 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 will be fixed in the 1.4 release. For a workaround, change the IP configuration from Private API to Use DHCP.
Error: NT continuously auto-connecting
A: 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 (greyed-out).
Error: Dialup adaptor not found in list.
A: Check your Control Panel -> Internet Options. Click the Connections tab. Click on the radial for "Never dial a connection".
Q: When I am connected I see a message with the current date and time followed by "- AdminMsg:"
A: 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 for informational purposes mainly, 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.
Q:
EnterNet version 1.4 freezes, GPFs, or blue-screens with Efficient 4060
DSL modems or
Q: EnterNet version
1.3 cannot list Efficient 4060 USB modems in Configuration
A: A regression was introduced in EnterNet 300 version 1.4 with the Filter driver that can cause errors when clicking Connect. A workaround is to change to the Protocol driver (From the EnterNet Profile folder, click Connections -> Settings -> Advanced Button). Restart the EnterNet application and the problem should go away.
A fix to the Filter driver has been released with version 1.41. This version is being sent to our service provider customers; you may contact them for an upgrade or purchase directly from our website.
Versions 1.3 of EnterNet were unable to locate the 4060 modems in the Configuration tab or Create New Profile wizard. If your Service provider has supplied you with an older version, contact them for an update.
Q: Performance issues with EnterNet
A: 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:
If you've tried everything and are still finding poor performance, check out other user's systems. You might have a service pack that needs updating, or downrev ethernet, USB, or DSL drivers.
The network might be slow for other users as well. Take measurements and compare with other users on your network.
Q: Memory consumption issues with EnterNet
A: 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 behaviour.
We suspect that most of these problems can be resolved by doing some of
the following memory enhancements on NT:
Q: NTS PPPoE adapters fail to load with EnterNet version 1.4 and 1.41 (Windows NT and 2000 only)
A: Occasionally we receive reports that EnterNet is not installing the adapter Windows NT or 2000. If this is the case, try overwrite the following inf files into the installer directory (this will only work with the zip file, not the self-expanding executable). Then reinstall EnterNet.
Q: Error 0051 - Failed to load Tap driver
A: 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. Change from the default Filter driver to the Protocol driver.
Q: Clicking the EnterNet icon displays only the top window bar or a very small display window
A: 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.
Q: How can I get the EnterNetFolder to stop launching every time I reload Windows NT?
A: Auto-launch is greyed out on NT because the feature is controlled from the PPPoE services. By default it loads at startup. If you wish to stop this behaviour, 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.
Click here for info on how
to have your EnterNet application connect automatically
at startup time.
Q: Why am I getting these 169.254.n.n IP addresses on my Ethernet adapter?
A: 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 DSL networks. This feature is enabled by default, but it can be disabled if not desired. You can disable it by editing the Registry.
In any effect, it should not cause problems with EnterNet. The ethernet adapter's TCP/IP address' metric is decremented in the routing table so that the negotiated address from your connection will take precedent.
Q: How do I get EnterNet to request Pap or Chap authentication?
A: 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 issue 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.
Q: How can I uninstall EnterNet?
A: There are three ways to remove EnterNet:
Q: I can connect on Windows 2000 but my browser won't work
A: There are a few problems related to Windows 2000 that can cause this problem. For that reason, there are a number of solutions that can resolve this problem. We recommend you follow them in this order:
IPProgramWait=45
Where 45 is the number of retries every second that EnterNet will attempt to program the negotiated IP address to the Windows 20000 TCP/IP component. Default is 30 retries. You can try any number between 1 and 60. Watch the detailed messages by right-clicking on the EnterNet icon in the system tray, and check for the recurring message "IP Address still is not Programmed" every second.
Q: Can I get EnterNet to connect automatically on NT/Win2000?
A: NT/Win2000 requires the user to launch EnterNet as a service. Click on the Control Panel -> Services to start the PPPoE Service manager. Then click on the EnterNet application, and select the EnterNet butterfly. Check the field for "Subservice loads when PPPoE Service starts". Then click OK to close.
From the EnterNet folder, click the Connections menu, then Settings. Check the Auto-connect field so that it will launch the default EnterNet profile at startup. The following illustrations show how to do this:
|
|
Error: P.P.P.o.E Adapter was disconnected from the network on Windows 2000 event log
A: This is an informational event from the Windows 2000 System event log. An entry will be made every time the connection is established and again when it's disconnected. Ignore it.
Error: The 'Language=' setting in the EnterNet.ini file is set to an invalid state
A: EnterNet supports a limited number of languages. Your service provider will normally define the default language for your service. You can change it by editing the EnterNet.ini file and setting it to your preferred language (ie: Language=ENU for English).
In rare cases, the installation was corrupted when the Resfolderenu.dll files were copied as Resfol~1.dll. Renaming this file should solve the problem, or uninstalling, deleting the EnterNet 300 directory and re-installing will also work.
Error: Blue Screen or hangs occurs when using Windows 98 Second Edition
A: Microsoft has issued a fix for their NDIS driver that on some occasions causes Blue Screens, freezes or hangs during startup or shutdown, or slow degrading performance. Information can be found from the Microsoft Knowledge Base article Q243199.
Q: Does Enternet support Windows XP (Whistler)?
A: EnterNet will not run on the current beta for Windows XP. We plan to support Windows XP in a future version.
Q: How can I get EnterNet to work with Windows Internet Security and Acceleration Server (ISA)?
A: There are some restrictions you'll need to know in order to use ISA over EnterNet:
1) If QoS packet scheduler is installed and configured, the PPPoE connection cannot be established. The QoS packet scheduler is one of the standard components built into Windows 2000, used for bandwidth adjustment. When ISA is installed on the system, this is also automatically enabled. You will need to disable the QOS scheduler before connecting with EnterNet.
2) An EnterNet connection cannot be established automatically using Dial on Demand. Dial on Demand is not supported on Windows2000. You will need to make the connection directly before using ISA.
Q: EnterNet slows down or hangs every 10 minutes for 45 seconds
A: In some cases, this is caused by the ethernet TCP/IP component sending out DHCP requests and failing to get a response. In order to work around this limitation of the Windows TCP, users have reported the following can be done to help: