 |
 |
Q: What network interface does EnterNet require?
or
Q: Does EnterNet support USB attached ethernet or DSL adapters?
A: EnterNet for Windows 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 must also be bound to the Ethernet Adapter.
Multiple Ethernet adapters are not a problem with EnterNet. Just select the required adapter in the profile properties and make your connection.
Q: Does EnterNet require Microsoft Dial-up Networking (DUN)?
A: Unlike other PPPoE clients, EnterNet does not require the Microsoft Dialup Networking (DUN) , 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.
DUN is required for Tango Access, our next-generation PPPoE client for Windows.
Q: Do I really need my Windows CD to install EnterNet?
A: Only rarely. During the 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.
Starting with version 1.4, support was added by EnterNet to copy the required files automatically without having to place the cd. But occasionally an unusual system configuration will still require the cd.
Q:Can I use Microsoft VPN with EnterNet?
A: Yes.
Q: Does EnterNet support multi-processor Windows NT & 2000 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: Multiple PPPoE sessions are not supported by EnterNet. They are supported in Tango Access.
Error: Install SU Reg Create Key failed during
Installation, or,
Error: Failed on Create Device: NTSPPP3 or NTSPPP19 (E0041)
Description: This error message occurs when the PPPoE adapter is not present in the Windows Networking adapters. It can happen if it was not properly installed or accidentally deleted by the user. This was a problem with earlier (pre 1.34) versions of EnterNet.
Possible Resolutions:
Q: What is the latest released version
of EnterNet?
Q: EnterNet for Windows Release Notes
A: EnterNet is no longer actively supported by Siemens Subscriber Networks. It was end-of-lifed in 2003 and replaced by our Tango Access client. If you are experiencing difficulties with EnterNet, we recommend uninstalling EnterNet and replacing with Tango Access.
EnterNet for Windows Version 1.5c Service Pack 2 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: Siemens Subscriber Networks is unable to distribute releases directly to end users.
Warning: You are about to install hardware that has not passed Windows Logo testing
A: This warning occurs sometimes when you install non-Microsoft networking software on Windows2000 or XP. EnterNet version 1.41a was enhanced to include our registered digital signature, so you will not see this warning on later versions of EnterNet with Windows 2000.
You will see this warning when installing EnterNet on Windows XP, sometimes multiple times during the Install. You should ignore the warning and click Continue Anyway to install the adapter. EnterNet has been carefully tested to support XP and will not destabilize your system.
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 three methods for getting around this error:
Create a registry key \\HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences
Add a Dword parameter of ForceOnline
Set ForceOnline = 0x00000001 (1)
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WebCheck
"LoadSens"="No"
"LoadLCE"="No"
Using your File Explorer, in the \Windows\System directory:
Rename the file loadwc.exe to DoNotloadwc.exe
Be aware that other problems may occur from other Microsoft files requiring this file. In that case, you may need to return it to it's original name.
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 Siemens Subscriber 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 |
| 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: | ||
| Symantec | Raptor Mobile | 6.5.3^ |
| Compatible Systems | Cisco 5000 | ( IPSec only) |
Siemens Subscriber 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, Siemens Subscriber 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
++ Enternet 300 v1.5b will work with the AT&T Global Network Client v5.04.1 and later on all Windows operating systems. Change the Settings to Protocol Driver and to use DHCP. Add the following information in the EnterNet.ini file:
[ExtraProtocols]
protocol1=ABVPNP95
protocol2=ABVPN98Transport
+++ 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. Change 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.
^ Raptor Mobile does not support PPPoE connections. See the Raptor Readme file for details.
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
Description: 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).
Q: Does EnterNet support Windows XP or Windows 2003 Server?
A: EnterNet version 1.5c will support Windows XP and Windows 2003 Server. It has been shipped to all our ISP customers with active support contracts. Contact your ISP if you need this, or you may purchase it from our website.
Windows XP also includes their own broadband dialup (PPPoE) support in the dialup networking components. Read the XP Dialup networking Help for further details.
When installing Windows XP, it will detect whether an older version of the NTS EnterNet software is installed. Unfortunately, the Microsoft XP installer was unaware that our EnterNet product is resold by many different service providers, who change the name of the product. Thus, the check may not detect if our product was installed with a different name than EnterNet.
We always recommend uninstalling Enternet before installing or upgrading any Operating System (be sure you know your username and password before doing this).
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.
EnterNet is no longer provided or supported actively by Siemens. 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. Siemens Subscriber Networks is unable to provide support with system sharing.
Error: Dialup adapter not found in list.
Description: The Windows Internet options is misconfigured to use the Dialup Networking component.
Possible Resolution: Check your Control Panel -> Internet Options. Click the Connections tab. Click on the radial for "Never dial a connection".
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:
The network might be slow for other users as well. Take measurements and compare with other users on your network.
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: Starting with version 1.5, the client can request either Pap or Chap authentication. In the EnterNet.ini file, under the section [Configuration], add the following line:
Q: How can I uninstall EnterNet?
(or)
Error: Uninstall log has become corrupt
Description: Information for the EnterNet uninstall is stored in the Registry and Program files.
Resolution: There are three ways to remove EnterNet:
If an error occurs on uninstall, you won't be able to remove EnterNet again. If this problem occurs, you will need to edit the Registry:
Error: I can connect with EnterNet for Windows but my browser won't work
Description: Connection completes successfully but browser is unable to reach any servers. Verify using the Connection Details that an IP and DNS address is set for the EnterNet connection.
Possible Resolution: There are a few problems related to all Windows Operating systems 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:
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
Description: 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.
Possible Resolution: Ignore it.
Error: The 'Language=' setting in the EnterNet.ini file is set to an invalid state
Description: EnterNet offers a limited number of languages, depending on the version your service provider has purchased. Your service provider will normally distribute the localized language of EnterNet for your country. You normally cannot change the language default to support a different language. EnterNet is available for single purchase from our webstore only in English.
Possible Resolutions: 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
Possible Resolution: 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: 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: What is the EnterNet encryption checkbox for?
A: This checkbox will cause EnterNet to request the Microsoft Point to Point Encryption for a 40-bit encrypted session over PPPoE. It will only work if the Network server supports encryption over PPPoE. We currently do not know of any servers that support this feature. Do not select this checkbox unless instructed by your ISP.
Q: What is the Logon to the Network checkbox for?
A: This checkbox will cause EnterNet to logon to an NT Domain server after the PPPoE session is established. For this to work, you need to have a valid WINS server address, as well as the means to establish a connection before logging in.
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:
Q: Changing the Advanced Settings to "Use DHCP" does not work on Windows NT
A: On Windows NT, the Siemens Subscriber Networks PPPoE Adapter TCP component is assigned a private static IP address, in order to hide the long delays when a DHCP server isn't present on the network. When the ethernet adapter is also configured as a static IP address, be sure to use the default Advanced Setting of "Use Private API" for IP address setting. If you change it to Use DHCP, the connection will work but the address will not take effect. This is only an issue with Windows NT; we do not assign static addresses for the PPPoE adapter on Windows 2000 and Win9x platforms.
In most cases, Private API is almost always the best way to configure an address with EnterNet.
Error: Cannot find gateway or other "errors" from Messages tab
Description: EnterNet has many internal informational errors and warnings that are displayed in the Messages tab and Status area of the EnterNet application. These events are a result of processing the connection with the Microsoft TCP interface. The Messages tab is for development and ISP support use only.
Some of these messages were inadvertently displayed in the Status tab and caused undue concern with users. Starting with version 1.5, these messages were moved into the Detailed logging only, which means the user normally will not see these messages unless the Settings -> Detailed log checkbox is enabled. You should not enable Detailed logging unless specifically requested by your service provider.
The "Cannot find gateway" warning was returned by the Windows 98 and earlier TCP protocols and was apparently fixed in later versions of the Windows OS. There is no need to be concerned when this error is returned - EnterNet will work around the error.
An explanation of the internal messages breakdown is as follows.
Possible Resolution: Ignore these internal messages unless told to collect them by your service provider.
Error: Server Communication Failure (E0043P) (or)
Timeout While Connecting to Server
(E0040P)
Description: You will receive this error when the PPPoE negotiation fails. It can occur if the DSL line is down or disconnected, if the network isn't responding, hardware errors, or misconfiguration of the EnterNet client.
Possible Resolution:
If this error occurs go Profile Properties->Services->hit Refresh. If no server or services appear, your DSL line is down or there is a problem communicating with the server.
Error: Tap failed to load (E0051)
Description: The "tap driver" is an intermediate NDIS driver. EnterNet uses this driver to communicate with the Microsoft Networking stack. This error message generally occurs when internal networking conflicts arise.
Possible Resolution:
Description: the client is able to reach the server, but cannot validate the users credentials.
Possible Resolution:
Error: Connection Cancelled by User
Description: If the user hits the Cancel button during the logon process this message will appear.
Possible Resolution: Do not hit the cancel button during the logon process.
Description: The new version of MediaPlayer causes some problems that only affects Windows 98 operating systems. There are two methods for working around this problem. It is not a problem with Windows Me or Windows 2000.
[CustomOptions]
WebCheck98=1
[Configuration]
WcDisable=1
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WebCheck
"LoadSens"="No"
"LoadLCE"="No"
Search for the file c:\Windows\System\LOADWC.EXE and rename it to DONOTLOADWC.EXE. This file is not necessary when using EnterNet for the connection.
A: All the known errors that EnterNet for Windows returns are described in this FAQ. Often we get requests for the full list of errors that EnterNet provides because they think it will help solve problems quicker. The quickest way to resolve problems with EnterNet is to follow the directions in the Troubleshooting EnterNet section and file a report with your service provider.
Q: After changing the icon, the old icon still shows up on the desktop
A: When an ISP wishes to change the app.ico for branding, they need to be aware that the Windows desktop is cached to allow for faster access. Therefore on systems that have been previously installed, the old icon will still show up on the desktop after installing. To clean the cache, you need to delete the IconCache.db file in the User's desktop settings group for NT, W2k and XP, or the ShellIconCache file in the Windows directory for Win9x and Me systems. Search for the file if you're unsure of the location. Then reboot. A new install should show the new icon.
Q: The installer reports "Before you can use EnterNet, you must have an ethernet adapter with TCP/IP binding"
A: This is occasionally found on systems that have been installed a few times. In some cases the ethernet adapter is installed with a valid TCP binding, but the installer mistakenly doesn't find it. The warning is informational only and can be ignored in this case. EnterNet will find it after the Install is completed and the system restarted.
Q: SNMP Vulnerabilities in EnterNet
A: There are no additional SNMP-related services or agents built into the EnterNet software. Your system will not become vulnerable to SNMP attacks simply by installing EnterNet. Since EnterNet does provide access to the internet, you should take precautions to secure your system from any SNMP-related actions that may be enabled either by your network hardware, internet-sharing programs, or Operating System. Click here for more information on SNMP vulnerabilies.
Q: Setting up EnterNet to install a specific autoconnection at windows launch
A: Some of our service provider customers wanted EnterNet to install for autoconnect with the desktop icon used to represent the specific user's profile, not the general EnterNet folder application. To do this, edit the following files in the EnterNet installer:
Setup.INI: [CustomOptions] StartNTfolderOff=0 AskDesktopIcon=0 DesktopIconFolder=0 DesktopIconProfile=1 AskNameAndPassword=1 DefaultProfileName=Your ISP connection StartWithWindows=1 EnterNet.ini: [Configuration] AutoConnect=1 LaunchOnStartup=1
A: The Tapbind.vxd was unable to locate an NDIS 3 compliant Ethernet or DSL adapter. Verify that the adapter is installed correctly. If so, try uninstalling and reinstalling EnterNet. If the problem continues, then uninstall your copy of EnterNet and download and install the latest version.
Error: Profile wizard did not find any with a TCP stack configured (E0083)
A: EnterNet requires the Microsoft TCP protocol to be bound to both the ethernet or DSL adapter and the Efficient Networks PPPoE adapter. Verify this by viewing the properties of your Network Adapters from the Control Panel. If a TCP protocol is actually bound to the adapter, then uninstall your copy of EnterNet and download and install the latest version.
Error: The Session no longer exists (I0065)
A: This usually occurs when a profile for a previous connection was copied to the desktop, but was deleted from the EnterNet Folder. Delete the Desktop icon, and copy over a new profile from the EnterNet Folder to your desktop.
Q: How do I change the password in the EnterNet.ini file when it's encrypted?
A: The password can be initially entered for the profile in the EnterNet.ini file as regular text. When an unencrypted password is read from the ini file, EnterNet will use it to make the connection and then store it in encrypted form, with a control byte as the first character.
Q: Setup was unable to initialize the uninstallation log
A: This error is reported from the InstallShield software, which EnterNet uses during the installation phase. It usually means that InstallShield is unable to create the temporary files required for it's environment. To fix this problem, you will need to find the location of your temporary files. From a Dos prompt (Start -> Run -> CMD) type SET. Then look for the value assigned to the TEMP parameter. Using Windows Explorer, go to the Temp folder and delete as many of the files and subfolders as you can. This should allow the Setup program to continue.
If you still find files in the \Program Files\Efficient Networks\EnterNet folder, delete this folder and all files in it. Then reinstall.
Q: A note to users of SBC Yahoo DSL service
A: Southwestern Bell Corporation includes an older version of our EnterNet product with their Yahoo installation software, version 1.5b. It does not support Windows XP, Windows 2003 server, or some other new Windows features, like MSN Mail.
Additionally, some users have discovered crashes after upgrading to XP or Windows 2000.
Siemens no longer provides support for EnterNet to any users. However we do provide tango Access (EnterNet's replacement) on our webstore for both evaluation and single-license purchase.
Users should be aware that SBC does not support later versions of EnterNet. Nevertheless, SBC users inform us that they have found the newer versions of EnterNet and tango Access to resolve most of the problems they run into with the SBC Yahoo installer. If you upgrade to XP, you will need to uninstall EnterNet and install Tango Access in order to connect with SBC.
A: EnterNet will not support some of the newer features of Microsoft's MSN network, such as accessing MSN mail and the MSN Address book, as well as the Mail sync feature. If you run into difficulties using MSN Mail, this feature is supported in our tango Access and tango Manager products, which replaces EnterNet with more full-featured network support.
Q: Does EnterNet support the McAfee Firewall?
A: EnterNet and Access Manager may crash (or blue-screen) on Windows 2000 and XP systems that have the McAfee firewall installed, particularly when you display the Profile Properties, or attempt to create a new profile. EnterNet does not support the McAfee Firewall.
To get around this, you will either need to use the firewall feature in XP or some other vendor's firewall software. EnterNet has been tested successfully with firewalls from Norton Internet Security, Black Ice, Zone alarms, Trend-Micro, etc.
Another option is to install Tango Access for Windows, which replaces EnterNet and Access Manager. Contact your Service Provider to see if they can provide you with Tango Access. You can also download an evaluation copy or purchase it from our webstore.