Oliver, It was pretty clear to me that the current default behavior is such to support virtual hosting. My complaint is I think JabberD does a poor job of handling this error condition. Either the server should issue an intelligible error message which a jabber client can interpret, or that the a default virtual host can be specified for when a stream request comes in qualified with an IP.
I think this problem is best illustrated with Jabber.com's Win32 client. If you encounter this problem it issues a dialog saying that it couldn't connect to the server and that it could be a problem with your firewall config, etc. But this is not a connection problem or a deficiency of the win32 client, its a server problem. JJ __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
