Has anyone ever used Crystal Reports against an Oracle DB via the internet?

Any idea how this might be accomplished if, say, the DB was located in a DMZ?

Thank you.

reijo_us@yahoo.com (Reijo) wrote:

>Has anyone ever used Crystal Reports against an Oracle DB via the internet?
>
>Any idea how this might be accomplished if, say, the DB was located in a DMZ?
>
>Thank you.
We do have a server set up for thus, but It is not easy to explain in a posting ; if you do a Google search in the oracle
newsgroups for Firewall - or check the Oracle docs at http://tahiti.oracle.com


It involves forcing the listener to use the same port for all communications( and then allowing that port through the
firewall) rather than the default behavior of assigning a random port after the initial connect is made.

hth,

Is there any security concerns to put a db server on DMZ??

Turkbear <john.g@dot.spamfree.com> wrote:

>reijo_us@yahoo.com (Reijo) wrote:
>
>>Has anyone ever used Crystal Reports against an Oracle DB via the internet?
>>
>>Any idea how this might be accomplished if, say, the DB was located in a DMZ?
>>
>>Thank you.
>We do have a server set up for thus, but It is not easy to explain in a posting ; if you do a Google search in the oracle
>newsgroups for Firewall - or check the Oracle docs at http://tahiti.oracle.com
>
>
>It involves forcing the listener to use the same port for all communications( and then allowing that port through the
>firewall) rather than the default behavior of assigning a random port after the initial connect is made.
>
>hth,
>

Turkbear wrote:

> reijo_us@yahoo.com (Reijo) wrote:
>
>
>>Has anyone ever used Crystal Reports against an Oracle DB via the internet?
>>
>>Any idea how this might be accomplished if, say, the DB was located in a DMZ?
>>
>>Thank you.
>
> We do have a server set up for thus, but It is not easy to explain in a posting ; if you do a Google search in the oracle
> newsgroups for Firewall - or check the Oracle docs at http://tahiti.oracle.com
>
>
> It involves forcing the listener to use the same port for all communications( and then allowing that port through the
> firewall) rather than the default behavior of assigning a random port after the initial connect is made.
>
> hth,
>
Hmmm - there *are* SQL*Net aware firewalls. The shared socket approach
was broken
for Windows in 8.1.6

--
Regards, Frank van Bortel

Frank <fbortel@nescape.net> wrote:

>Turkbear wrote:
>
>> reijo_us@yahoo.com (Reijo) wrote:
>>
>>
>>>Has anyone ever used Crystal Reports against an Oracle DB via the internet?
>>>
>>>Any idea how this might be accomplished if, say, the DB was located in a DMZ?
>>>
>>>Thank you.
>>
>> We do have a server set up for thus, but It is not easy to explain in a posting ; if you do a Google search in the oracle
>> newsgroups for Firewall - or check the Oracle docs at http://tahiti.oracle.com
>>
>>
>> It involves forcing the listener to use the same port for all communications( and then allowing that port through the
>> firewall) rather than the default behavior of assigning a random port after the initial connect is made.
>>
>> hth,
>>
>Hmmm - there *are* SQL*Net aware firewalls. The shared socket approach
>was broken
>for Windows in 8.1.6

To be clear..The DB server is not in the DMZ, it is inside the firewall - the Reports that use the data are linked through
the Web Connector on the DMZ machine..

The shared sockets problem was fixed in 8.1.7 ( but still can cause problems) - works fine in 9.

Turkbear wrote:

> Frank <fbortel@nescape.net> wrote:
>
>
>>Turkbear wrote:
>>
>>
>>>reijo_us@yahoo.com (Reijo) wrote:
>>>
>>>
>>>
>>>>Has anyone ever used Crystal Reports against an Oracle DB via the internet?
>>>>
>>>>Any idea how this might be accomplished if, say, the DB was located in a DMZ?
>>>>
>>>>Thank you.
>>>
>>>We do have a server set up for thus, but It is not easy to explain in a posting ; if you do a Google search in the oracle
>>>newsgroups for Firewall - or check the Oracle docs at http://tahiti.oracle.com
>>>
>>>
>>>It involves forcing the listener to use the same port for all communications( and then allowing that port through the
>>>firewall) rather than the default behavior of assigning a random port after the initial connect is made.
>>>
>>>hth,
>>>
>>
>>Hmmm - there *are* SQL*Net aware firewalls. The shared socket approach
>>was broken
>>for Windows in 8.1.6
>
>
> To be clear..The DB server is not in the DMZ, it is inside the firewall - the Reports that use the data are linked through
> the Web Connector on the DMZ machine..
>
> The shared sockets problem was fixed in 8.1.7 ( but still can cause problems) - works fine in 9.
>
>
>
>

