AC9 and WiBu-key

[Anonymous]

Hi

I installed the Wibu-key on our server (XP with sp2). I installed AC9 on a client (XP with sp2) and I can use AC9 in other words there is communication with the WiBu key on the server.

For some reasons I had to change the subnet on our network. From that moment I can NOT use AC9 on this client. A re-install (recommended by our supllier) of AC9 is no solution.

On other clients, on which AC9 is installed after the change in subnetting was made, AC9 works just fine.

any idea?

[__archiben]

granaet wrote:
For some reasons I had to change the subnet on our network. From that moment I can NOT use AC9 on this client.

totally obvious, but i take it that both machines are still on the same subnet?!

~/archiben

[Anonymous]

I assume the client address is set manually. You could try setting it to DHCP (if you haven't already) and see if it picks up the subnet properly.

[Anonymous]

totally obvious, but i take it that both machines are still on the same subnet?!

Yes thet are in the same subnet, this client works fine execpt that AC does not start.

I get the following error message

'protection key not found or not valid"(1050017)'

[Anonymous]

Hi

For your information: the clients get there adress from a DHCP server. De server in our network has a fixed adres. All in the same subnet with a correct mask.

When I start AC there is shortly the splashscreen and then there is a error message saying 'protection key not found or not valid (1050017)'.

[Anonymous]

Because its saturday and my colleage have there weekend I tried the following:

I installed the WiBu driver on that client of mine and moved the key from our server to this client. So this client is the WiBu server.
With the WiBu software (that green icon from the configuration panel) I can not detect the USB WiBu-key (this works fine when the key is inserted on our server). Also in this configuration AC will not launch.

[Anonymous]

I'm not to familar with the windows wibukey server, but I'm sure it does not differ too much from the Mac. Some things I would try:

Check your wibu key settings on the server and the wibukey.ini on the client and confirm the settings match. Ip Address and port # etc. Be sure to un-comment the "Server="Your server ip address"" under the [WkLAN Client] heading.

Open your web browser and insert the following : "YourServerIPAddress:Port#ofWibuKeyServer" ex. "10.0.201:22347" or "192.168.1.1:22347" This should call up the WIBU-KEY Server Web Monitor page. If not I would guess you have a network issue.

Again, this is where I start in a Mac only environment. YMMV

On the client does AC start when you plug the key directly into one of the ports?

-Scott

[Anonymous]

I've just upgraded the WIBU software on our server as recommended by our dealer for use with ARCHICAD 10.

Now we have lost the ability to share our dongles on both Release 9 and Release 10, which is seriously affecting our work capability.

Have I missed something? Is there a something you have to do to initialise the WIBU once it's been upgraded?

Workstations: MAC with OSX 10.3.9
Server: PC with Windows XP.

[Djordje]

Keith wrote:
I've just upgraded the WIBU software on our server as recommended by our dealer for use with ARCHICAD 10.

Now we have lost the ability to share our dongles on both Release 9 and Release 10, which is seriously affecting our work capability.

Have I missed something? Is there a something you have to do to initialise the WIBU once it's been upgraded?

Workstations: MAC with OSX 10.3.9
Server: PC with Windows XP.

Ability to share? Network dongle?

Please be more specific.

[Anonymous]

Problem solved through our dealer.

Turned out to be 2 x faulty dongles.

Thanks - K