<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:m="http://schemas.microsoft.com/office/2004/12/omml" 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 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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=WordSection1><p class=MsoNormal> One of my filepro customers asked me if they could spool their filePro reports, forms and spreadsheets directly to SMB shares on their local network from their SCO Openserver 6 box. They want to do this because their staff wants to work remotely from home more days each week and they want to make the remote experience as seamless as possible.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> They are running filepro 5.7.03.03D4. They are also running Facetwin terminal emulator on their Windows workstations (mostly Win 7 yet, some Win 10).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> Their Windows techs gave me a sample SMB path to the Windows Server 2012 box that runs the RDP sessions for their home (remote) users: \\internal.xyzcorp.com\Users\Mike\Reports<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> If there is an issue using the FQDN, the static IP for internal.xyzcorp.com Windows Server 2012 is 172.16.104.20 <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> They also gave me a user name and password for Mike’s share. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> Currently each user can choose to spool reports to their user subdirectory (IE; /usr/Mike/Reports) on their SCO server. The reports end up with unique names like “statement-JonesCorp-98765” where the 98765 is the “$$” process ID.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> When the users want to pull all their forms over to their Windows Desktop to review and print them, they have an icon on their desktop that uses a little FTP script that I wrote to pull only the new report names (those reports not already in a folder on their desktop) off of the Unix server and onto their RDP desktops. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> This system works OK and the users are happy with it. However, the 3<sup>rd</sup> party guys who maintain their Windows network keep badgering me about why the users have to FTP the reports to their desktops. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> This FTP thing was a work-around I came up with several years ago to enable their staff to work from their homes. The users connect to the main office via a Fortinet VPN, then log into an RDP session of Windows 7. From there, the FTP script I wrote works just fine to connect to to their SCO server at 172.16.104.18 and pull their files over to their RDP workstation session. I converted some of the most used reports to PDF’s to eliminate viewing and printing problems with the different printers each staff person has at home.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> The Windows guys refuse to open a port on their firewall so I can do Facetwin Remote printing. (Even the SP encrypted version of Facetwin isn’t secure enough for them.) Also, occasionally when printing Facetwin reports and the user wants to cancel a report, the print spooler was getting jammed up.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> I’m hesitant to open Samba shares on the server because of all the recent ransomware attacks. I’ve always told them that their SCO Unix machine is pretty well protected against ransomware attacks. I know Facetwin is also capable of making SMB shares. Both Facetwin SMB and Samba are disabled right now...<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> Can I even do what they are asking? Can I just make an entry on the /etc.hosts file and in the SCO print spooler system and ‘print” things to an external network share? <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> Bob Rasmussen: If you think you have an Anzio solution, I would be interested in that. I could probably talk them into buying Anzio licenses; at least for their remote users.<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><o:p> </o:p></p><p class=MsoNormal>Mike Schwartz<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p></div></body></html>