Subject: | Re: oplocks etc
| Date: | Tue, 7 Jan 2020 08:35:32 -0500
| From: | "Steven Green" <greens@diamondsg.com>
| Newsgroups: | pnews.paradox-development
|
we have everyone in the main building connected directly, and the folks
across the street in the warehouse using VPN / TS.. remotely, I can dial
into an old Dell tower and/or the new TS setup
I don't fully understand all this new "SMB" stuff and the ways they've
changed the oplocks registry stuff, so I don't know what might be related to
the mixed environment, and what might just be related to the newer Server
versions
we're seeing these "file access" class of errors too often.. we've had
several instances of SEVERAL tables going south at once.. probably
two-thirds of it is just the TS side, with the old side humming along fine..
but some of it is the same stuff, on the old side
this is what we get, for trying to keep paradox running in 2020 (sigh)
--
Steven Green
Myrtle Beach, South Carolina, USA
http://www.OasisTradingPost.com
Collectibles and Memorabilia
Vintage Lego Sets and Parts
- and Paradox support, too
"Tom Krieg" wrote in message news:5e13cdd1@pnews.thedbcommunity.com...
Steven,
I've never had that situation, it was either all TS or all local server.
(The TS server was accessed via a VPN)
You would probably need local share turned on, the net file on the TS
server to be shared by everyone and I suspect you would need
write-behind cacheing turned off on the server because local
workstations can break the connection between Paradox and the tables.
On 7/01/2020 12:06 am, Steven Green wrote:
>
> Tom.. local share OFF?
>
> Tom.. what complications come from the combination of local / TS access?
>
> --
>
|