Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

New interface detected event (Windows XP) problem

Nov 18 04 11:20 am

Hi. I have problem with WinGate 5.2.3.901. I have two OSes Win98SE and WinXP. Wingate is installed in both OSes. I have two LAN cards in my server computer. One is connected to internet, second is connected to second computer (client). In Win98SE everything works fine. I'm using ENS to share internet. The problem is with WinXP. When I boot client computer before server then works fine. When I boot server when client is off, Wingate says that my interface was disconnected, then when I boot client - internet sharing is not working. To start working I must stop Wingate engine, then start it, then Wingate says that new interface is detected, autoconfigured and from now everything i ok. How can I fix it? In Win98SE both interfaces are always available in Wingate even if client is off. In XP lan card connected to client dissapears from Wingate. Can anyone help me?

Nov 18 04 11:29 am

XP is slightly more advanced. From the sound of it, you are using a crossover cable between the two PCs. With one off, XP will detect it as "disconnected".

WinGate 5.2.3 had that exact problem with bindings, which is why 6.x has introduced a binding policy system; which allows you to specify a policy for which adapter to bind to. That way, no matter what the state of the adapter is, when it becomes available WinGate will bind to it.

You can use your existing license key with 6.0.3, so an upgrade will resolve this for you.

Nov 19 04 3:29 am

Thank you very much.
Post a reply