'Read Only' shared drives on Windows servers stops Visual LANSA Network Clients connecting to server
|Date:||6 January 2006|
|Product/Release:||Visual LANSA - All versions|
|Abstract:||Shared drives or directories on newer windows operating systems are created with "Read only" permission, which affects Visual LANSA network clients connecting to the windows server|
|Submitted By:||LANSA Technical Support|
In the V11.0 Installing LANSA on Windows guide, the section 1.1 BEFORE You Install or Upgrade LANSA makes the following point:
"If you are performing a Visual LANSA Client Only Network Install, ensure that you have mapped to a drive on the server where Visual LANSA is installed. Also check that you have access rights to the mapped drive."
This step has two parts
- Sharing the LANSA directory on the Windows server.
- Creating a map for this shared directory
In older Windows operating systems, sharing a drive or directory would be created with "Full Control" by default. In newer Windows operating systems (eg. Windows 2000 Server, Windows 2003 server), when you share a drive or directory, the share is created with only "Read" permission by default. This causes the Visual LANSA network client to not be able to connect to the Visual LANSA server. When attempting to run Visual LANSA Development Environment from a network client, nothing happens.
The solution is to amend the windows server shared directory to have "Full Control" which then allows the network client to connect.