Symantec Security 5600 Series, Security 5400 Series,Clientless VPN 4400 Series, Administration Manual

Page: 196 / 861

196 Defining your security environment
Controlling full application inspection of traffic
Configuring additional CIFS and NBDGRAM features
The security gateway’s ability to handle and process CIFS and NBDGRAM traffic can be modified to suit
your specific needs. This section includes the additional tasks you have available to further define how
the security gateway supports CIFS and NBDGRAM. Each task includes the appropriate configuration
steps needed. This section assumes that you have already configured the security gateway to pass CIFS
and NBDGRAM traffic.
Review the following tasks to determine if any additional configurations are needed for CIFS and
NBDGRAM.
■
“Modifying the timeout period for inactive CIFS connections” on page 196
■
“Creating trace files of CIFS connections” on page 196
■
“Logging UDP broadcasts” on page 197
■
“Enabling filtering through mail slots” on page 197
Modifying the timeout period for inactive CIFS connections
CIFS connections will timeout and become unusable after a period of 300 seconds (5 minutes). You
should increase the timeout period if you find that your connections are timing out too quickly during
average use.
Prerequisites
Complete the following task before beginning this procedure.
■
“Configuring access for CIFS and NBDGRAM traffic” on page 194
To modify the timeout period for inactive CIFS connections
1 In the SGMI, in the left pane, under Assets, click Proxies .
2 In the right pane, on the Proxies tab, click the CIFS proxy and then click Properties .
3 In the Proxy Properties dialog box, on the General tab, in the Timeout text box, type the new
timeout value.
4
Click OK .
5 Optionally, do one of the following:
■
To save your configuration now and activate later, on the toolbar, click Save .
■
To activate your configuration now, on the toolbar, click Activate .
When prompted to save your changes, click Yes .
Related information
For related information, see the following:
■
“Proxy Properties: CIFS—General tab” on page 699
Creating trace files of CIFS connections
When troubleshooting CIFS connections, you can configure the security gateway to create a separate
log file for CIFS connections only. You may want to do this if you want to track what is happening to
CIFS packets as they pass through the security gateway, or you might simply want an audit trail for all
CIFS connections.
Note:
The CIFS trace file is normally written to /var/log/sg/cifsd.log.