WGIC Not Working

[Kong]

Okay... I've looked for any info I could find on this and found nothing.

WinGate Server....
AMD K6-II 450MHz
256MB PC133 SDRAM
Windows 2000 Pro SP4
WinGate 5.07
It has worked and still works fine... I do not believe the server has anything to do with the problem.

Client PC with Problem
System Stats not important.... higher than Server > 1.6 GHz
Windows XP Pro SP1
WGIC from WinGate 5.07 installed.

Now, I tried upgrading to WinGate 5.08 when it was released but had problems running an an app that ran fine in 5.07. With 5.08 it could no longer connect to related servers.

Anyway, I recently had to redo that client computer. Everything was working fine. I use WGIC and for certain apps disable WGIC and just run NAT.

I have folders shared over private network, as I normally do, I went to set certain folders shared on the client PC and WinXP said it rquired me to run the Network Setup Wizard to be able to set folders to be shared. At the time I saw no reason not to run it, and didn't stop to pay attention to see if it was required to run or not.

Now WGIC will nto run.

THe client PC still has access to the internet through WinGate but using NAT only. WGIC is not running.

Does this sound familiar?
Does anyone have any ideas on how this can be resolved?

Any help would greatly be appreciated. If you require more information I will do my best to supply it.

Thanks in Advance.

[erwin]

Hi Kong

Have you tried resetting the WGIC as per helpfile instructions.? Found under the Advanced tab of the WGIC applet.

There is also a toggle which will switch the WGIC completely off. It can be restarted from the WGIC applet. Check that on the general tab the Enable WinGate Internet Client is still ticked?

Have you reselected the server to use under the WinGate servers tab?

You can try rechecking these things to see if it helps.

Regards

Erwin

[Kong]

I have tried resetting WGIC, I have tried toggling it off and back on, and I have tried reinstalling it.

Also, selecting the server to use won't make a difference because it's not like WGIC is starting up and then cannot find the server... It simply wont' run.

[tim]

I have tried resetting WGIC, I have tried toggling it off and back on, and I have tried reinstalling it.

Also, selecting the server to use won't make a difference because it's not like WGIC is starting up and then cannot find the server... It simply wont' run.

Hi, please check in GateKeeper that the WRP service still has a binding to the Private interfaces. Maybe in the upgrade a binding was lost or removed.

Tim

[Kong]

Hi, please check in GateKeeper that the WRP service still has a binding to the Private interfaces. Maybe in the upgrade a binding was lost or removed.

Tim

There is no WRP Service under User Services.
There is a Winsock Redirector Service in System Services.

The Winsock Redirector Service has all it's binding set properly.

[Kong]

So is that what you were referring to?

I was thinking.... this all started happening after I ran the networking setup wizard. It makes sense to me that there would be a networking setting or component which got set when the wizard ran.

I just have to find it.

I'm thinking there must be something to tell Windows that when looking for an external connection run WGIC. I was looking around and found something which my be unrelated.

Networking Connections -> Advanced Settings -> Provider Order

There are 3 listings under network providers...

Microsoft Terminal Services
Microsoft Windows Network
Web Client Network

Any ideas on that?

Maybe someone running WinXP and that has WGIC working can check on that and see what they have in there.

[Kong]

No one has any ideas?

WGIC stops working when/if you run Network Setup Wizard.

I do not have ICS running on the server, only wingate.
There is nothing wrong with the WinGate Server or it's WinGate settings.

There must be something to tell the client PC that if looking for an ouside connection run WGIC but it won't.

Any ideas?

I really dont' want to re install windows again.

[adrien]

Are you just trying to use IE when you see this problem?

After running the network setup wizard, IE6 no longer loads winsock properly, and so therefore doesn't load the WGIC LSP dll.

The only way we have found in the past around this is to remove the default route/default gateway on the client machine, but this means you cannot use NAT any more. If this is not a problem, you could try that.

Adrien

[Kong]

IE has nothing to do with it.

I have a number of applications that I use and all I ran with WGIC.

WGIC simply is not running and will nto run. I dont' know why.

I'll ask again....

There has to be something on a client pc that has WGIC installed telling it to start up WGIC if a connection onto the net is required.

Does nayone know what that might be?

[adrien]

Um

I wrote WGIC

So believe me IE can sometimes have something to do with it. Especially version 6.

Sometimes it doesn't load winsock properly. the WGIC is a DLL that is loaded by winsock.

But if this is happening on other applications then you answered my question, and it is obviously some other problem.

