Okay, let's try something interesting. . . Here's part of nslookup's result for Yahoo's web servers:
Non-authoritative answer: Name: yahoo.com Address: 66.218.71.198 Name: yahoo.com Address: 64.58.79.230 Try telnetting to port 80 on one of 'em, and see if that works. If that doesn't work, they've blocked outgoing TCP connections at least to port 80. Here's my IP address (obtained by nslookup dave.tj): Name: dave.tj Address: 67.81.72.42 See if you can connect to port 5222 on that system. If it doesn't work either, it's probably safe to assume that all outgoing TCP connections are blocked. Now, if that's the case, we may have luck using keepalive via HTTP against a web server front-end with a huge maximum request per connection limit (assuming your proxy supports keepalive connections). If that doesn't work either, it's time to think some more. . . - Dave Andreas Ames wrote: > > Hi, > > Dave <[EMAIL PROTECTED]> writes: > > > Just out of curiosity, what exactly are the firewall restrictions? > > I'd very much apreciate a way around these restrictions, though I > haven't found one yet. Altough 'they' provide a http and ftp proxy I > can't even resolve outside hostnames via dns. That's the worst one. > No ping to outside ip addresses either. I could possibly use http > polling for jabber but as I understand it, it's more of a hack right > now. I haven't tried pserver with ip addresses instead of hostnames > (see dns thing above) but I doubt very much it would work. > > cheers, > > Andreas > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev