GeeDee for Windows

Troubleshooting Page - Useful Information

Troubleshooting Page - Useful Information

Previous topic This is the last topic No directory for this topic Expand/collapse all hidden text  

Troubleshooting Page - Useful Information

Previous topic This is the last topic Topic directory requires JavaScript JavaScript is required for expanding text JavaScript is required for the print function Mail us feedback on this topic!  

Resolving network and other file problems


This page covers info from as far back as Windows 98/NT to present day. Information is still relevant.


Last updated January 2017  (Added more Win8/10/Win2008/12 SMB2 & GPO Drive Information)


Network / file problems, can be caused by one or more of the following:


   * Kinked or damaged cable - just because it looks ok doesn't mean it is - test it or swap it out for another one you may have.

   * Cable running close to a fluorescent light ballast (fixture)

   * Loose connector/plug on cable

   * Old "worn out" cables, particularly coax cables that have been around for years

   * Out of date drivers

   * Bad hub or a bad port on a hub

   * Failed/failing network card

   * Power problems (PLEASE protect your systems with a UPS, power problems are one of the biggest troublemakers we know of. Yes, a UPS might cost $79 to $450 depending on how big a unit you buy, but how much is your computer and a day's worth of business worth? Consider it much less than the time to fix a power-caused mess.

   * Network setup and/or configuration problems

   * Inadvertent shutdowns

   * Shutting down servers while workstations are still in the program

   * Out of date network drivers (even those right out of the box are sometimes a problem)

   * Improper or less than desirable network bindings/settings

   * Loss of network connections caused by server-management-induced timeouts


NOTE: Remember that having backups is a saving grace in the face of file/network problems. Network problems can corrupt your files in a heartbeat. If you have no backups, you are in big trouble (future or present - trouble will occur). Having backups is a responsibility you must take VERY seriously.

GeeDee File Servers: Best Practices & System Requirements - TROUBLESHOOT


Windows configuration recommendations (This is the standard configuration request for all Trust Systems Nationally)

      Sufficient windows user permissions (MODIFY) to the GEEDEE Database Share and local Program folder (IE: C:\GEEDEE). Ensure adequate permissions are setup on the Share tab as well as the Security tab.
     Ensure Windows Sync Centre (Windows Offline Folders) is disabled. Being enabled by default it may direct GEEDEE to an offline version of a data file. We recommend to Reconfigure the GEEDEE Database Share to ensure No files or programs are available offline. (Share Properties > Advanced Sharing > Caching
    Disable User Account Control (UAC).
     Exclude GEEDEE EXEs in the Data Execution Prevention (DEP) List.
     Check the computers network card and configuration
     Ensure the connection is wired using Cat5 / Cat6 cabling standards, connections over WIFI or VPN are not supported by GeeDee.
    Disable QOS.
     Ensure the link speed is at least 100Mbit and that TCP/IPv4 is the only protocol in use (IE: Disable TCP/IP v6). **For Domain Controllers or Exchange Servers we recommend TCP/IP v6 is left as default.
     Ensure the computer is only connected to one physical network.
     Check the type of network card installed on the computer, confirm the correct drivers are installed.
     Under connection properties, disable all power management options to remove control from other programs.
     If running DHCP check how often new TCP/IP addresses are allocated or better yet set to static for easy control.
      Review all screen saver and power saving plans
     Optimise for High Performance.
     Disable items such as hibernation, turning off HDD and Network cards etc.
     Confirm the computer clocks are synchronised to the same time source and within a few seconds of each other.
     Confirm the computer has all of the current Microsoft Updates installed.
      Turn off Disk Compression to optimise disk I/O performance.
      Disable Outlook Security Warnings (Programmatic Access Security settings).

GPO - Mapped Network Drive Issue
Here is some  further information from our recommended IT Group. Please review below.


To determine if this is in place you need to go to Group Policy manager on the domain controller (not local group policy manager).


You may be dealing with a different network issue if there are no drive mapping policies in place via group policy.


The below is a screenshot of Xxxxxxx’s setup. Their old it had it set under a specific policy called ‘Mapped Drives’, but this will vary site-to-site.

Click me to expand!

Drive Disconnects - on the server:
To turn off the autodisconnect feature, open a command prompt with elevate permissions, type the following line, and then press ENTER:
net config server /autodisconnect:-1

on the client:
restart GP or "gpupdate /force"

This KB seems to address it as well.


More information:
Q: Why is the Group Policy (GPO) preference that sets drive mapping not working on Windows 8 and Windows Server 2012 machines?

Dec 6, 2012 John Savill | Windows IT Pro
A: Network drives aren't correctly mapping in Windows 10 & 8 and Windows Server 2012, though the Group Policy setting that mapped them worked on Windows 7 and Windows Server 2008 R2. The solution is to modify the Group Policy preference drive map so that the reconnect option isn't selected (see screen shot below). This enables the drive maps to work on Windows 8 and Windows Server 2012.
It appears that this issue is the same for Windows 10 and Server 2011.

Again, another source reference:
Windows 10 losing mapped drives

ColtsFanMN Oct 15, 2015 at 3:38 AM


I had that problem with Win 7.. seems that MS in its infinite wisdom decided that 'disconnecting' mapped drives if their resources weren't in use (had nothing to do with the workstation use), saved network traffic/load.  I did try the command (via a batch file):


net config server /autodisconnect:-1


this did help in certain cases.. but not all.  So I tried mapping drives in AD via a login script (not in GPO) using the following syntax as an example:


net use f: \\<servername>\<sharename> /persistent:yes


The /persistent:yes flag tells Windows to keep a persistent connection to the share, regardless.  Since I have done that, the drives stay mapped always.  I was not able to get this working via a GPO.. and I know it's preferred by most, but this was my solution.
The issue you are experiencing is the exact same situation experienced at 2 other sites with incorrectly configured Group Policy settings for mapped Network Drives. It is not a persistanent setting at all. The reports from our IT, is that this configuration issue greatly effects, MYOB, Reckon, Quicken and other like products.
Your currently configured settings is an issue between your Server and Windows 10. Hence, the complete drop and failure in communication. It will work fine under Windows 7 but with Windows 10, at irregular intervals throughout the day, your current configurations are instructing the Drive Mappings to completely disconnect and then reconnect.
It is a very weird configuration and one which is typically more suited for server migrations, where one would in fact like to disconnect the drives so that they again can be freshly reconnected to a new mapped drive on a new server. It is all very strange, but it is the exact issue and error messages experienced at the site with this setting.
As requested, can you please forward me a screen shot of your Group Policy settings for the mapped G:\ network drive. The key information is in the Update / Replace and the Reconnect option.
*Note, the UNC path requirement for Trend AV also appears to be missing. If you can forward that information through I will contact and discuss.
As you are the third site to be sent sideways by this configuration for mapped drives, I would love to get a copy of your current properties and  information. I can then confirm and include your information in an email to clients as an issue to watch out for. Thank you!
Sean Darcy



flag_green Opportunistic Locking


It is imperative to disable opportunistic locking on all drives.

Opportunistic locking is a mechanism that Microsoft has chosen to make things faster in a single-user mode but in multi-user mode, it creates locks on data records that are longer to release.


Failure to run the required GeeDee Server or Workstation Installer and further failing to supply the legally required checklists (as per GeeDee Realty Systems Pty Ltd End User Licence Agreement) will result in the integrity of your businesses data potentially being effected.
This is nothing new or different. Nationally, this is also the same request all like software packages enforce as a rule.  * The GeeDee Server & Workstation Installer will automatically supply the required changes.


In all Windows O/S including NT/XP/V/7, Opportunistic Locking must be disabled to prevent data loss

Microsoft has admitted to have problems due to Opportunistic locking.





Disabling Oplocks on Windows Servers

To disable oplocks on a Windows server (a Windows PC that hosts an embedded database table accessed from another PC), the GeeDee Server installer will automatically change or add the following Registry values:


   * HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters EnableOplocks = 0


Disabling Oplocks on SMB2 (Vista, Server 2008, Server 2011).

SMB2 on a Windows Server 2008 or Windows Vista PC hosting embedded database tables, the GeeDee Server installer will automatically change or add the following Registry value:


   * HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters SMB2 = 0


Once SMB2 is disabled, SMB1 will be used again and the methods described above applied to disable oplocks for SMB1.




Disabling Oplocks on Windows Client PCs

To disable oplocks on a Windows client PC (a Windows PC that accesses an embedded database table hosted on another PC), the GeeDee Workstation installer will automatically change or add the following Registry values:


    * HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters OplocksDisabled = 1


MS KB296264 Configuring opportunistic locking in Windows



Windows Workstations XP/V/7

    * Ideally turn off all power saving features.

    * Disable caching/opportunistic locking on all drives. {This is critical. Failure to disable opportunistic locking through the use of the correct and up-to-date GeeDee Realty Systems Pty Ltd installers could result in possible datafile damage, for which the installer/user accepts all responsibility}.

    * DO IT NOW!!




Drivers up to date? Windows networking is subject to a number of problems, MANY of which can be solved simply by installing updated driver software from the manufacturer or (more often) Microsoft. The link below will go to a web page that describes just ONE of the problems in Windows peer-to-peer networking, yet there are several other problems referenced at the bottom of that page. In particular, anyone on Windows 95 needs to get their network drivers and "requestor" updated. and in particular note some problems that can burn you.


Windows NT users - Are you on service pack 6 instead of service pack 6a or another service pack? If so, expect lots of problems. Microsoft has acknowledged that service pack 6 broke a lot of things network-wise. You can get service pack 6a at their site or you can go back to service pack 5, either of which is stable. In addition, do NOT mix service packs on different NT machines on your network. In other words, run all your NT machines on service pack 5 or on service pack 6a, but not a mix of both service packs.



Slow network browsing in Windows

1) Shortcuts in 'My Network Places' make network browsing very slow

2) Explorer randomly locks files

