by Pascal » Aug 18 04 12:42 am
Slow day in the office - apologies.
I suspect what is happening is, because you are using a cross over cable with only the two computers, up until the point where both machines are started the XP machine is not seeing itself as connected to a network. Because WinGate has already started - it has no IP to bind to for services. When the client starts up, the IP begins to exist, but WinGate remains unaware of it until you stop/start the Engine.
6.0 has introduced dynamic binding to get around this exact type of problem. It lets you specify a policy that tells the service what to bind to (Internal vs External, specific adapters, ips, etc.) so no matter how you change things underneath, WinGate will bind correctly. (Plugging cables in out, USB adapters in out, etc.)
So, an upgrade to 6.0 might very well help you. As always, if you are upgrading, make appropriate backups of your registry and make sure you have your license key handy - this version requires activation.