As it *is* Oracle, I suppose SQL*Net comes in place. You state the db is
inside the firewall, so I suppose -again- there's SQL*Net between
your Web Connector (DMZ) and your db - meaning through the firewall.
This firewall should/could be SQL*Net aware, or you use the
shared_socket solution.

Just to point out another possibility, namely SQL*Net aware firewalls.
--
Regards, Frank van Bortel

Turkbear <john.g@dot.spamfree.com> wrote in message news:<u20nrvsc3g2lm6pr0k6fcha3d7arqqedmq@4ax.com>. ..
> Frank <fbortel@nescape.net> wrote:
>
> >Turkbear wrote:
> >
> >> reijo_us@yahoo.com (Reijo) wrote:
> >>
> >>
> >>>Has anyone ever used Crystal Reports against an Oracle DB via the internet?
> >>>
> >>>Any idea how this might be accomplished if, say, the DB was located in a DMZ?
> >>>
> >>>Thank you.
> >>
> >> We do have a server set up for thus, but It is not easy to explain in a posting ; if you do a Google search in the oracle
> >> newsgroups for Firewall - or check the Oracle docs at http://tahiti.oracle.com
> >>
> >>
> >> It involves forcing the listener to use the same port for all communications( and then allowing that port through the
> >> firewall) rather than the default behavior of assigning a random port after the initial connect is made.
> >>
> >> hth,
> >>
> >Hmmm - there *are* SQL*Net aware firewalls. The shared socket approach
> >was broken
> >for Windows in 8.1.6
>
> To be clear..The DB server is not in the DMZ, it is inside the firewall - the Reports that use the data are linked through
> the Web Connector on the DMZ machine..
>
> The shared sockets problem was fixed in 8.1.7 ( but still can cause problems) - works fine in 9.


For those connecting through a firewall, are you using Advanced
Security for encryption?

Thanks.

Turkbear <john.g@dot.spamfree.com> wrote in message news:<u20nrvsc3g2lm6pr0k6fcha3d7arqqedmq@4ax.com>. ..
> Frank <fbortel@nescape.net> wrote:
>
> >Turkbear wrote:
> >
> >> reijo_us@yahoo.com (Reijo) wrote:
> >>
> >>
> >>>Has anyone ever used Crystal Reports against an Oracle DB via the internet?
> >>>
> >>>Any idea how this might be accomplished if, say, the DB was located in a DMZ?
> >>>
> >>>Thank you.
> >>
> >> We do have a server set up for thus, but It is not easy to explain in a posting ; if you do a Google search in the oracle
> >> newsgroups for Firewall - or check the Oracle docs at http://tahiti.oracle.com
> >>
> >>
> >> It involves forcing the listener to use the same port for all communications( and then allowing that port through the
> >> firewall) rather than the default behavior of assigning a random port after the initial connect is made.
> >>
> >> hth,
> >>
> >Hmmm - there *are* SQL*Net aware firewalls. The shared socket approach
> >was broken
> >for Windows in 8.1.6
>
> To be clear..The DB server is not in the DMZ, it is inside the firewall - the Reports that use the data are linked through
> the Web Connector on the DMZ machine..
>
> The shared sockets problem was fixed in 8.1.7 ( but still can cause problems) - works fine in 9.

I have noticed talk on the newsgroup about using CMAN in the DMZ or
setting up shared servers (MTS) and specifying the ports to use.

Are there any known limitations or issues/problems with CMAN (or MTS)
used in this fashion?