Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: AJ Dyka on March 04, 2001, 01:46:11 PM

Title: More gateway access issues
Post by: AJ Dyka on March 04, 2001, 01:46:11 PM

Now that I have the Outlook mail and ICQ issues solved (hehehe ...) has anyone had any experience with getting SETI to talk via the gateway?

I was wondering if access to ports 25 (POP3), 110 (SMTP), 4000 (ICQ), etc have been specifically opened to allow access through the firewall, and if all others have been closed?

I'm not sure what port SETI trys to use, but is it something that I will need to enable specifically with a custom IP chain or should it 'just work'?

If I do need to enable it (and I know this question has been asked before, but not really answered), how would I go about making the appropriate ammendment to allow it?

Thanks.

Title: SETI (was Re: More gateway access issues)
Post by: Fran Boon on March 04, 2001, 01:55:15 PM

SETI just uses HTTP - this is enabled by default, so you shouldn't need to make any modifications :)

F

Title: Re: More gateway access issues
Post by: Steve Lewis on March 05, 2001, 05:07:09 PM

I use Seti@home on two clients behind e-smith gateway w/out any proxy config or special config.