At 11:53 AM 3/01/2006 +1100, you wrote:

>I have an application using IBO events and I am trying to deploy it to a
>public service network. Events are failing with a message on registration:
>"PCName cannot be resolved."
>It appears that the network will resolve the fully qualified PC name i.e.
>PCName.sub.domain.nsw.gov.au but it will not resolve the abbreviated PCName
>name.
>
>I talking to the network admin people about this but just thought someone
>might know if it's possible to register events by appending the
>.sub.domain.nsw.gov.au suffix onto the machine name prior to registration?

Events are routed between a client and a random port at the server, i.e.
not port 3050, using whatever transport layer the client connection is
using (tcp/ip, netbeui). The server address is the same one that the
application accesses; the port that the server uses for a particular
connection's event callbacks isn't known to the application but it's surely
not "appended".

For tcp/ip, it will be PCName.sub.domain.nsw.gov.au/nnnnnn:, where nnnnnn
is the randomly selected port number. At the API level, where IBO dwells,
the port number isn't known/knowable/settable. The callback address is
calculated and used internally and is transparent to the API layer, i.e. it
either works or it doesn't and, when it doesn't, you get the exception.

The error message seems to indicate that the callback is failing because
the server couldn't resolve PCName.sub.domain.nsw.gov.au/nnnnnn: as a
machine and port visible to the network. My first guess would be that the
server doesn't have any open ports available and so the callback address is
stuffed. With or without that problem, if it's a VPN, then events can't be
used at all, since the VPN session itself is (by design) bound and isolated
to one and only one port.

Helen