Network disconnects

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a small 25 user Windows 2003 network. One file server which is also a
domain controller. Users are mapped to an app directory where they are
running quickbooks from the network. Everyone once in awhile when a user is
in Quickbooks, they get an error saying they cannot access the quickbooks
file. When I check the workstation they are still connected to the network.
It seems like a momentary disconnection.

I first thought it was my switches, but I replaced them wth different
hardware and the problem did not go away. Has anyone seen disconnection
problems with mapped drives with Windows 2003 Server?

Paul
 
Nothing is wrong. This is normal when running Applications this way when
applications were not meant to be run this way,...as Quickbooks was not.
Quickbooks is a "single-user" applicaation designed to run locally on a
single machine running a single-user session.

Running it as you are it is perfectly normal for users to "conflict" when
trying to access the same resource at the same time. This is the big
differce between single-user applications and multi-user / client-server
applications that are designed to be run in a multi-user / multi-access
environment.

Also, Mapped drive *do* timeout with inactivity,...and they *do* sometimes
"lag" a bit when reconnecting with new activity,...sometimes they fail to
reconnect at all. Mapped Drives are horrible,...they are a "thing of the
past",...and all effort should be made to eliminate them on modern networks.
 
Let me clarify. I am using the multi-user version of Quickbooks. Also the
app is not running off the server, it is loaded locally on the user desktop.
The data files are located on the network. I described this wrong.

I found found a Knowledge Base article which tells you how to shut off the
regular disconnection of a mapped drive, but this is not working.

Phillip Windell said:
Nothing is wrong. This is normal when running Applications this way when
applications were not meant to be run this way,...as Quickbooks was not.
Quickbooks is a "single-user" applicaation designed to run locally on a
single machine running a single-user session.

Running it as you are it is perfectly normal for users to "conflict" when
trying to access the same resource at the same time. This is the big
differce between single-user applications and multi-user / client-server
applications that are designed to be run in a multi-user / multi-access
environment.

Also, Mapped drive *do* timeout with inactivity,...and they *do* sometimes
"lag" a bit when reconnecting with new activity,...sometimes they fail to
reconnect at all. Mapped Drives are horrible,...they are a "thing of the
past",...and all effort should be made to eliminate them on modern networks.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Paul C. Charleston said:
I have a small 25 user Windows 2003 network. One file server which is also a
domain controller. Users are mapped to an app directory where they are
running quickbooks from the network. Everyone once in awhile when a user is
in Quickbooks, they get an error saying they cannot access the quickbooks
file. When I check the workstation they are still connected to the network.
It seems like a momentary disconnection.

I first thought it was my switches, but I replaced them wth different
hardware and the problem did not go away. Has anyone seen disconnection
problems with mapped drives with Windows 2003 Server?

Paul
Click to expand...
Click to expand...
 
Paul C. Charleston said:
Let me clarify. I am using the multi-user version of Quickbooks. Also the
app is not running off the server, it is loaded locally on the user desktop.
The data files are located on the network. I described this wrong.
OK

I found found a Knowledge Base article which tells you how to shut off the
regular disconnection of a mapped drive, but this is not working.
Click to expand...

See if you can run it with the UNC path instead of a drive path.
\\machinename\sharename\foldername
 
You'd have to call MS and reference the article. They would try to verify
the situtation to see if it required the patch. Due to compatibiliy issues
some patches are only given out on a case by case basis because they have to
potential to cause other problems,...more so than the publicly released ones
do. There is no charge for patch or SP related calls.
1-800-936-4900
 
Back
Top