Re: Firewall: use_shared_socket

We had to do exactly the same thing, for the same reason.

Our registry setting is in ....HKEY_LOCAL_MACHINE/software/oracle/home0..

If this does not work then you can set up an NT system variable of use_shared_socket = TRUE

Hope this helps...

If you need more info we've got a couple of e-mails from Oracle Support that may be of help

Cheers

Steve Bright

steve.bright_at_capgemini.co.uk

vs <slootsky_at_erols.com> wrote in message news:3809CA89.5AAA242C_at_erols.com...
> Does anyone have an experience in utilizing use_shared_socket=true in
> order to keep incoming calls on the port 1521? Why I need port 1521?
> Because I have a fire wall without proxy and only 1521 is allowed to
> accept incoming calls. The Oracle database is inside FW, the client -
> outside. I have Windows NT4.0, SP 4, Oracle 8.0.5. I have multiple
> Oracle homes. So I placed use_shared_socket=true in
> HKEY_LOCAL_MACHINE/software/oracle/all_homes/id0. The registry value of
> type is REG_EXPAND_SZ. It still does not work.
>
> Before:
> Without use_shared_socket=true my client's attempt to connect ended up
> with message "lost connection." It is my assumption that the initial
> client's call hits 1521 port, the only opened port in my firewall. Then
> listener sends the packet back to the client with new randomly assigned
> port (i.e. 1616) for establishing connection. Since this port 1616 is
> not open by firewall, the packet from client on its way back to server
> dies and client receives a message "lost connection."
> Picture: Client -> server-> client-> FW and "lost connection."
>
> After:
> I put this use_shared_socket=true into registry, the message on client
> machine is "no listener"
> But I know that there is listener! I can connect to database from my
> own client machine, which is inside firewall. And I can see listener up
> and running in LSNRCTL STATUS
> Why "no listener" ?!!!
>
>
>
Received on Mon Oct 18 1999 - 06:12:25 CDT