Q-101.193
Client-Server connection in Windows NT/2000


Frage
Problem In a homogeneous Network with windows NT/2000/2003 Server and windows Workstations one or more useres can not connect to the DvISE Server.
Produkt David.InfoCenter
Priorität normal
Effekt normal
Datum 26.06.2002

Antwort
If some Tobit InfoCenter are not able to connect you should consider the following issues:
  1. First, carry out the de-installation routine by »Start -> Programs -> Tobit InfoCenter -> Uninstall ...«
  2. If there are Start menue entries delete them manually.
  3. Carry out the »DAVID\CLIENTS\WINDOWS\FAXIMG\Setup.exe« and activate just the checkbox »Remove ancient Fax-Image Driver« and then select »Install«.
  4. Navigate to the directory WINNT by the Windows Explorer and search for the following files:
    • DV*.*
    • DAVID*.*
    • TOBIT*.*
    • FW*.*
    • FAXWARE*.*
  5. Delete all the the file entries at the HDD according to the patterns above.
  6. Carry out »C:\WINNT\regedit«
  7. Delete - in case - the following registry entries manually:
  8. HKEY_CLASSES_ROOT/Applications/DVATT.EXE
  9. HKEY_CLASSES_ROOT/Applications/DVEXTINF.EXE
  10. HKEY_CLASSES_ROOT/Applications/DVWIN32.EXE
  11. HKEY_CLASSES_ROOT/Applications/TobitFaxFile
  12. HKEY_CLASSES_ROOT/Applications/TobitInfoCenter*
    (the corresponding entries beneath Applications)
  13. HKEY_CURRENT_USER/Software/Tobit
  14. HKEY_LOCAL_MACHINE/Software/Classes/Applications/DVATT.EXE
  15. HKEY_LOCAL_MACHINE/Software/Classes/Applications/DVEXTINF.EXE
  16. HKEY_LOCAL_MACHINE/Software/Classes/Applications/DVWIN32.EXE
  17. HKEY_LOCAL_MACHINE/Software/Classes/Applications/TobitFaxFile
  18. HKEY_LOCAL_MACHINE/Software/Classes/Applications/TobitInfoCenter*
    (the corresponding entries beneath Applications)
  19. HKEY_LOCAL_MACHINE/Software/Clients/Mail/Tobit InfoCenter
  20. HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/App Managment/ARPCache/Tobit InfoCenter
  21. HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/Unindstall/Tobit InfoCenter
  22. HKEY_LOCAL_MACHINE/Software/Microsoft/Windows NT/CurrentVersion/Terminal Server/Install/Software/Tobit
  23. HKEY_USERS/.DEFAULT/Software/Tobit
Check besides the following facts:
  1. The files NWCALLS.DLL and NWIPXSPX.DLL should not be located at the workstation if TCP/IP is the only protocol configured as IPX/SPX is not.
  2. The users should not be configured manually because the way preferred is to create users by autovalidation i.e. the first connection of the prospective user concerned by the Tobit InfoCenter creates the David / Faxware user corresponding.
  3. Replace the server name by the server-ip-address in the »C:\WINNT\Tobit.ini section [COMMON]«.
  4. The server name should not contain any special character. Specifically, avoid explicitely to use an underscore in a Windows NT and Windows 2000 server name. The hyphen could be an alternative.
  5. Remove the standard gateway in the TCP/IP settings, once. After the re-login of the client it can be configured again.
  6. It is recommended to have only the TCP/IP protocol in operation. This is sufficient to connect to the David server.
  7. Check besides, if the ip-addresses and the subnet mask at the server match to the entries at the workstations.
  8. Check if the up to date Service Pack installed.
  9. A high CPU charge can be the reason for which the clients are not able to connect to the server.
  10. Check besides if the user(s) are able to get access to the David sub-directories at the file system level.
If the clients have the OS's Windows 95, 98 or ME in operation consider besides the following issues:
  1. The file UNIDRV.DLL must not be present more than once in the directory C:\Windows and should have a size of 197.840 Bytes.
  2. Deacticate the file and printer access in the network properties of the workstation concerned.
If the clients have Windows NT derivative OS's in operation consider the following issues:
  1. Enter the clients by their name and their ip-address in the file »WINNT\SYSTEM32\DRIVERS\ETC\HOSTS«. The entry in question should formatted at follows:

    DvISE-Server(3 blanks)192.168.0.1

  2. Bind the TCP/IP protocol at the server and at the client as well, first.HINT:
    In some cases the Winsock.dll should be replaced. Consider the KnowledgeBase Artikel Q-100.935 for further information.