We send the registered URL's for Sharepoint and Reporting back to the client - based on a default install, those are "internal" names (the hostname of the app tier). If those aren't resolvable to an "outside" client, when it goes to connect to those url's, it will fail.
You can see which URL's are registered by logging into the app tier and invoking GetRegistrationEntries (http://localhost:8080/services/v1.0/registration.asmx?op=GetRegistrationEntries) with an empty toolId - in the XML that comes back, you'll see RegistrationEntry's for Reports and Wss (the Type elements in those stanzas). If you try those exact url's (no hostname changing) from the "outside" clients, does it work? I'm assuming not.
In that case, you'll want to have a name that works for both "internal" and "external" clients, then change the registration url's so those are the ones hit. An example of this (in this case, going through an ISA server) is at: http://www.vergentsoftware.com/blogs/ckinsman/CommentView.aspx?guid=4f5f8046-c0a6-4fd4-844f-128b03fba264
Team Foundation Server - http://blogs.msdn.com/jmanning/ |