<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="Section1">
<p class="MsoNormal">A long winded question(s) on DFS and JCIFS. Essentially, I am looking to understand how JCIFS works in a Domain-based DFS system. I am new to both JCIFS and DFS, so please excuse my ignorance if I completely miss the boat.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Setup:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Domain: company.com<o:p></o:p></p>
<p class="MsoNormal">DNS servers that resolve to company.com when doing a nslookup on the Linux side of the house:<o:p></o:p></p>
<p class="MsoNormal"> server1<o:p></o:p></p>
<p class="MsoNormal"> server2<o:p></o:p></p>
<p class="MsoNormal">DFS Namespace server: Server3<o:p></o:p></p>
<p class="MsoNormal">DFS Root: <a href="file:///\\company.com\dfs">\\company.com\dfs</a><o:p></o:p></p>
<p class="MsoNormal">File I would like to retrieve via JCIFS: <a href="file:///\\company.com\dfs\test\test.txt">
\\company.com\dfs\test\test.txt</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In Windows:<o:p></o:p></p>
<p class="MsoNormal">Going to <a href="file:///\\company.com\dfs\test.txt">\\company.com\dfs\test.txt</a> results in the file being accessible.<o:p></o:p></p>
<p class="MsoNormal">Going to <a href="file:///\\server1\dfs\test.txt">\\server1\dfs\test.txt</a> results in the file NOT being accessible<o:p></o:p></p>
<p class="MsoNormal">Going to <a href="file:///\\server2\dfs\test.txt">\\server2\dfs\test.txt</a> results in the file NOT being accessible<o:p></o:p></p>
<p class="MsoNormal">Going to <a href="file:///\\server3\dfs\test.txt">\\server3\dfs\test.txt</a> results in the file being accessible<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Utilizing JCIFS to retrieve this file with the example Get.java, is the following (loosely) true? I say loosely because I’m sure there is plenty more going behind the scenes, I’m just generalizing.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">JCIFS will resolve strsoftware.com and determine that it’s made up of server1 and server2.<o:p></o:p></p>
<p class="MsoNormal">JCIFS will try to retrieve the file from server1 and fail, return Network name not found exception because the file is truly not accessible on that server because it is not a namespace server.<o:p></o:p></p>
<p class="MsoNormal">JCIFS will try to retrieve the file from server2 and fail, return Network name not found exception because the file is truly not accessible on that server because it is not a namespace server.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Setup 2:<o:p></o:p></p>
<p class="MsoNormal">Domain: company.com<o:p></o:p></p>
<p class="MsoNormal">DNS servers that resolve to company.com when doing a nslookup on the Linux side of the house:<o:p></o:p></p>
<p class="MsoNormal"> server1<o:p></o:p></p>
<p class="MsoNormal"> server2<o:p></o:p></p>
<p class="MsoNormal">DFS Namespace server: Server3 AND Server2<o:p></o:p></p>
<p class="MsoNormal">DFS Root: <a href="file:///\\company.com\dfs">\\company.com\dfs</a><o:p></o:p></p>
<p class="MsoNormal">File I would like to retrieve via JCIFS: <a href="file:///\\company.com\dfs\test\test.txt">
\\company.com\dfs\test\test.txt</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In Windows:<o:p></o:p></p>
<p class="MsoNormal">Going to <a href="file:///\\company.com\dfs\test.txt">\\company.com\dfs\test.txt</a> results in the file being accessible.<o:p></o:p></p>
<p class="MsoNormal">Going to <a href="file:///\\server1\dfs\test.txt">\\server1\dfs\test.txt</a> results in the file NOT being accessible<o:p></o:p></p>
<p class="MsoNormal">Going to <a href="file:///\\server2\dfs\test.txt">\\server2\dfs\test.txt</a> results in the file being accessible<o:p></o:p></p>
<p class="MsoNormal">Going to <a href="file:///\\server3\dfs\test.txt">\\server3\dfs\test.txt</a> results in the file being accessible<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Utilizing JCIFS to retrieve this file with the example Get.java, is the following (loosely) true? I say loosely because I’m sure there is plenty more going behind the scenes, I’m just generalizing.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">JCIFS will resolve strsoftware.com and determine that it’s made up of server1 and server2.<o:p></o:p></p>
<p class="MsoNormal">JCIFS will try to retrieve the file from Server1 and fail, return Network name not found exception because the file is truly not accessible on that server because it is not a namespace server.<o:p></o:p></p>
<p class="MsoNormal">JCIFS will try to retrieve the file from Server2 and succeed because the file is truly accessible from the server as it is a namespace server.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The above examples have been my experience and I just want to make sure that I’m not missing something. In the end, for a file to be accessible in this situation, at least one of the hosts that are resolved via nslookup or dig must be
a namespace server. Correct?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Brent<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>