Ah that makes sense. Thanks for taking a look! Any reasonable work-around in the meantime that you can think of? It seems all you can get out of a NetworkAddress is OS-specific handles and there doesn't seem to be a way to feed that into the relevant TCPConnection framework that I can see.
Sorry you to wait until tomarrow noon. Then I hopefully know more ...
should not be too much trouble to find a workaround.