CYBERNET HOME ABOUT MYCYBERNET CLIENT LOGIN CONTACT US
Cybernet Main Page
Cybernet Personal Service
Cybernet Business Service
Reseller Plans
Cybernet Webmail Access
Cybernet Postini Centre
My Account
 
 
 

 

 

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 300 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 Millenium and Windows2000.

 

 

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).

 

 

Check that your IP configuration is valid and consistent with that which was provided by your ISP. A general guideline of IP configuration is available on this web site for both Windows computers and Apple computers.

If your IP configuration is correct, ensure that your network card is operating properly. With Windows 95 select Start... Settings... Control Panels. From there, double-click on the System icon. In the window that appears, click on the Device Manager tab at the top and find Network adapters in the list of devices. If there is an "X" or "!" next to it, then the device is not operating properly. Check your installation of the drivers specific to your network card. You may need to contact the manufacturer for help in determining the problem.

If you are still having difficulty, contact SwitchWorks Support in determining the problem.

 

 

This message is the result of an incomplete install of the Enternet 300, usually because the Windows CD was unavailable. To remedy the situation, the failed install needs to be removed and the software needs to be reinstalled

Use the Enternet 300 uninstall program to uninstall. To access it:

  1. Click Start

  2. Select Settings

  3. Select Control Panel

  4. Double click the Add/Remove Programs icon

  5. Select the Enternet 3000 uninstall program from the list

  6. Click Add/Remove to complete uninstallation

If the Enternet 300 uninstall program in not available, manually remove the system files as follows:
Delete the Enternet 200 directory
Delete the Enternet 300.inf from Windows\inf directory
Delete the Program Files\Nts directory

Manually remove the PPPoE HSE adapter:

  1. Click Start

  2. Select Settings

  3. Select Control Panel

  4. Double-click on the Network icon

  5. Select the PPPoE HSE adapter

  6. Click Remove

You can now safely reinstall the software from the CD-ROM

 

 

Server Communication Failure In some cases on Windows 95/98/ME, 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.

 

 

This is an error message from the Microsoft DHCP component, mainly on Windows95 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.

 

 

Dial-On-Demand is a feature that is disabled by default in version 1.31 and later of EnterNet 300 , 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:

Launch EnterNet 300 at Windows Startup
Auto-Connect
Persistent Connections

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.

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 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 "Installed" 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.

If Installed is true, and the user elects to activate Dial-on-Demand at install time, the "Activate DoD" Start menu item will not be added.

Note: Dial-on-Demand does not work with Netscape Navigator. This feature is unsupported and may not work with your version of browser.

 

 

This warning occurs when you install most software on Windows2000. Ignore it. EnterNet is awaiting testing by Microsoft labs. It is safe and tested by anti-virus software.

 

 

By default, Enternet 300 is configured to launch your default browser automatically. This behaviour can be modified.

  1. Launch Enternet 300

  2. Click the File menu

  3. Select Preferences

  4. Uncheck the Launch Mycybernet after Connection option

  5. Save and close the dialog

 

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.

 

 

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.

 

 

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, start your EnterNet folder, click the Connections -> Settings menu, then the Advanced button. Change the IP configuration from Private API to Use DHCP.

 

 

If you are having difficulty opening certain websites while using Windows NT, your Maximum Transfer Unit or default information packet size may be too large. All data transmission across the internet is done by transferring packets of information from computer to computer. Some network routers prevent the transfer of packets they feel might be overly large due to virus infection. If this is a problem, you will need to reduce the default packet size that is leaving your machine. To do so, follow these steps in Windows NT:

  • Click the start button

  • Choose RUN

  • Enter regedt32 in the command line and click ok

  • The registry editor will open

  • In the registry directory structure on the left, locate and expand HKEY_LOCAL_MACHINE and then expand through the following path:

    SYSTEM\CurrentControlSet\Services\NTSPPPoE6\Parameters\Tcpip
    Note: the entry for the NTSPPPoE section may vary depending on the version of the Highspeed software installed. The latest will appear as NTSPPPoE6

  • Once you have selected the tcpip key, click EDIT from the menus at the top of the window.

  • Choose ADD VALUE

  • Enter the value name as MTU

  • Select REG_DWORD for Data Type

  • Click OK

  • On the next screen enter 1400 in the DATA section, and under RADIX select the decimal option

  • Click OK to save and close the Regedit32 window

  • Restart your computer

Websites you previously had difficulty with should now be accessible.

 

 


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:

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

 

 

You may have the Ethernet adapter still set to DHCP and while your ISP has shut off DHCP service. If so, you will not be served an address and the OS will wait during boot. Setting your Ethernet adapter to a non-routable IP address may speed up the boot process.

 

 

In rare cases during Installation 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:

  1. Click Start ->Settings -> Control Panel -> Networks

  2. From the Configuration Tab, click Add -> Adapter

  3. Select Manufacturers = Network TeleSystems -> Network TeleSystems PPPoE Adapter (NTSP3)

  4. Click OK, wait for completion, then reboot.

 

Make sure you have at least version 1.102. Also check to verify that there are no multiple directories of Program Files\NTS\Enternet xxx. If found, remove, uninstall and re-install EnterNet.

 

 

What to do:

  1. Click On Start > Setting > Control Panel

  2. Double click on Network >

  3. You should have the TCP/IP Ethernet card PPPoe Adapter >

  4. Select the TCP/IP Ethernet PPPoE Adapter and click on "Properties"

  5. Click On the IP Adress TAP

  6. Put a dot in front of "Specify an IP Adress"

  7. Type in the IP adress 10.0.0.1

  8. Click on OK


If that doesn't work, you will need to re-install the Enternet software.

 

 

The SMS server is the local telco router that you connect to. Having the name of this server is useful to the technical support team to provide assistance in troubleshooting your connection problems.

  1. Right click on the profile that you use to connect to the highspeed service.

  2. Select on "Properties".

  3. A new window should open up with 5 tabs on the top.

  4. Click on the tab called "Services".

  5. In there, you will see 3 boxes.

  6. The first two boxes are "Server" and "Service". These boxes should be empty.

  7. The third box is called "Services". This box contains the name of the router that you are connected to.

  8. If you have a connection to an SMS Server, you should see in the box something like "13041039918263-SMS1-Ottawa23".

  9. If you do not see anything in the 'Services' box, just click on the button 'Refresh' button at the bottom of that page.

If after completeing these steps you still don't have or see an SMS server, it may be related to a misconfiguration in the program. To make sure everything is configured properly, just follow the steps listed here that relate to your operating system.

 

 
 

 

CYBERNET HOME ABOUT MYCYBERNET CLIENT LOGIN CONTACT US

 

The MyCybernet website is operated by SwitchWorks Technologies Inc.