3) Listing the contents of a shared folder is slow - Desktop.ini


CleanRoamingProfile.vbs - VBScript to delete selected files from a roaming profile.

SysInternals - Mark Russinovich - Desktop.ini files fill up the audit event log.

Q904160 - File sharing on the network is slower than expected (WinServer 2003 SP1)

Q885189 - Slow performance from a mapped drive - Windows Server 2003

Q841978 - Explorer.exe stops responding when you use network shortcuts (XP)

Q834350 - Access to network resources is slower

Q822219 - Slow File Server Performance

Q819017 - Long delay before files appear in My Computer (XP)

Q816375 - XP Explorer pane flickers

Q814112 - Network shares open slowly SMB/AntiVirus scanning

Q326549 - Read-only & System attributes for folders

Q321281 - Desktop.ini does not work correctly when you customise the Default Profile

Q320138 - Disable automatic search for network printers and folders (XP)

Q320829 - Increase the Request Size Buffer on the file server - (try between 32 and 64 Kb)

Q319470 - Office2000: Screen response is slow in Save As dialog box in Word

Q315237 - 100-Megabit network packets

Q312403 - Distributed Link Tracking

Q265396 - Slow network performance on a share that uses NTFS

Q245800 - Delay viewing shares (Windows 98/2000)

CleanMgr - Automated cleanup of Temp files, recycle bin

