Wingate 6.1.1 Demand-dial with multiple routes broken

[HenriLemmers]

Today I finally made the transition from 6.0.4 to 6.1.1. Most things went smooth. However, one automatic network connection now fails.

I run a AD/2003 server with internal adapter 10.2.1.2.
My (almost permanent) internet connection is a VPN-ADSL connection 80.60.x.x through my external adapter 10.0.0.150.
For my office connection I created a Demand-dial interface in RRAS for segment 10.1.x.x, so whenever, on my internal network, I try to connect to my work, the server automatically dialed the connection on ISDN.
This setup worked last year.

After the upgrade however, this autodial feature is broken. My workstation request is sent out over my internet connection in Wingate, and lost. If the line to work is open, the workstation request is handled corectly. From the server the IE-request does initiate the dialer (RRAS!) and works correctly.

Looking at the routing table on the server "route print" shows:
10.1.0.0 255.255.0.0 0.0.0.0 ffffffff 1 ;ISDN not connected

10.1.0.0 255.255.0.0 10.1.0.2 10.1.14.79 1 ;ISDN connected

At the same time Gatekeeper in Extended Networking-properties, routing does not show the 10.1.0.0 line at all when ISDN is not connected, and stays empty after connection is established (from the server). At this time the activity screen shows the correct forwarding from my workstation to the (DMZ-) office line.

Half an hour after disconnecting, the route print table correctly shows the disconnected state, however, Gatekeeper does include the line:
10.1.0.0 255.255.0.0 10.1.0.2 10.1.14.79 1
and Wingate sends my workstation requests out on the internet gateway interface.

I somehow think an update timing has been changed on the automatic interface detection, which I rather need.
If you like me to send further details, I will be glad to provide them.

[adrien]

Hi Henri

Racking my brains to think what may have changed in this regard.

I think WinGate will probably consider any route with an interface address of 0.0.0.0 and gateway address of 255.255.255.255 to be invalid, so the question is how did it work before.

All I can think is that WinGate driver must have been letting the packet up the stack so that RRAS could do the autodialing.

Do you have "support for multiple subnets" turned on in the ENS properties? You could try turning this off, which will then make WinGate let the OS do routing (but not NAT).

Adrien

[HenriLemmers]

Hi Adrien,

Thanks for your prompt response. Turning off support for multiple subnets indeed transferred control of automatic dialing to RRAS, so it seems to be working again.
I never knew I had turned it off in 6.0.4. In fact I thougt I always looked up the routing table in wingate also, whereas I can't do it now with sup. mult. subnets turned off. For now it is to troublesome to deinstall 6.1.1 and test the settings 0f 6.0.4.
It seems to be that indeed routing is not transferred to windows with support for multiple subnets enabled.

Anyhow for the moment my problem is solved, and my automatic conections are working again.

Thanks again,

[adrien]

Hi

It's probably something that changed in 6.1.1 or 6.1.0 - we did a few tweaks to the handling of multiple routes.

Now that I know about this type of route entry though, I can put specific support in for it, so that WinGate will always behave properly for these situations

Let me know if you run into any other problems

Regards

Adrien

[HenriLemmers]

Thanks, I will keep a watch on the next update.
Meanwhile I'm happy as it is right now, and will comment if I run into new problems.

Bye

[HenriLemmers]

Hi Adrien,

Unfortunately autodial is broken again. I may have had 1 or 2 reboots (for windows-updates) in between, but last week autodial stopped. Meanwhile I have tried rebooting with KAV-firewall both dis- and en-abled on startup, and with "support for multiple subnetworks" and "enable support for multiple default routes" on and off in different combinations, but am not able to get autodial working again.
In "services" "Remote access connection manager" is started (automatic), and "Remote access auto connection manager" is stopped (manual).
Looking up the specific site from IE on the server does initiate autodial.
I wonder if my aim is related to Kevin Goodknecht's, him persisting on using Windows 2000 NAT. (I only use the second route once every few weeks).

I hope to see your final solution soon.

[HenriLemmers]

Hi Adrien,

To keep you posted. The autodial is working again. It appeared that on my domain (and wingate) server the external adapter was listed first and my internal adpater second in order. (My Domain DNS was linked to the external adapter primarily). Switching the order linked my computername to the internal adapter, so lookup starts with my own DNS.

Thanks for your support.