Accessing tables on alternate drives with Citrix (AREV Specific)
At 24 AUG 2000 12:35:48PM Don Bakke wrote:
We have a client that uses Terminal Server 4.0 and Citrix for remote access. This TS box is a client to their Novell 4.1 server.
There are two volumes on the Novell server that have AREV tables on them. All LAN workstations and the TS box map these volumes as H: and G:. AREV itself is on H:.
Regular LAN workstations run without any problems accessing the tables on both drives. The TS connections, however, can only see the tables on H:. Even though the tables on G: can be seen from Explorer and the Command prompt, AREV acts as if there are no tables at all (i.e. FS109 whenever one does an attach or listvolume.)
Now…if we launch AREV from the G: drive then we can work with these tables normally. The tables on H: are no longer accessible however (FS109 again.)
Any ideas as to why AREV can't see tables on a different drive than the one it was launched from?
Thanks,
At 24 AUG 2000 05:05PM Steve Smith wrote:
Don,
Guessing here, but it probably has something to do with the context of AREV.EXE to the REVMEDIA.* files.
Assuming that there are no security restrictions, the mapping
of the drives is controlled by Terminal Server, so look at Novell's
map root= (where the apparent root is not the actual root) and also Terminal Server's drive mapping configuration for clues.
Steve
At 24 AUG 2000 06:01PM Don Bakke wrote:
Steve,
I'm not sure how to check Terminal Server's configuration in this, but I did a MAP command from the DOS prompt and it says that G: is mapped to the correct volume.
At 30 AUG 2000 09:32AM Don Bakke wrote:
We have now discovered that this problem impacts AREV and OI as well. Also, we have discovered that it is not related to database files either. We have routines that OSOpen and OSBRead DOS files which fail when attempting to access them on drives which are different than the drive the application is being launched from. Finally, we have tested this on a pure NT network environment so it seems to be strictly related to Terminal Server.
Database Manager and the Utility("CHOOSEFILE") function can show us all the drives and paths that exist, but they won't display any database/DOS files. Very wierd.
Does AREV and OI share a common method of getting file information from the OS that is no longer supported by Terminal Server? If anybody has any more ideas we would be grateful.