Cable Modem issues with wingate

[tmpease↑↓]

I have a working dialup configuration with wingate 5.2.3.

I added a network card to connect to my cablemodem. It uses DHCP to acquire an IP address.

The cablemodem interface is being acknowledged (listed in the bindings/interface tabs of services) by wingate, but wingate will not use the interfaces when connecting. (Even with the modems disabled -- they seem to get precedence when they're on)

The cablemodem does work locally when the wingate engine is disabled.

Help!

Thank you for your time.
--Tim

[adrien↑↓]

Hi

If you want to use multiple connections to the Internet, then you should take a look at WinGate 6

It handles multiple connections in a different way, allowing selection of a gateway and interface to use for a service, rather than just an interface. This method also bypasses the OS's routing, which often gives one connection priority, thereby allowing much better control of what services use which Internet connections.

Adrien

[tmpease↑↓]

After installing Wingate 6.0.2, I set up a web proxy with the gateway set to "priority" and listed only the cablemodem's explicit gateway ( IP address '...1' ).

The gatekeeper shows the request being made, but then the connection hangs. The NIC's connection status shows very little traffic, as much as if there were no wingate connections.

On the gatekeeper "Network" Tab, the "Network Connections" area shows the status of "Local Area Connection 2" as "unknown". What does this mean?

Are there any other indicators that I can use to troubleshoot this problem?


Thank you for your time,
--Tim

[tmpease↑↓]

This is the chain of events:

After reboot: -- ipconfig shows cablemodem interface initialized properly; wingate lists interface properly
windows-2000 connection status (connection status window) : connected
wingate connection status (gatekeeper network tab): unknown

After disabling the interface: (from the windows 2000 connection status window)
windows 2000 connection status (in the network and dialup connections window): disabled
wingate connection status: disabled

*** After enabling the interface: (from the network and dialup connections window)
windows 2000 connection status: connected
wingate connection status: disconnected

After a minute or so, its back to:
windows-2000 connection status: connected
wingate connection status: unknown


Also...
Reboot without wingate: interface works with local webbrowser, ipconfig /release/renew works
Reboot with wingate: interface does not work with local webbrowser (what IS wingate doing), ipconfig /release/renew fails ("DHCP server unreachable")


Does this indicate a hardware, software, or combined problem??

Thank you for your time,
--Tim

[Pascal↑↓]

Basically, this sounds as if WinGate is detecting this adapter as external and then firewalling it. (Correctly ... as it's your internet connection)

Do you see any corresponding hits on the WinGate Firewall tab?

[tmpease↑↓]

I have ENS disabled, so nothing shows on the Firewall tab.[/quote]

[tmpease↑↓]

Another cablemodem test (mainly DNS tests):

Boot with no wingate:
ipconfig/route table/etc. normal
ping ipaddress works
ping hostname works
webpage loads at full speed

Start wingate engine:
ipconfig/route table/etc. normal
ping ipaddress works
ping hostname fails "unknown host" -- nslookup reports DNS requests timing out
webpage does not load

Stop wingate engine:
ipconfig/route table/etc. normal
ping ipaddress works
ping hostname fails "unknown host" nslookup reports DNS request times out
webpage does not load

Note:wingate DNS settings include the cablemodem DHCP-set DNS servers.


What's happening here? Is wingate squashing the local DNS?


Hope this sheds some light on the problem(s).
--Tim