Max Cached Icons - Resize the icon cache



Is your network slow when using a mapped drive letter?

The reason is this: The computer has both TCP/IP and NetBEUI (network protocols, similar to different spoken languages). TCP/IP for the Internet and NetBEUI for the local network. TCP/IP is the default protocol. When connecting to a mapped drive after some idle time, the computer tries to connect first over TCP/IP and times out. Then and only then it tries the NetBEUI connection. Go to the Control Panel > Networks > Bindings. Make NetBEUI as the default protocol.


Is your network slow when using a mapped drive letter? (part 2)

Is the drive mapped to the main computer's drive or to a folder?

If it is mapped to a folder, you will likely see a decrease in performance, often a quite noticeable decrease. We are not sure why this happens, but mapping directly to the drive has been proven time and time again to be faster. We have not discovered the reason for this, despite extended searches of Microsoft's tech database ( ).



Is your network slow?

Recently, we have noticed that the "Windows Indexing Service" has a seriously negative effect on network performance. Turn it off. The indexing service scans your hard disk and indexes the files so that the next time you do a file search, Windows can find the files more quickly. Turn it off. Think about how often you do searches vs how much time you waste waiting on your network. Do a search and do other work while waiting for it. Its just not worth waiting 99% of the time to speed up 1% of your work.


