[no subject]

On Saturday 10 January 2004 03:11 pm, James P. Kinney III wrote:
> No. If all they are doing is downloading a file from an internet server,
> then let use and http get.
>
> If you need more complicated access then consider setting up a wins
> server so the users can find the machine and it's shares.
>
> On Sat, 2004-01-10 at 13:05, David Hamm wrote:
> > Are you saying you can mount shares or access directories and files via
> > HTTP in the same manner as SMB?  The SMB users need the full
> > functionality of an SMB share.
> >
> > On Saturday 10 January 2004 12:14 pm, James P. Kinney III wrote:
> > > Try a login authenticated web access.
> > >
> > > On Sat, 2004-01-10 at 11:30, David Hamm wrote:
> > > > Hello,
> > > >
> > > > I have an FTP server sittting on the Internet.  One group of users
> > > > uploads files via FTP the other group downloads those files via SMB.
> > > > Securing SMB communications in most cases is handeled by listing the
> > > > SMB users's IP address in an IPTables rule with a -j ACCEPT.  But
> > > > recently I gained an SMB user an ALLTel's network and ALLTel blocks
> > > > port 135.  The only options I can come up with is eithher FreeSwan or
> > > > PopTop and from recent experiences I'm not excited about using
> > > > either.  I wonder if I could run SMB on another port? Under Linux I
> > > > don't see a problem but the Windows workstations mounting the share
> > > > can't be modified since they also participate in an SMB based LAN. 
> > > > Any suggestions are welcomed.
> > > >
> > > > Thanks.
> > > >
> > > > _______________________________________________
> > > > Ale mailing list
> > > > Ale at ale.org
&gt; &gt; &gt; &gt; <a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
&gt; &gt;
&gt; &gt; _______________________________________________
&gt; &gt; Ale mailing list
&gt; &gt; Ale at ale.org
&gt; &gt; <a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00386" href="msg00386.html">[ale] SMB options</a></strong>
<ul><li><em>From:</em> jkinney at localnetsolutions.com (James P. Kinney III)</li></ul></li>
<li><strong><a name="00401" href="msg00401.html">[ale] SMB options</a></strong>
<ul><li><em>From:</em> mhw at wittsend.com (Michael H. Warfield)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00374" href="msg00374.html">[ale] SMB options</a></strong>
<ul><li><em>From:</em> ale at spinnerdog.com (David Hamm)</li></ul></li>
<li><strong><a name="00379" href="msg00379.html">[ale] SMB options</a></strong>
<ul><li><em>From:</em> ale at spinnerdog.com (David Hamm)</li></ul></li>
<li><strong><a name="00381" href="msg00381.html">[ale] SMB options</a></strong>
<ul><li><em>From:</em> jkinney at localnetsolutions.com (James P. Kinney III)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00383.html">[ale] Radio-frequency identification (RFID) chips</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00385.html">[ale] Radio-frequency identification (RFID) chips</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00381.html">[ale] SMB options</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00386.html">[ale] SMB options</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00384"><strong>Date</strong></a></li>
<li><a href="threads.html#00384"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>