Troubleshooting guide

Appendix A: State Tables for VPN-1/FireWall-1 4.0 DCE/RPC tables
Advanced Technical Reference Guide 4.1 • June 2000 171
DCE/RPC tables
dcerpc_maps table
The dcerpc_maps table relates to the DCE/RPC port mapper’s replies.
Example
attributes: sync refresh expires 86400 keep
The dcerpc_maps table uses the following format:
Its keys are the Endpoint Mapper’s IP address and the GUID requested by the client (which takes 4 fields, since
it is 16 bytes long), and the value is the port of the port mapper’s response.
See definition of a key in “The basic structure of a connection in a table entry” on page 142)
dcerpc_binds table
The dcerpc_binds table lists the GUID requested in the port mapper connection.
Example
attributes: sync refresh expires 3600
The dcerpc_binds table uses the following format:
The keys are the connection parameters, and the values are the requested GUID.
See definition of a key in “The basic structure of a connection in a table entry” on page 142
dcerpc_portmapper_requests table
The dcerpc_portmapper_requests table holds requests to the DCE/RPC port mapper that are still not answered.
Example
attributes: sync expires 20
The dcerpc_portmapper_requests table uses the following format:
Its keys are the connection’s parameters and the requested GUID.
See definition of a key in “The basic structure of a connection in a table entry” on page 142
dcom_objects table
The dcom_objects table holds data on the responses to DCOM remote activation requests.
Example
attributes: sync refresh expires 86400 keep
The dcom_objects table uses the following format:
<source IP address, destination IP address, destination port given by DCERPC portmapper, IP protocol, 4
ClassID fields; time left/total time>