Phantom PPP adapter

[olaf.krause]

I'm using Windows 2003 Server with Wingate 5.0.8. If I activate ENS (load driver on startup) I very often get a "phantom ppp adapter" after a dial in session (to my ISP). That means it works for a while and at some time (latest after a few hours) an additional ppp adapter with IP address 0.0.0.0 is created (same name as the correct one). If this happens of course no traffic to the internet is possible.
If I deactivate ENS (not loading driver, only deactivate does not help) it seems to work fine (I tested it over 24h). Because I would like to use the firewall feature it would be fine if somebod could give me a hint how to solve this problem. I tried to find something via google but I only got some hits talking about Zonealarm (which sometimes seems to have the same problem).

Here my ipconfig /all in failure situation below also the good case:

Windows-IP-Konfiguration

Hostname . . . . . . . . . . . . : nostromo
Primäres DNS-Suffix . . . . . . . : research.ok-edv.de
Knotentyp . . . . . . . . . . . . : Unbekannt
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Ja
DNS-Suffixsuchliste . . . . . . . : research.ok-edv.de
ok-edv.de

Ethernet-Adapter LAN-Verbindung:

Verbindungsspezifisches DNS-Suffix:
Beschreibung . . . . . . . . . . : Intel 21143-basierter PCI-Fast Ethernet-
dapter (Standard)
Physikalische Adresse . . . . . . : 00-40-F6-CC-9E-7E
DHCP aktiviert . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 192.168.0.1
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . :
DNS-Server . . . . . . . . . . . : 192.168.0.1

PPP-Adapter Internet:

Verbindungsspezifisches DNS-Suffix:
Beschreibung . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physikalische Adresse . . . . . . : 00-53-45-00-00-00
DHCP aktiviert . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 0.0.0.0
Subnetzmaske . . . . . . . . . . : 0.0.0.0
Standardgateway . . . . . . . . . :

PPP-Adapter Internet:

Verbindungsspezifisches DNS-Suffix:
Beschreibung . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physikalische Adresse . . . . . . : 00-53-45-00-00-00
DHCP aktiviert . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 217.2.84.140
Subnetzmaske . . . . . . . . . . : 255.255.255.255
Standardgateway . . . . . . . . . : 0.0.0.0
DNS-Server . . . . . . . . . . . : 62.225.251.16
194.25.2.129
NetBIOS über TCP/IP . . . . . . . : Deaktiviert



If it works I have:
Windows-IP-Konfiguration

Hostname . . . . . . . . . . . . : nostromo
Primäres DNS-Suffix . . . . . . . : research.ok-edv.de
Knotentyp . . . . . . . . . . . . : Unbekannt
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Ja
DNS-Suffixsuchliste . . . . . . . : research.ok-edv.de
ok-edv.de

Ethernet-Adapter LAN-Verbindung:

Verbindungsspezifisches DNS-Suffix:
Beschreibung . . . . . . . . . . : Intel 21143-basierter PCI-Fast Ethernet-
dapter (Standard)
Physikalische Adresse . . . . . . : 00-40-F6-CC-9E-7E
DHCP aktiviert . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 192.168.0.1
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . :
DNS-Server . . . . . . . . . . . : 192.168.0.1

PPP-Adapter Internet:

Verbindungsspezifisches DNS-Suffix:
Beschreibung . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physikalische Adresse . . . . . . : 00-53-45-00-00-00
DHCP aktiviert . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 217.2.84.228
Subnetzmaske . . . . . . . . . . : 255.255.255.255
Standardgateway . . . . . . . . . : 0.0.0.0
DNS-Server . . . . . . . . . . . : 62.225.251.16
194.25.2.129
NetBIOS über TCP/IP . . . . . . . : Deaktiviert

[adrien]

Hi

We thought we had this issue under control before, and we tested for it here in the lab before releasing this latest version.. We will have another look.

Adrien

[olaf.krause]

Could your reproduce the error? I'm now 99% sure that it was caused by END because my server now runs stable since 4.10.2003.


Olaf

[olaf.krause]

thx for 5.0.9. At the moment it looks very good. Wingate is now running > 12h without creating any phantom adapters.

Olaf

[adrien]

yep, we definitely fixed the phantom adapters, however the fix didn't work as it should, and we broke outbound filtering on dialup adapters.

I have a fix for it, and we are readying our third release in as many days... this is getting ridiculous!!! at least we are nailing these problems though.

[olaf.krause]

Hi,

any ideas when the next (beta) with ENS fixes will be available. At the moment I have no version of wingate in which I could enable the firewall or NAT etc because of the "ghost adapter" problem.
OK - better you take another week or two for developing and regression tests to get a STABLE version out.

regards

Olaf