The Database as a Networked Server - Implementing Database Security and Auditing - page 79

Figure 3.13
Protocol definitions
using Oracle Net
Manager.

You can also use the Oracle Net Manager to select a listener and add as
many addresses as you need—each address definition is shown as a tab on
the right pane and each defines a protocol, as shown in Figure 3.13.
On the client side, you need to have appropriate entries in tnsnames.ora .
You can edit the file manually or use the Oracle Net Configuration Assistant.
In the starting screen (Figure 3.11), select Local Net Service Name configura-
tion and click Next. You can then select to add, reconfigure, delete, rename,
or test an entry. Then you select the network protocol for that service name,
as shown in Figure 3.14.

3.4.4 Implementation options: Use TCP/IP only

As mentioned in the previous subsection, each vendor allows you to disable
or enable the various protocols on which the server is listening. Unless you
have an unconventional (i.e., non-TCP/IP) environment, my suggestion is
that you disable all protocols except TCP/IP.
Another protocol that I've found to exist in the real world is Named
Pipes, and you've already seen that you can enable Named Pipes with any of
the major database vendors. Named Pipes uses a generic protocol called
Server Message Block (SMB, which is explained further in Appendix 3.B).
SMB is a stable protocol that has proven itself through the years. In the