Question : Setting up Winroute

I'm wanting to share a dial-up internet connection from a server running Win2000 Pro (ip 192.168.0.10) with a Win2000 PC (ip 192.168.0.11) and Win98 PC (ip 192.168.0.12). I'm aware of ICS but had problems getting that working too, and Winroute has other useful features.

Some of the settings I have tampered with are:
Network properties -  IP address and Default Gateway
IE 6 - Tools - Internet Options - Connections - Settings and LAN settings

I would like to use the static IP addresses listed above rather than use DHCP to dynamically assign, and I want the server to dial on demand.

I did get the Win98 PC sharing the server connection and it auto-dialed ok, but I failed to get the browser on the server itself to connect.  I then read that it is not necessary to use the proxy in Winroute but use NAT instead., but when I disabled the proxy it did not dial on demand.

I've read a number of articles on the net, rather than supply more url's could someone give me an overview of how I should set it up and then help with some specific questions please.

Answer : Setting up Winroute

I used to use winroute all the time untill I reciently switched to IPCop (www.ipcop.org). I used it on broadband though and haven't used it on dialup in years. When I did use it on dialup I had a dedicated phone line and just left it connected 24/7.

Here is something I found in the FAQ at www.kerio.com


Why won't WinRoute dial on demand?
One possible reason is that there is a default gateway already in place. If you perform the route print function from a command window you should not see a default route for destination network 0.0.0.0. If you type route, the command window will show you how to remove a route. Note that dial-on-demand does not work from the winroute host computer unless the TCP/IP properties are pointing to the localhost as the DNS server and winroute's DNS forwarder is enabled. Also note that in this scenario it is imperative that you do NOT select the first option to forward all queries to the DNS servers known to the operating system, as this will cause an infinite loop of DNS requests. If you have installed Microsoft's DNS server, winroute's dial-on-demand feature will only work if the IP to host resolution is cached, otherwise the request will be discarded by the TCP/IP stack because there is no gateway for which to forward the packet. One easy work around the demand dial issue is to create a favorite link in all client browsers pointing to http://winroute:3129 where "winroute" is actually specified by the local IP address or netbios name of the winroute machine. This will bring up an interface where the user can control the dial up connection. This feature is nice because the user can also disconnect the RAS connection.


I think basicly what it's saying is that you probably already have a default gateway on your router so it's trying to send to that instead of dialing a new connection. Check your network properties for a default gateway and remove it if it's there.


You're right about not using the proxy feature. I always disabled that feature. But, I did (do still) always use DHCP. You can set it to always give the same IP's to each computer and it makes it alot easier if you add another computer to the network. I don't know if that will help the dial-on-demand issue though.