Ghost adapters under Wingate 5.x.x

[absalomedia]

I've installed a server with 5.0.1, checked it all legimately that all DNS / DHCP data was correct, updated it to 5.1 and for some reason, it held a ghost adapter from a network segment it wasn't even connected to (without my knowledge, being a ghost adapter and all). The client then found the rogue Ghost adapter as the bound interface for their network. This would explain why it took nearly a month to find the ongoing issue with the network.

Has the Ghost adapter bug finally been fixed in 5.2, since I've just been subjected to it in 5.1 ?

After all, the revision list for 5.1 states:
From 5.0.10 -> 5.1
1. Still more work on the Ghost adapters problem - we think we have finally beaten it into submission.

I'd suggest, since the bug was still present after an upgrade path to 5.1, that whatever fixes have been done still don't go far enough..

[adrien]

lost me there.

The ghost adapter issue was one with dialup where upon making a connection then disconnecting, the adapter for the dialup connection would still show up as an interface in the route table if you went to the command line and typed "route print' then you would see it, and on subsequent connections and disconnections of the dialup, more and more of these would appear

By all accounts we did fix this in 5.1

Are you seeing something else? What you describe sounds more like something else.

Adrien

[absalomedia]

How else would you explain an adapter that cannot be seen in Wingate (let alone anywhere else - W2K Active Directory, DNS, RRAS, etc..) yet still holds control of all the DHCP data on an internal network via the registry ? It is a "ghost".

That was the bug, and there has been a significant commercial backlash against my business and my reputation because of it.

Let me ask you this - if you have two distinct networks both attached to the Net through the same router (same NETBIOS network name, different IP and DHCP scopes), both using W2K Active Directory integration into Wingate (i.e. the old network was being retired), is there a chance the DHCP scope / adapter info could be transferred between the network global catalogs?

When I initially set this network up, this "ghost" adapter wasn't happening. Online and offline access to the server/ Net via Wingate worked like a dream, yet as soon as the client decided to relocate the server to its designated area, all hell broke loose.

Now Wingate did something out of the ordinary because it was rendered Net access nearly inoperable for a month. Time and time again it came back to the issue that the DHCP data on the network was incorrect, yet all servers (Wingate, Wingate DHCP, Active Directory DNS, RRAS) all reported everything as legit and working.

The client finally found a registry setting showing Wingate pointing to the old network gateway instead of the new one, when I had expressly tested the network so it held the gateway data for the new network. And that fixed it..

As far as I can tell, there was a discrepancy between a "bound interface" in regards to what Wingate reported, and what Wingate had in registry.

(Hopefully screencaps of this bug in action will follow)