John Monahan wrote:
> Raptor is not certified with NT SP6anything, so go back to SP5+hotfixes
and
> you shouldn't have any problems. They had to release a new version, 6.01,
> to work with SP5, so I'm assuming there will be another new version that
> will work with SP6a.
Now after I found the origin of my problems (see below), it works pretty
fine. /With/ SP6a and all Post-Sp6-hotfixes available end of december (and
even some handmade scripts enforcing security of NT systems, among others
see people.hp.se/stnor/hpntbast13.pdf).
BTW: Axent released patch 6.02 (I'm working with) some months ago to work
with SP5.
> Remote Log is installed with Raptor 6 in \raptor\firewall\bin on NT.
No, it is NOT installed in this location. You can find it on CD in
\additional
software\axent\rlog.
> Check page 9-16 of the Raptor reference guide for more information.
Somebody stated here some time ago that Raptor documentation is not very
helpful.
It's even worse. There are LOTS of things that just don't work as described.
It's some kind of marketing paper, no technical doc.
On their web site you can't find anything. Tech support was not able to
answer evident questions (from a retrospective point of vue).
My problem with outbound SMTP (see below) was solved after I searched - by
coincidence - the internet for the term 'MX rollover' (anybody here who's
able to explain what this is, or better to state in which RFC it's
described?). /THEN/ I found on Axent web site the paper I had been searching
for which described exactly my problems:
Raptor SMTP Proxy does NOT work as MX relay (again: anybody here who would
expect a 'proxy' of a store-and-forward protocol to work transparently?).
You have to configure your internal mail servers to deliver directly. That's
rather hard to find in documentation. And (even if I don't like those
sophisticated discussions about technical terms): is this a 'proxy'?
Something working transparently is no proxy. Maybe an application gateway.
And, remember, store-and-forward protocol...
[Enno Rey]
>> Is anybody here who got outbound SMTP via Raptor 6/NT (SP 6a + some
patches
>> + Raptor patch 6.02) to work?
>> I tried the whole night from internal Exchange 5.5, from internal
sendmail
>> 8.7.6, via direct access from Outlook, directly telnetting to port 25
>> internal interface or port 25 at MX outside the firewall, disabling ESMTP
>> on Exchange and whatever.
>> I called Axent tech support (they gave me a case number...), searched
up'n
>> down the Internet.
>> I sniffed round the firewall: SMTP connections to firewall don't seem to
>> get any further than TCP handshake, but on the outside I see DNS traffic
>> for
>> resolving MX for mail addresses from internal queue ... strange!
>> For testing purposes, I even allowed 'universe to universe SMTP' (don't
>> blame me, being desperate) - nothing!
>> Messages to internal mailers alike 'service not provided to you', logs on
>> firewall indicated something like 'x.x.x trying non-transparent access'
(so
>> I enabled various forms of transparency) or 'timeout: x.x.x didn't
respond
>> to startup command' (I don't know any SMTP 'startup' command, do you?).
>> I ended up with redirecting ports to mailer outside firewall. Thatworked.
>> But then I don't need 'high-end' SMTP-proxy. And then I have to configure
>> outside mailer to relay generously...
Enno Rey
[EMAIL PROTECTED]
PGP: FB9B DA6D 6706 5A8D A361 F63C 6650 E4C8 3BBE 04E9
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
