Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
Java
driver for LAN access
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Rogan Dawes, post: 1571279"] As far as I know, neither. Unless Novell servers also use the SMB file transfer protocol (which I think they don't - AFAIK, they use NCP) Note the differences between Samba and jCIFS: jCIFS is a mainly CLIENT side implementation of the SMB protocol. Samba is a mainly SERVER side implementation of the SMB protocol. i.e. jCIFS provides an API that allows you (or your application) to connect over the network to an SMB shared folder, and access resources on it. Samba on the other hand, allows you to share a folder on e.g. a Unix server to SMB clients (Windows workstations, jCIFS apps, etc) There are two ways you can approach this, I think. If your fax server is dropping files in a Windows Shared Folder, and your app running on e.g. a Unix server wants to retrieve those files, wherever they are, I'd say you want to use jCIFS. If your fax server can drop files onto a network share (which there is no real reason why it shouldn't, I guess), you may want to use Samba on your Unix server to provide that network share, and then simply access the files in the underlying disk/directory using the standard Java File API Personally, I'd probably lean towards using jCIFS, because it means that there is less configuration required on your Windows host. Samba is not always the most trivial application to get working. Good luck. Rogan [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
Java
driver for LAN access
Top