http://www.weethet.nl/dutch/adsl_mxstream_winroute.htm
4.1.27 Pro
http://www.tinysoftware.com/manual/v4.0r/543.htm
Configuring WinRoute to authenticate through SMTP
This is a registry modification. First disable the WinRoute engine. From the start menu select run and type regedit from the command line. Proceed to HKEY_LOCAL_MACHINE -> SOFTWARE -> TinySoftware -> WinRoute. In the right hand window you will modify MailRelayAuth to "1". Then modify MailRelayUser (naam)and MailRelayPassword (password)to reflect your SMTP server's authentication information. Note that this only applies to build 25 or higher.
PPPoE DSL connection
PPPoE is a recently deployed technology for many DSL subscribers. Although it is being widely deployed by various ISPs it provides users with crippled performance and it is not (at present time) the-best-you-could-get solution for the connection of your network to the Internet. The customers should require the standard DSL solution whenever possible.
The deploying of PPPoE with WinRoute is similar to the standard DSL in terms of TCP/IP settings. WinRoute Pro should be installed on the same computer as the PPPoE adapter. WinRoute Pro will recognize the PPPoE adapter as a network interface. You should enable NAT on this interface. You will also see the ethernet adapter (plugged to the cable modem) as the interface in WinRoute Pro interface table. You should not enable NAT on that interface.
WinRoute Pro works well with all PPPoE adapters available on the market. However - time to time - customers may experience performance issues with certain PPPoE adapters:
Enternet 100, 300, 500 PPPoE client
WinRoute Pro 4.1 works well with the Enternet PPPoE client from NTS if you switched on Protocol Driver instead of default Filter Driver. To do that run Enternet PPPoE client, go to menu Settings->Advanced and change desired values.
If you would experience the issue on the performance you may also need to lower the MTU on the client machines to 800.
WinPoet from Ivasion
WinRoute Pro 4.1 works well with WinPoet under following circumstances: IP header compression (is RAS/Dial-up networking settings) is turned off.
Lowering the MTU:
The PPPoE adapter adds additional information to the header of every outgoing packet. By default, windows uses the maximum allowable packet size. The PPPoE adapter compensates for this by ensuring that the MTU of the local machine is slightly lowered to compensate for the addional information added to each packet. Unfortunately, all other machines still use the maximum size for transmission. This will result in packet loss. The following links will show you how to lower the MTU on all the clients.
For Windows 95/98 users:
http://www.microsoft.com/support/kb/articles/Q158/4/74.asp
(XS4all 1350)
For Windows NT4/2000 users:
http://www.microsoft.com/WINDOWS2000/library/resources/reskit/samplechapters/cnbd/cnbd_trb_vcfx.asp
http://www.tinysoftware.com/pppoe.php
Configuring WinRoute Pro/Lite with ADSL using PPPoE
Many DSL service providers offer a connection method for their service called PPP over Ethernet or PPP over ADSL. PPPoE combines the Point-to-Point Protocol (PPP), commonly used in dialup connections, with the Ethernet protocol. With PPPoE, the user must install special software that is used to announce the computers presence and to obtain an IP configuration. In the process, the software uses a virtual interface to encapsulate each ethernet frame with additional header information. Depending on the type of PPPoE software used, WinRoute may need to be adjusted to fragment data packets, or in some cases, you will need to lower the Maximum Transmission Unit (MTU) on each computer behind WinRoute.
(xs4all 1350)
Basic network setup for PPPoE:
IP Configuration: (For basic configuration with only two Ethernet adapters, though more may be used)
Assign an IP address and subnet mask to both ethernet adapters and nothing more, eg. no gateway/dns etc.
For example NIC1 may have an address like 192.168.10.1 mask 255.255.255.0
NIC2 may have an address like 192.168.20.1 mask 255.255.255.0
It is a common misconception that the interface connected to the ADSL modem should use DHCP. You must assign this adapter an IP address and mask and it must be in a different subnet than any other interface so that proper routing may take place.
NAT Configuration:
The PPPoE software supplied to you should install specific drivers as well as an additional interface. This interface is typically identified in WinRoute as either a virtual ethernet adapter or a RAS connection. You must enable NAT on only this interface. Note that NAT will be enabled by default for all RAS adapters. For WinRoute Lite users, if your PPPoE adapter is a RAS type you must specify dial-up as your connection type and select the corresponding PPPoE RAS connection from the drop down menu. If it is a virtual adapter you will specify a second network adapter and select the PPPoE adapter from the drop down menu.
PPPoE Configuration:
RASPPPOE by Robert Schlabbach and WinPoet from Fine Point Technologies
WinRoute works best with these known PPPoE software providers because they both use RAS interfaces to connect to the internet. Most users choose to set the connection to persistent dial for an "always on" connection. By using RAS, WinRoute may remain running as a system service and initiate the connection at start-up. You may notice an error WRSendPacket() failure in the error log. This can be fixed by allowing WinRoute to fragment incoming packets. Refer to our FAQ page for further explanation and instruction.
Enternet 300 by Efficient Networks
In the advanced connections/settings of the Enternet 300 you must enable protocol driver in place of filter driver. You must also connect to the internet and successfully receive your IP configuration before starting the WinRoute engine. This means that you must disable WinRoute as a service so that it will not launch the engine at startup. NAT must only be enabled on the NTS pppoe adapter. If you have WinRoute Lite this adapter should be specified as your 2nd network adapter.
WRSendPacket() failure
It is likely that you will find this message in the error log of WinRoute. Refer to our FAQ page for further explanation and instruction.
Setting The MTU
The Maximum Transmission Unit (MTU) is a value that defines the maximum size of each packet leaving your computer. You may need to lower this value on each computer behind WinRoute. To see if this is necessary you can perform a ping test from a client computer as follows.
From a dos window type: ping -f -l 1472 yahoo.com
If you receive the message: Packet needs to be fragmented but DF set. Then you need to lower the MTU. Try the same test again using 1400 in place of 1472. If you get a message like: Reply from 216.115.108.243: bytes=1400 time= 180ms TTL= 246.Then 1400 is a sufficient size. Otherwise you'll need to continue lowering the value until you get a reply. It is possible that you may not get a reply, this is ok. You only need to lower the MTU if you get the specific response "Packet needs to be fragmented but DF set." (XS4all 1350)
Note: If the client is set to obtain its IP information through DHCP, the registry structure may not appear as follows. To make sure you apply the necessary MTU value to the proper location you need to exit the registry editor and proceed to the TCP/IP settings of the adapter for which you are setting the MTU. Disable DHCP and manually input an IP address and subnet mask. Use a random value such as 1.2.3.4 that is easy to remember. Reboot the computer and refer back to the registry editor and follow the steps outlined below. Once you have set the MTU and rebooted you can go back to the TCP/IP properties and reset the adapter to obtain its IP information through DHCP.
Windows 95/98/ME
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Class\NetTrans\{000x}
Beneath NetTrans should be several keys labeled 000x. Select the first key and refer to the window to the right. Look for an IP address setting that will display the IP you inputed in the TCP/IP settings, 1.2.3.4 in our example. If you cannot find the IP then select the next key down and so on until you have located the IP address. When you have located the correct key look for a value called MaxMTU. If it does not exist, add a string value and label it MaxMTU taking into account case sensitivity. Modify its contents to reflect the necessary bit size determined by the ping test. Under most circumstances 1400 is sufficient. You must reboot the machine for the changes to take affect.
-----------------------------------------------------------------------------------------------------
Windows NT
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ethernet-adapter\Parameters\Tcpip
When you have located the correct key look for a value called MTU. If it does not exist, add a dword value and label it MTU taking into account case sensitivity. Modify its contents to reflect the necessary bit size determined by the ping test. Under most circumstances 1400 is sufficient. You must reboot the machine for the changes to take affect.
-----------------------------------------------------------------------------------------------------
Windows 2000
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{interface}
Beneath Interfaces should be several keys signifying each interface. Select the first key and refer to the window to the right. Look for an IP address setting that will display the IP you inputed in the TCP/IP settings, 1.2.3.4 in our example. If you cannot find the IP then select the next key down and so on until you have located the IP address. When you have located the correct key look for a value called MTU. If it does not exist, add a dword value and label it MTU taking into account case sensitivity. Modify its contents to reflect the necessary bit size determined by the ping test. Under most circumstances a decimal value of 1400 is sufficient. You must reboot the machine for the changes to take affect.
:strip_exif()/u/27224/tux.gif?f=community)
)
(ik vat et ff niet. want keb nix gedaan, maar goe)
working on it 
:strip_icc():strip_exif()/u/809/LegoSpaceMan_Icon_XS.jpg?f=community){kind=icon}