Thank you, Steve!
That just cleaned up a situation which made me look - and feel - like a
dinosaur.
Bruce
------ Original Message ------
Sent: 8/15/2018 6:49:35 PM
Subject: RE: [RBASE-L] - Tip of the Day: Scrutinize Security Software
with R:BASE X/X Enterprise
From: "Steve Johnson" <sjohnson...@sprintmail.com>
To: rbase-l@googlegroups.com
Cc:
To All,
It might be useful for those of you operating in simpler networks
(primarily those operating without a domain server), Microsoft has
deprecated the ability to see the entire network through file explorer.
This is related to the SMB1 protocol which enabled the original Network
Neighborhood in Win 98 and had become a serious security issue in
today’s environment. I discovered this change following a recent
version upgrade in Windows 10 to build 1803 on one desktop where I could
no longer see or connect to our NAS/file server. This should also occur
if one replaces a desktop with a new Win10 machine. Supposedly SMB1 had
been deprecated in earlier builds of Win10, but SMB1 could be turned
on/off. Build 1803 simply removed the ability all together. However,
I have found that the results of the deprecated SMB1 is inconsistent
between individual machines and both Win7 and Win10 probably due to
existing settings/files already in place. If you run into a situation
where you suddenly can’t see or reach a file destination on the network
that was available before, especially following an OS upgrade or new
desktop/laptop using WIN10, this may very well be the cause. The
solution is using UNC Path (with appropriate permissions in place) as
noted by Mike and Dan.
Steve Johnson
From:rbase-l@googlegroups.com [mailto:rbase-l@googlegroups.com] On
Behalf Of Dan Goldberg
Sent: Friday, August 10, 2018 1:18 PM
To:rbase-l@googlegroups.com
Subject: RE: [RBASE-L] - Tip of the Day: Scrutinize Security Software
with R:BASE X/X Enterprise
I switched to unc paths a while ago. They work good. Also good for
malware/ransomware protection as they scan mapped drives to put their
bugs in.
Dan Goldberg
From:rbase-l@googlegroups.com <rbase-l@googlegroups.com> On Behalf Of
mike.rams...@aksteel.com
Sent: Friday, August 10, 2018 9:06 AM
To:rbase-l@googlegroups.com
Subject: Re: [RBASE-L] - Tip of the Day: Scrutinize Security Software
with R:BASE X/X Enterprise
Thank you, Razzak, for this very timely information.
Our company upgraded our corporate security software to the most recent
version and it created some havoc for me. This also coincided with some
recent Windows Updates.
Configuring the software per Razzak's recommendations has greatly
improved the performance of my databases and programs. I'm using
R:BASE X Enterprise
One issue that came up involved references to mapped network drives
(such as T:\, U:\, etc.) versus referring to them by their full UNC.
I've had to replace references to mapped drives with the full UNC
(\\host-name\share-name\file_path
<file:///\\host-name\share-name\file_path>.
Before doing this I was getting errors like:
Invalid file spec, or unable to access directory. (2561)
Invalid destination filespec (2282)
Invalid source filespec (2281)
Hopefully my experience and solution may help someone else.
Kind regards.
Mike Ramsour
AK Steel Coshocton Works
Quality Department
Phone: 740-829-4340
Cell: 740-502-1659
From: "A. Razzak Memon" <raz...@rbase.com>
To: rbase-l@googlegroups.com,
Date: 07/26/2018 11:21 AM
Subject: [RBASE-L] - Tip of the Day: Scrutinize Security Software
with R:BASE X/X Enterprise
Sent by: rbase-l@googlegroups.com
--------------------------------------------------------------------------------
Thursday, July 26, 2018
Tip of the Day: Configuring Security Software with R:BASE X/X Enterprise
Product.......: R:BASE X and R:BASE X Enterprise (Version 10)
Build.........: 10.0.3.20710 or higher
Keywords......: Environment, Multi-User, Network Configuration
Section.......: General
Client and server computers may have one or more security-based software
(anti-virus, anti-malware, anti-spyware) utilities installed.
Common to security programs is the ability to define "exceptions" for
program files and folders where scans should be ignored.
Including R:BASE within the exception area is required in order maintain
performance.
If R:BASE itself is scanned each time it is launched, and the contents
of
the database and temporary files are halted and scanned each time they
are
created/accessed, users will see much slower response times when running
R:BASE, making connections, and accessing files.
It is important to add exceptions to three areas of the R:BASE program:
01. - Program Executable
For R:BASE X Enterprise, the executable name is RBGXE.exe. The default
installation folder is "C:\RBTI\RBGXE".
For R:BASE X, the executable name is RBGX.exe. The default installation
folder is "C:\RBTI\RBGX".
For R:Compiler/Runtime for R:BASE applications, the compiled executable,
Runtime executables, and DLLs (all of which are usually stored onto the
shared network location) must be defined as exceptions.
02. - Database Files
For R:BASE X Enterprise, the database files are the .RX1, .RX2, .RX3,
and
.RX4 files.
For R:BASE X, the database files are the .RB1, .RB2, .RB3, and .RB4
files.
Although wildcard may be accepted, adding each file extension
individually
as an exception may be more appropriate.
03. Temporary Scratch Files
When R:BASE is launched, it will create three .$$$ temporary files.
After
performing certain actions, additional files may be created, and the
existing files will increase and decrease in size.
Add the *.$$$ files as an exception.
It is also recommended to scrutinize the security product, specifically
how
it handles exceptions!
Some security products treat exceptions differently, where scans (manual
and scheduled) apply for "folder" exceptions, however real-time
(application
control) applies specifically to "file" exceptions.
The above could mean that all folder exceptions applied in a security
product
do not prevent the R:BASE executable from being scanned when launched,
nor
do the exceptions prevent the database files from being scanned while
accessed!
You and your staff should see the expected R:BASE performance after
performing
the above security software review.
Very Best R:egards,
Razzak.
https://www.rbase.com <https://www.rbase.com/>
http://www.facebook.com/rbase/
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google
Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Confidentiality Notice
This message is intended exclusively for the individual or entity to
which it is addressed and may contain privileged, proprietary, or
otherwise private information.
If you are not the named addressee, you are not authorized to read,
print, retain, copy or disseminate this message or any part of it. If
you have received this message in error, please notify the sender
immediately by e-mail and delete all copies of the message.
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google
Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google
Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google
Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
