Loosing nework maps

[ssphoenix]

I am using Citrix to conned to a satelite office. I am having problems loosing the network drives. The software I am using, opens Word to merge documents. While in explorer all my network drives are fine. After the merge, citrix maps the drive I suppose to have, to the local citrix box.

Please help...

 

[gray2002]

Your posting is a bit unclear sspheonix.

When you connect to the Citrix server it probably re-maps your local drives to V: or W: or something. Try using a different drive letter for the drive you want mapped. You may need to adjust your Word macro to point to the new drive letter.

Hope this helps.

 

[ssphoenix]

Gray2002, thanks for replaying. I am loosig my mind here.
What happens, the citrix box has the following maps:

server name (u)
server name (t)
server name (v)

These drives are mapped from the nt login script to various public and private drives.

When I look in the explorer from the workstation in questions, i see the drives are mapped correctly. The same with Word, when I save as and point to any of these drives.

However, I am using a software the works in conjunction with word to merge documents. When this merging occurs, the network drives are gone. They are replaced with the above one. (server name (u) etc..

I do not believe is a word or network mapping issue. I can remap the drive no problem. But after the mearge again, the drive I just mapped, becomes the same as the above...

i.e apps on NTserver name (R) becomes citrix server name (R)

This being again, the C partition of the citrix box.
Very strange...

I have reaplied SP6 on terminal server, I have reaplied all the SPs for Word and office.

Help would be greatly appreciated.

 

[gray2002]

Sorry I'm still confused. Here's what I think you're saying:

You login and drives are mapped

\\SERVER1\SHARE$ (u)
\\SERVER2\SHARE$ (v)
etc

After running your merge program, the drive mappings change to

\\SERVER3\SHARE$ (u)
\\SERVER4\SHARE$ (v)

If this is the case, take a good look at the merge program. Maybe it is disconnecting the mapped drives and then mapping new ones.

If this is not the case, please try to explain it again.

gray