Is your Windows 2003 network slow?

#1 - Get all the Windows 98 machines off of the network. Not just out of your program, but OFF THE NETWORK.


#2 - Get all XP machines on Service Pack 3 and or removed.


#3 - Get Windows 2003 on Service Pack 2 or later.


#4 - Disable SMB On the Windows 2003 Small Business Server, run "gpmc.msc" and make sure the following policies (10 in total) are all 'Disabled' (instead of 'Not defined') in BOTH 'Default Domain Security Policy' and 'Default Domain Controller Security Policy':


NOTE: The policies are under 'Windows Settings' -> 'Security Settings' -> 'Local Policies' -> 'Security Options'.


1) Microsoft network client: Digitally sign communications (always): Disabled

2) Microsoft network client: Digitally sign communications (if server agrees): Disabled

3) Microsoft network server: Digitally sign communications (always): Disabled

4) Microsoft network server: Digitally sign communications (if client agrees): Disabled

5) Network security: LAN Manager authentication level: Send LM & NTLM - use NTLMv2 session security if negotiated


B. Restart the DC and client computer to take effect.


Do some or all computers on your network randomly "die", "go to sleep" or "hang"?

Usually, this is caused by power management being active on the workstation and possibly the server. Power management is a fancy computer geek word for "Windows has settings that turns stuff off when it hasn't been used in a while". Power management is a bad thing on a network. It's great on a laptop at 37,000 feet with 3 hours remaining of your flight, but it's far more trouble than it is worth otherwise. Bottom line issue: You dont want network cards turning off because you haven't moved your mouse for 20 minutes. You don't want your server's hard drive turning off because no one has touched the server keyboard in the last 30 minutes (this might make your workstations just a little bit cranky when they are trying to read stuff on that server's drive). This is exactly what Power Management is supposed to do, but you don't want this to happen when using a networked database. To investigate, go to Start, settings, control panel (XP in "ugly mode" or Windows 2000) or Start, Control Panel (XP in "pretty mode") and double click the Network Connections icon (if that doesn't exist on your computer, you need to find the place where you can change settings on your network cards). Find your network adapter on this screen. Usually it will say something like "Local Area Connection" or "Wireless Connection 1" (if you are ignoring our advice and using wireless). Right click that icon, click properties. When the screen opens, you'll see the name of the network card up near the top, just below the tabs. To the right of that, there is a Configure button. Click it. When the next screen opens, there will almost certainly be a Power Management tab. On that tab, chances are you will see a checkbox that says something like "Allow the computer to turn off this device to save power". Uncheck the box and click OK until you dont have to look at all these network settings anymore. Reboot your PC, hope for the best.


Windows networking

Here is Microsoft's "best place to start" page for dealing with Windows XP issues, including networking issues.


Windows 2003 Server networking;EN-US;winsvr2003


Workstation drive letters "getting the red X" (disconnecting from the main computer)

You can disable this by issuing this command from the DOS command line: net config server /autodisconnect:-1

Before using this command, we suggest you read the Microsoft article that discusses autodisconnect. You can find it here:;en-us;138365


Windows 2000 or Windows XP mapped drives disconnecting for no apparent reason? (showing the red X over the drive in explorer);en-us;138365


Novell Netware problems?

The problem could be your Novell Opportunistic Locking setting. Contact your network person for further details. How to turn it off? Goto Control Panel -> Networks -> Novell Client Properties -> Advanced Settings Tab -> Opportunistic Locking and make sure this is switched off on all client Machines - ALSO Make sure True Commit is ON at each client PC (This should help stop data corruption)


