An unsuppoted operation was attempted

[neujron]

Hello Support! (Pascal, Genie, others...)

We have a problem on our Wingate since we upgrade to the latest version (from v.4.4 to v6.0). When we try to modify the policies of any services, there's an error that pops and it says "An unsuppoted operation was attempted". We didn't encounter such problem in the previous version.

What's wrong with this? We cannot add or modify anything on the "Policies" anymore. We are using "Everyone" and on the "Locations" tab we just include/exlude IP Addresses for the users to access the service. Even when you just click OK to exit without changing anything, same error appears. There are some services that we need to modify thru the policies and we need it badly.

I'll be sending the screen shot to the e-mail of Pascal for your reference.
Any help would be greatly appreciated, thanks.

[adrien]

Sounds like a bug in GateKeeper (I presume this is the application that posts the error rather than WinGate?).

We haven't seen any such problems like that here. I wonder whether there is some configuration setting that you have that is interacting and causing this.

Can you please send us your WinGate registry so we can take a look?

Adrien

[neujron]

Hi Adrien,

Before anything else, I just want to clarify 1 thing, Wingate Engine is different from Gatekeeper? When you right click on the icon for Wingate Engine and select Start Gatekeeper, they are totally different product or technically speaking? Just want to clarify the matter.

Anyway, the modifications, adding of services/server is in the Gatekeeper right? So, that means Gatekeeper is the one posting the error.

What file exactly that you need, a .REG or .INI file for the whole NT server or for the Wingate only? If only for Wingate, where can I find it, in what folder? If you're asking for the file "WinGateConfig.reg" which is the only .REG I found in Wingate sub-folder, it's an old file dated 12/04/2002.

Thanks so much.

[Nev]

Hi Adrien,

What file exactly that you need, a .REG or .INI file for the whole NT server or for the Wingate only? If only for Wingate, where can I find it, in what folder? If you're asking for the file "WinGateConfig.reg" which is the only .REG I found in Wingate sub-folder, it's an old file dated 12/04/2002.

Thanks so much.

Hi,

What you could do is:

In GateKeeper, click: advanced > options > Save Registry Settings

That will have all your current config from the registry.

Nev.

[adrien]

Sorry, I should have been a bit more specific.

If you go to HKEY_LOCAL_MACHINE\Software\Qbik Software\WinGate

and export that, or as Nev suggested export it from GateKeeper.

Then if you could send it to adrien at qbik dot com, that would be great.

In answer to your other question, WinGate comes in 2 parts, the administration and user interface part, called GateKeeper, and the engine that does all the work, wingate.exe.

GateKeeper connects to the engine to configure and monitor it.

Adrien

[neujron]

Thanks Nev & Adrien,

I've got already the wingate registry file created on Gatekeeper's Advance Option, I'll be sending it to Adrien's e-mail.

Have a nice weekend.

[Pascal]