When you reinstalled the WGIC did you uninstall it first? If so, try reinstalling over the top without doing that.

The WGIC links into the chain of winsock service providers and remembers the OIDs of the components it linked to in the registry, if the network setup wizard messed with this chain (perhaps reset it), then an uninstall or a rebind may not work properly. since it would attempt to use the registry values to relink or unlink.

Adrien

[Kong]

Um

I wrote WGIC

So believe me IE can sometimes have something to do with it. Especially version 6.

Sometimes it doesn't load winsock properly. the WGIC is a DLL that is loaded by winsock.

But if this is happening on other applications then you answered my question, and it is obviously some other problem.

That's what I ment. The problem has nothing to do with IE. Other applications which are supposed to run WGIC are not.

When you reinstalled the WGIC did you uninstall it first? If so, try reinstalling over the top without doing that.

The WGIC links into the chain of winsock service providers and remembers the OIDs of the components it linked to in the registry, if the network setup wizard messed with this chain (perhaps reset it), then an uninstall or a rebind may not work properly. since it would attempt to use the registry values to relink or unlink.

I tried that and it didn't help.

WHere can I go to find out if the dll is even been loaded?

[erwin]

Hi Kong

I had a test with trying to reproduce this and we think we may have found the problem.

We found that regardless if you had previously had set IE not to dial a connection (setting under Conections tab in Internet Explorer), Windows would reset it to "Dial if Network Connection not present" after running the network wizard.

I found that by changing this setting back to "Never Dial a connection"
WGIC would begin to work correctly again for Internet access. I tested this also with other aplications such as ftp.exe and telnet.exe and these work fine.

May I suggest checking the connections setting in IE to see that it has not been reset like I described above. If it is set it back to "Never dial..." and it should hopefully solve the problem.

Let us know how you get on

Regards
Erwin

[Kong]

Thanks for looking into this for me. Unfortunately, what you suggest I can not do.

Those options...

Never dial...
Dial whenever...
Always dial...

Can not be changed or are not used, greyed out. They have always been like that. I dont' have any dialup settings since I have no dialup adapters in this computer and no VPN settings.

[erwin]

Hi Kong,

With a little further investigation I found (fingers crossed ;-) a solution to you having all your connections greyed out.

We also have some dual NIC machines in our lab and so found a similar situation.

Now this might sound a little strange, but when you are faced these options greyed out, I have discovered that if (after running network wizard etc) if you do the following, it will work

1. Go to the connections tab in IE as before
2. Click on the "Add" button which is beside the Dialup and Virtual Private Network connections box.
3. It will start a Wizard for a new connection... at this point click Cancel
(you will should be returned to the Connection tab in IE).
4. Click the OK button down the bottom of the Connections tab.
5. Relaunch IE and WGIC should start working.

Obviously in XP, IE6 controls the Internet applications/connections etc, but by "fooling" IE as I have suggested it will enable WGIC to work again.

Hope this helps

Regards
Erwin

[Kong]

Well... I dont' know exactly how or why that would work... but it did so I'm happy. :)

Thanks for all the help. I'll keep my eye on it just incase it decides to stop working again and if anything else happens I'll let you know.

Thanks. :)

[pepexe]

I just registered to say that I had the very very same problem Kong had, and I could solve it just like him. Thanks a lot.

The only "but" I'm experience is that now pages and pop3 mail cheking is done a little slower than before (obviouly in client machine).

I'm going to do the win-xp-auto-network thing again to compare speed. Kong, did you notice this too?

[Kong]

Everything seems to be working fine for me.

Normal speed.

[ChrisH]

Hello,

I have a very similar issue that doesn't want to be solved with the above recommendations.

The user upgraded from win98 to XPpro and ran the network wizard. Now WGIC client will not work on this machine. I tried the solutions above to no avail. I have uninstalled and reinstalled WGIC many times.

I did discover though, that something is holding on to the wglsp.dll. It cannot be removed from the system. I finally caved and booted from a floppy into DOS and removed it the "old fashioned" way. Upon reboot the LAN connection no longer worked. So I set static address and pointed to WG machine and it now connects to LAN. Reinstalled WGIC - no workee. Connects OK by NAT but no way no how by WGIC.

Short of reinstalling XP on this machine does anyone else have any suggestions? Although reinstall XP may be fastest way. The frustrating part is I have another machine upgraded to XP and no problems. This network wizard obviously adjusts something critical. TIA