Performance issues are often caused by network protocol "bindings"

Check the following Network protocols basics:


   * Make sure that your default network protocol has no bindings to a virtual device (dialup.....).

   * If you are using TCP/IP and you have dialup on this workstation, try NetBEUI.

   * Try to avoid using IPX and NetBEUI together. IPX gets confused when you have a "chatty" NetBEUI. Removing IPX (if you can) is strongly advised.

   * If you need to examine the network further, check out to get a bird's eye view of what's going on.



Database corruptions, timeouts and other troubles

Another issue is the various ways that Windows9x and NT try to improve performance, often at the price of stability. Sometimes these things work, other times they cause network timeouts because they force additional file operations behind the scenes and those file operations time out (fail). One way to turn one of these items off is to turn off "Synchronous buffer commits". To do this, click Control Panel, System, Performance, File System, Troubleshooting and check the "Disable synchronous buffer commits" checkbox.


Database corruptions, timeouts and other troubles, part II

Further, Windows NT users face issues caused by some performance improvements that NT tries to implement with network applications by 'faking' multiple use of files. Unfortunately, some users experience file corruption because of this. This article is a bit of nerd-speak, but your network person should take a look at it if you are seeing "Access denied" errors on network files when they *know* that the network permissions are set properly.  The topic of this article can also be the cause of database corruption and network timeouts (drive not available messages and the like).



Windows 2000 and Windows XP users - Turn off write caching

You need to disable the "write-behind cache". When the program ask to save the data, the data is kept in cache on the local machine [until the cache is flushed] instead of being on the server.

Right Click MY Computer > Properties > Hardware > Device Manager

Right Click Disk Drive > Properties

Disable: Write Cache Enabled

Restart the computer



BDE on Terminal Server

Screen shot of error:


How to get BDE to work on a terminal server.

The Solution


As with getting most legacy applications to work correctly on Terminal Server, getting the BDE to work is a matter of rights. Once rights are setup, you can then configure the BDE.


There are many ways to solve these specific rights errors. One easy solution if you trust the users using the terminal server is to add them as administrators to the terminal server. An elegant way to accomplish this if you're using Active Directory is to add your user group to the Administrators group of the terminal server.


Add users to admins of terminal server.




Opportunistic locking (oplocks) and performance

This white paper discusses issues related to opportunistic locking - something that can seriously impact performance on application databases (which ours are). This site is related to a product (DataFlex) that we do NOT use, but the same issues can impact your databases.



More oplock info below in the Windows 2008 / SMB2 discussion


More Microsoft articles related to opportunistic locking

Now you see why we suggest keeping up to date on Microsoft fixes...;en-us;q124916


Some Client Applications Fail when writing to Windows NT;en-us;q129202


PC EXT: Explanation of Opportunistic locking in Windows NT;en-us;q130922


How the autodisconnect works in Windows NT;en-us;q142803


Locking error or Computer hangs Accessing network database files;en-us;q148367


Possible network file damage with redirector caching;en-us;q152186


Possible network data corruption if locking not used;en-us;q163401


How to disable network redirector file caching;en-us;q174371


Possible database file damage when data is appended;en-us;q219022


Improving performance of MS-DOS database applications (ours arent DOS, but its good reading anyhow);en-us;q296264


Configuring opportunistic locking in Windows 2000;en-us;q290757





On Server 2008 is a new OpLocks called SMB 2.0


How to disable and more info:

Registry key: HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters

key name: Smb2 REG_DWORD 0 = disabled


See also


Thanks to Carl Barnes for the info.


More on SMB2 found by Jeff Slarve.




Enable Concurrent Desktop Sessions in Windows - TechSpot Guides

How to Check for Open Files on Windows


Hidden Photos


Maintain Files  |  Filter  |  "Field Value" .DB for "\pict\".






Avast Internet Security


Click me!

Click me!
Exclusion Locations:        G:\Program Files\

* Do not forget the Server root folder location!  E.G. X:\GDData\Program Files\GeeDee\


Thank you to David Huang for the Avast images.