I just tried this on a clean Windows NT 4.0 installation - it worked fine. What version of IE and which service pack do you have on that machine ? (I believe it's NT4.0, correct ?)

[neujron]

It's IE v6, NT4 Service Pack 6a, all critical updates/patches are applied.

Thanks.

[Pascal]

Thx, will try that setup now.

[neujron]

Thanks also, we'll wait for the result. One more thing Pascal, hope you'll not get tired of helping us. As I have told you before we'll post whatever problem that may arise.

Why is it that local computers on same network can't ping internal IP of the Wingate server even when the option in the ENS->Firewall ("Allow users to ping this machine locally") was checked already, installation/upgrade did check it by default.

Best regards.

[neujron]

Pascal,

The issue for the PING is a least priority, the operation attempt error and PC Anywhere is our 1st priority.

Thanks

[labull]

Neujron,

Have you tried the configuration for PCAnywhere as Pascal recommended - External IP for binding and Internal IP for interface?

Are ports 5631 (TCP) and 5632 (UDP) open in the firewall?

Is PCAnywhere running on the WinGate Server - if it is PCA could be intercepting the traffic at the WinGate server instead of it being passed on.

Larry

[labull]

Garbled message - please ignore

[neujron]

Hello Larry,

Yes, I've tried everything before I upgraded to the latest version (v6) and luckily I was able to modify the Bindings (external IP) and Interface (internal IP). Because right now there's no more Interface menu item on the newer version. I have also problem with the Policies item, I can't modify it anymore, I can't give or deny access to any user because of "An unsupported operation was attempted" error message.

PCAnywhere is not on the Wingate server, it's on a different PC internal to our network. Actually, we've connected a laptop to a dial-up (outside ISP) just 2 hours ago and tried connecting to the one hosting the PCAnywhere but unfortunately we can't. There were no hits or activity on the Wingate server either. Ports 5631 (TCP) and 5632 (UDP) are open in the firewall.

Thanks for the help.

[Pascal]

Interfaces have been replaced by "GateWays" in version 6.

We're still trying to reproduce the "unsupported operation" message. Currently running with your registry setup on NT4, with IE 6 (Which gave me about 15 errors on installing, but eventually completed - so that might be dodgy) and Service Pack 6. (Not sure if it's a - I'll have to double check that)

No matter which modifications I make, it still doesn't give me the problem, though.

[neujron]

Hi,

Thanks for the info Pascal, I checked already "GateWays" and it's different from previous version (wordings) but same functionality I think. What's "Specify IP" there, can I put also the IP Address of the PC hosting the PCANywhere instead of the internal IP of the Wingate server or it's not right?

We'll, I don't know what have caused this problem that's why I asked you guys. Have you installed it on a previous installation or you just install it without version 4.4, directly version 6? Maybe there's a difference also on the PC Configuration. Ours is just a clone PC with just 256MB RAM, Pentium III, 667MHz - a possibility maybe, I don't know.

Well, we have to wait again until your testings are over.

Best regards.

[adrien]

One thing to try - are you connecting from the local WinGate machine?

Try binding the Remote Control Service to your internal adapter, then run GateKeeper from another machine... just a hunch.

We would be keen to find out if the new build out also does this for you - we just uploaded build 993, WinGate 6.0.1 as a maintenance release.

Adrien

[neujron]

Hi,

Yes, I'm connecting on the local Wingate machine. If I'm going to bind to our internal adapter (right now the bindings is on the local machine MS TCP loopback only), is it any adapter and any IP? Do I have to remove the loopback or edit or just add internal adapter? Then I will install GateKeeper on another internal PC and access Gatekeeper from there to do modifications? Could you be kind enough explaining how to do it? I'm not so familiar with the steps.

Is it okay that I'll update first to the latest build or do bindings first (above procedure) ?

Thanks.

[adrien]

Hi

To bind to your internal adapter, you would just add a policy to bind to any internal adapter. If you instead choose any adapter, then the service will also be available from the Internet (it's secured so not a security issue).

Best to leave on the option for localhost as well.

As for whether you upgrade first or not. Hmmmmm. I guess it would be good to know whether accessing remotely fixes the issue. You should only need to copy GateKeeper.exe to the new machine as well.

Thanks

Adrien

[neujron]

Hi Adrien,

I have done what you have told me but same error we have even when you access it remotely. I bind it to our Internal Adapter and successfully connected but unfortunately it's the same result.

What should be the next step now?

Thanks.

[Pascal]

Does this happen if you create a new policy as well ? Even for a new service ?

Does it happen if you edit the system policies as well ?

[neujron]

Hi,

Yes, it happens everywhere on anything, existing or new services and on the system policies. We can't modify any policies anymore.

[adrien]

Maybe our best bet is to connect in from here running GateKeeper in the debugger. That will find the problem very quickly.

If you would like to do this, drop me an email to adrien at qbik dot com. You would also need to bind the Remote Control Service to your external adapter (or any adapter).



Adrien

[neujron]

OK Adrien,

How do we do this? Are you saying you're going to connect to our Wingate server? Just give me the details on what to do next.

Thanks.

[adrien]

basically I would need the IP address of your server, and a username and password to log into it with.

For me to be able to connect, you would need to bind the remote control service to your external adapter.

Then I should be able to see what is going on.

Adrien

[neujron]

Does the user with an Administrator rights (clone admin user) or just a common user?

Bind to ANY external adapter or to our 3COM network adapter (with our external IP on it)? If ever our 3COM, do I need your IP so that you can connect? Binding to ANY external adapter will be a security concern or not?

[adrien]

it shouldn't be a security concern, WinGate Remote Control Service uses a secure challenge-response authentication system, and encrypted connections. We have hammered it in the past with nasty stuff to see if we could cause problems, because typically this is one of the ports more likely to be opened up for remote admin than other ports.

Will probably need Admin rights, since need to be able to edit a service to modify policies.

You shouldn't need my IP unless you are tying things down, but it is 210. 55.214.100

Post user details to adrien at qbik dot com.

Thanks

Adrien

[neujron]

OK. So I'll just put ANY External Adapter because you confirmed to me it's not a security issue.

I'll send you the details on your e-mail.

[neujron]

Hello Adrien,

Just want to follow up what happen on your connection to our machine. Any updates so far?

Thanks.

[adrien]

Yes, got the problem fixed.

It is related to running a version 4.x key on that install. If you activate a trial key, you should be able to get around this problem immediately until we release a fix (I have fixed it here).

Thanks for your help

Adrien