Disk or Network error on Terminal Server

An unusual spin to this recurring disk or network error in a Terminal
Server environment. Access 2000, Terminal Server 2000, file server is
windows 2000. All users have a separate copy of the front end db,
everyone accesses the back-end db via a network share. To preface,
non Terminal Server users (4 or 5 in office) never have this problem.
There are two Terminal Servers running win 2000, both basically
identical. This error affects users on both of them. Problem is
intermittent, and does not target specific users or back-end dbs.
Several times a week, various users will pull up a form in access, and
a combo or subform will be blank. With error trapping, or if pulling
up a form where the recordsource is actually based on the backend db
affected, the user will receive the DISK OR NETWORK ERROR. Having the
user close the database and re-open, even pulling a new copy of the
database, in most cases does not alleviate the problem. Having users
logout of Terminal Server and log back in somtimes works, sometimes
not. Hard to nail down what the problem is really tied to.

Here's the kicker: If the user receives the error, then opens Windows
Explorer, navigates to the db file, right-clicks the .mdb file and
selects PROPERTIES, there is usually a 1 second pause, the properties
windows for the db opens, and the user's database access is now ok.
They can immediately refresh or close/re-open the form, and the data
shows correctly. This works EVERY time.

I would really like to figure out what the problem could be, but i'm
stuck. I have verified that all jetdb versions are the same across
all systems (TS and workstations). When this problem occurrs, the
user's connection (read/write etc) to other dbs in the same shared
drive are not affected.
.

Relevant Pages

  • Re: Multi-user access of an Embedded Windows System ?
    ... First off, EWF is available ... > only for Windows XP Embedded, and is not intended to be used with XP Pro or ... > install, and in this case it sounds like the system would be best suited ... it looks to me like what you're referring to is the Terminal Server ...
    (microsoft.public.windowsxp.embedded)
  • Re: Event ID 1000 (Userenv)
    ... Maybe it's time to install those 2 hotfixes that I mentioned in my ... MCSE, CCEA, Microsoft MVP - Terminal Server ... it takes longer that their profile is loaded. ... Windows 2000 SP4: ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Newbie Setup Question
    ... Microsoft MVP - Terminal Server ... RDP Client to connect to the TS of your choice. ... Windows 2003 Server running as a Terminal server. ... login an go directly to the TS without the user manually launching RDP ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Server 32bit /PAE vs 64bit
    ... 935649 - Error message when you try to log on to a Windows Server ... MCSE, CCEA, Microsoft MVP - Terminal Server ... memory and that our applications are actually addressing it ... I have seen thru the task manager performance tab our dl380 ...
    (microsoft.public.windows.terminal_services)
  • Re: Access to Terminal Services server via internet RDP
    ... A Draytek Vigor 2600 ADSL Router with address 192.168.0.1 ... In my initial scenario port 3389 was forwarded using routing to Windows 2000 ... I then changed to point to Windows 2003 Terminal Server at 10.0.0.254, ... packets are from public internet and blocks them from Terminal Server. ...
    (microsoft.public.windows.terminal_services)