Some of our developers work remotely; the WireTap server is on a local net with a link-local IP and we've set up the router to do NAT port forwarding. We've also set the wiretap.cfg file to have both the local IP address and the world visible IP.
This works for browsing and reading frames, but not for writing frames. When a remote client tries to write frames, it seems that WireTap is trying to use the link-local IP.
Sounds peculiar. In v2007 (client and server), when a connection is established to a server, a negociation is made regarding the IP address to use for media IO. All media IO (read and write) shares the same network path under the hood.
I can't think of a situation why this would not work ... unless you are writing to a pre-2007 server.