Davenport Troubleshooting Guide

This document provides resources for resolution of issues with Davenport. If you encounter an issue that this article cannot help you solve, please post a description to the jCIFS mailing list at jcifs@lists.samba.org.

General Steps for Resolution

The following are some good first steps to isolating and resolving any problems you may encounter. It is recommended that you try at least some of these before reporting an issue (if these steps don't resolve the problem, the information gathered will be useful in further troubleshooting).

1. Ensure you are running the latest version of Davenport

The Davenport download area is at:

http://sourceforge.net/project/showfiles.php?group_id=78146

If the problem you are experiencing is listed in the change log, there is an excellent chance it has already been fixed. If you are not running the current version, it is recommended that you upgrade in any case; the issue may have been resolved even if not noted in the change log.

2. Check your configuration

Look over the settings configured in Davenport's deployment descriptor ("web.xml"). Refer to the Davenport Configuration Reference for details.

3. Check your WebDAV client

If possible, determine whether the issue is Davenport-specific or a symptom of the WebDAV client being used. An excellent resource for known problems with the Microsoft Web Folder WebDAV clients can be found here:

http://greenbytes.de/tech/webdav/webfolder-client-list.html

4. Check your Servlet container

Davenport ships with the Jetty Servlet container, and has also been extensively used under Tomcat. Both of these containers are freely available; if possible, try running Davenport under either of these to help determine if your issue is container-related.

What To Do Next

If you've tried the above with no success, please send a message describing the issue you are encountering to the jCIFS mailing list:

jcifs@lists.samba.org

Include as much of the following as possible:

A detailed description of the problem.
Detailed instructions on how the issue can be reproduced.
A description of your client (web browser or WebDAV client and version).
A description of your Servlet container (type and version).
A description of your SMB/CIFS servers (Samba vs. Windows, version).
Attach your deployment descriptor ("web.xml") if possible, but remember to remove any sensitive information before sending it .

You can also submit a bug report on the Davenport SourceForge site, if you like; but you will likely receive a much faster response from the mailing list.

If it is determined that a network issue may be causing the behavior, a Davenport or jCIFS developer may request a packet capture. This is a recording of network traffic, and is an extremely useful troubleshooting tool. Packet captures may contain passwords or other sensitive information, and should not be sent to public mailing lists . If a capture is required, it should be sent to the developer directly.

Instructions for obtaining a packet capture can be found at:

http://jcifs.samba.org/src/docs/capture.html

Davenport captures should ideally be run on the Davenport server; in a typical scenario, the following ports should be captured:

8080	The default Davenport HTTP/WebDAV port; this port services Davenport clients directly.
137	NetBIOS Name Service; used for NetBIOS name resolution.
138	NetBIOS Datagram Service; used for delivering NetBIOS datagrams via UDP.
139	NetBIOS Session Service; used for TCP NetBIOS traffic (including SMB).
445	SMB/CIFS; used for SMB traffic.

If you are using "tcpdump", the proper command would be:

    tcpdump -s 0 -w davenport.pcap 'port 8080 || 137 || 138 || 139 || 445'

This should produce the packet capture file "davenport.pcap".