For a list of current known issues, refer to the Customer Service Discussion Forums at:
Microsoft Updates
All servers on the network, whether D3 NT server or D3 NT client is installed, MUST be running identical Microsoft Service Packs and/or identical Microsoft patches. Certain Microsoft Service Packs/patches that fix security issues with RPC buffer overruns can interrupt communications from FSI to FSI if one system has a Service Pack/patch and the other system does not.
Logging to an Account
When logging to an account for the first time, if the file version number was changed, the system needs to upgrade all of the files in this account. This may take longer on larger accounts.
Performance Monitoring
Performance Monitoring does not work on Windows 2000, 2003, and XP (Issue 24417). The work around is in the perfmon.exe program which is provided in the D3Programs directory.
RPC Communication
This version is not able to communicate over RPC with releases of D3 NT prior to 7.2.0.
Linksys Network Adapter Cards
Early model Linksys network adapter cards on the client and server randomly cause the VME and/or Windows NT to shut down and reboot. To correct this problem, switch to another brand of network adapter card.
Shutting Down Windows While D3 NT is Still Running
Because shutting down Windows while D3 NT is running causes a loss of overflow, it is recommended that you ensure that D3 NT is shut down prior to shutting down Windows.
Windows Printers
In certain instances, printers may not be available to D3 until initialized by Windows, depending on the initialization string that is required by the printer driver.
ISQL
ISQL is not supported on D3 NT.
Accessing Mapped Drives from D3 NT
Mapped network drive resources may not be available to D3, even if the user that mapped the drive in Windows is the same user that is starting D3. If this is the case, map the drive directly from D3 using the net use command.
|
NOTE— |
• Ensure that these commands work from a MS-DOS prompt to verify that your command syntax is correct and that the drive can be successfully mapped. • Avoid any prompts requiring input as they will hang your D3 session when attempting to map the drive using !net use from TCL. |
Syntax
net use {drive letter:} \\{machine name}\{share name} {password} /user:{domain\user name}
Example(s)
net use I: \\svr-sup\robert password /user:admin\rlb
Once the resource is mapped from a MS-DOS prompt (with no prompts for input), you can delete the resource from the MS-DOS prompt. For example:
net use I: /delete
Then map it from TCL by inserting a ! before the command. For example:
!net use I: \\svr-sup\robert password /user:admin\rlb
You can set up a user on the destination system with a generic name and password and add this command to the user-coldstart macro to ensure the resource is properly mapped and available to D3 every time D3 is started.
Installing D3 NT on Windows XP
If you are installing the D3 NT Server on Windows XP Service Pack 2, after activating the D3 NT Server, the following message may display:
Prc Locator has encountered a problem and needs to be closed. We are sorry for the inconvenience. If you are in the middle of something, the information you were working on might be lost.
If the message displays, see Microsoft Knowledge Base issue 904767 at the following URL and install the associated HotFix:
http://support.microsoft.com/?kbid=904767
Telnet Localhost
On 64 bit versions of Windows, the telnet localhost shortcut in the D3 7.5 program group may report a problem with shortcut error. If this occurs, select the Fix It option to correct the pathing.