It is theoretically possible, if you open WIBU's port on the firewall. If you "see" the wibu server from home, but ArchiCAD can't connect to it, the problem is usually that you have not specified the server in WkConfig. If no server is specified, ArchiCAD will search the subnet for key servers. If you want to connect to a remote key server (not in the same subnet) you have to specify the server(s) in the "Ordered List of WkLAN Servers" in WkConfig. (or on PC, under the Network tab page in the WIBU control panel)
You have to specify the server address in the WkConfig on all client machines. Of course this IP address needs to be the one that is valid and working outside the firewall. You don't have to change anything in the WkConfig of the key server machine.
The options "local" and "WkLAN" tell WIBU where to look for the key. On the server machine (where the key is plugged) this should be "local", as it should scan the USB ports to find the key. On the client machines it should be "WkLAN", since they have no keys attached, they need to browse the network. If you enable both "local" and "WkLAN" on all machines that is also fine.
We're having some problems running Archicad on a new Mac OSX network.
The network is setup so that users have roaming profiles. When Archicad loads, a window appears saying that the Cache Library cannot be loaded on a remote drive (it's currently set to the recommended default which is homes:user:library:caches:graphisoft). All permissions are set so that users can read and write to the library:caches:graphisoft folder.
We're also having autosave problems when the autosave folder is set as the default (... library:application support:graphisoft etc...).
Should the cache folder be set to be on the local machine? Does anyone know any unpleasant side effects that might happen if I do this?