<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">We have an internal lab network for old
PCs, and a file server with two ethernet ports- one looking in,
and the other looking out. Lab users dump their data, images, etc
on the file server, and then later reach over to retrieve their
stuff. In a few cases we have an even simpler setup: wire up a new
Windows box next to the old one, then use the new box as the Z:
drive for the old WinXP instrument. The user can then turn to the
new box to transfer files to network storage. That means the new
box must have two ports. We've been using little Intex Nuc boxes,
since they are cheap and come with one wireless and one wired
port. We use the wired ethernet for the local connection, and the
wireless for connection to the campus network.<br>
<br>
It's difficult to shut off the USB ports, since they are used for
the keyboards and mice. We put stickers over the unused USB ports,
but sometimes people use them anyway. Short of gluing the
connectors I don't have any good ideas about how to ban USB
sticks.<br>
<div class="moz-signature"> <br>
<font size="-2">--------------------------------<br>
Michael Rooks <br>
Yale Institute of Nanoscience and Quantum Engineering <br>
<a href="http://nano.yale.edu">nano.yale.edu</a>
</font>
<br>
<br>
<br>
<br>
</div>
On 09/10/2018 01:28 PM, Dennis Culver wrote:<br>
</div>
<blockquote
cite="mid:165c4871c51-1ec6-107dd@webjas-vaa215.srv.aolmail.net"
type="cite"><font color="black" face="arial" size="2">Hello Kevin,
<div>I run into this issue with systems running WIN 3.1 &
Win 98. On the process equipment, disable USB support in BIOS
so your process systems don't get infected and allow a "print
to file" option as this isn't bi-directional. Then, just
install a wireless network card to each system PC so that
those files could be dumped to a dedicated PC for file
retrieval or directly sent to each students Email address
through that PC. There is an inexpensive program called Nitro
Reader that can create *.pdf files at your source PC's as well
so there aren't any compatibility issues with software. </div>
<div><br>
</div>
<div>Dennis<br>
<br>
<br>
<div
style="font-family:arial,helvetica;font-size:10pt;color:black">-----Original
Message-----<br>
From: Kevin McPeak <a class="moz-txt-link-rfc2396E" href="mailto:kmcpeak@lsu.edu"><kmcpeak@lsu.edu></a><br>
To: labnetwork <a class="moz-txt-link-rfc2396E" href="mailto:labnetwork@mtl.mit.edu"><labnetwork@mtl.mit.edu></a><br>
Sent: Mon, Sep 10, 2018 4:56 am<br>
Subject: [labnetwork] Getting files off older computers<br>
<br>
<div
id="AOLMsgPart_1.2_130495a5-8bf5-422a-b203-423b4ca14cdc">
<div class="aolReplacedBody">
<div dir="auto">Dear Colleagues,<br>
<br>
Here at the LSU cleanroom, we have several older
computers (e.g Win XP and Win 7) which are not allowed
on the network. These computers are connected to
instruments <span style="font-family:sans-serif">(e.g.
SEM and AFM)</span> that we often need to get files
from. Unfortunately, the instruments do not run on Win
10 (our network administrator won't allow Win 7 on the
network as well).
<div dir="auto"><br>
</div>
<div dir="auto">The current protocol to get images
etc. off these older computers is to use a cleanroom
owned USB stick to move the file to one computer in
the cleanroom which is on the network.
<div dir="auto"><br>
</div>
<div dir="auto">I do not like this protocol. It is
very difficult to stop users from using their own
USB stick, which could be infected. Also USB
sticks grow legs.</div>
<div dir="auto"><br>
</div>
<div dir="auto">I suspect other facilities on the
list have faced these same challenges. I am
curious how you have resolved them. Thank you in
advance for your input!</div>
<div dir="auto"><br>
</div>
<div dir="auto">Regards,</div>
<div dir="auto">Kevin<br>
<br>
-- <br>
Kevin M. McPeak<br>
Assistant Professor<br>
Louisiana State University<br>
Dept. of Chemical Engineering<br>
3307 Patrick Taylor Hall<br>
Baton Rouge, LA 70803<br>
email: <a moz-do-not-send="true" target="_blank"
rel="noopener noreferrer"
href="mailto:kmcpeak@lsu.edu">kmcpeak@lsu.edu</a><br>
phone: 225-578-0058<br>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
labnetwork mailing list<br>
<a moz-do-not-send="true"
href="mailto:labnetwork@mtl.mit.edu">labnetwork@mtl.mit.edu</a><br>
<a moz-do-not-send="true"
href="https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork"
target="_blank">https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork</a><br>
</div>
</div>
</font>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
labnetwork mailing list
<a class="moz-txt-link-abbreviated" href="mailto:labnetwork@mtl.mit.edu">labnetwork@mtl.mit.edu</a>
<a class="moz-txt-link-freetext" href="https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork">https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork</a>
</pre>
</blockquote>
<br>
</body>
</html>