wingate internet client problems

[divinity]

Hey --

i just tried installing the new WGIC on two machines running xp pro sp2. on both machines, the wingate authentication dialogue fails to pop up, and when i try to toggle the client on and off, i get a small message box entitled "wingate internet client is not installed", with a message saying either "the requested file can not be found" or "the operation completed successfully."

inspecting the file listing under c:\windows\system32, i noticed that wgsrvins.dll is installed instead of wgclins.dll -- i'm not sure why this is happening.

the wglsp.dll appears to be registered correctly in the Winsock2 service.

thanks!

[adrien]

Hi

When you installed the WGIC, which login were you under? Was this an administrator login?

Adrien

[divinity]

i was under my own login, which is definitely an administrator account.

[Pascal]

We've had reports of problems when using the WinGate Internet Client with XP SP2. Unfortunately, our tests in QA have all been successful - i.e. we can continue working, WGIC stays up, etc.

However, been doing some research on this. Microsoft has released two articles that detail what you can do when you are experiencing problems post XP SP2.

Link1:
http://support.microsoft.com/default.aspx?kbid=884130&product=windowsxpsp2

Link2:
http://support.microsoft.com/default.as ... -us;842242

The problem could be related to the XP firewall. Is this turned on or is it turned off ? It is possible that the application attempting an internet connection starts. The LSP is hooked, but any traffic going between the client and server is blocked by the firewall. Then you won't see the login dialog.

It might be worth enabling the log file for XP Firewall, that might give you a clear indication if this is happening or not.

[divinity]

this still doesn't explain, in my mind, the problem with the wingate toggle. i'm working on the windows firewall stuff...

[Pascal]

It should not happen with build 995 - that is the one we've been using internally here. There were some problems with some of the earlier BETA releases which would have caused that kind of behaviour. A second problem could be related to XP SP2, but I've not been able to reproduce this kind of behavior.

What version of WGIC do you have installed ? (I.e. from which Engine build did it come)

Secondly, have you tried to uninstall and reinstall, see if that makes a difference ? Does that work on non SP2 machines ?

[divinity]

i only ever downloaded build 995, so the WGIC comes from that installer. uninstallation/reinstallation of the software has not helped. i've tried this in combination with various different reboot/wgic toggle patterns.

i haven't tried it on non-sp2 machines. the remaining machines on our network need to have solid internet access, and i can't afford to mess with them until this problem is solved.

[Pascal]

And if you enter the WGIC control panel - does it show as "Enabled" or "Disabled" ?

[divinity]

Enabled.

i reinstalled the WGIC after diabling windows firewall for the machine in group policy, and it appears to have installed correctly, now...

[n]

[Pascal]

Ahhh. Good to hear. But does that mean you're running XP (With SP2) in an Active Directory environment ?

If that's the case:
Is WinGate synchronised with AD ? And who becomes the DNS server for the network then ?

That might be the missing piece of the puzzle when we were trying to reproduce this.

[divinity]

yes. we have xp sp2 clients served by a w2k server running active directory with DNS integration. wingate is set to NT authentication, but wingate's dns is disabled.

also, i've noticed that some of the problems i was having with troubleshooting this stem from the fact that the clients no longer reliably automatically detect the presence of the wingate server on the network...

[Pascal]

The unreliability - was that post XP SP2 or post 6.0 ?

[divinity]

post-sp2, i believe. i don't think i upgraded the WGIC on any of the machines before applying sp2, however.

[Pascal]

The Client will make a GDP request on UDP port 368 to discover any known WinGate Gateways. Is it possible that the response could have been blocked by the firewall ?

It might be necessary to add a port exception for the local area connection in the XP Firewall. Enabling logging for it would probably give you a clear indication if that is the case.

[adrien]

PS, this discovery uses broadcast packets. I'm not sure if the SP2 firewall treats these differently.

Adrien

[divinity]

i've disabled the firewall, though....it hasn't helped.