Vista remote desktop connection to Windows Server 2003

[Jimmy Niko]

Hello,

I have a Windows Vista laptop which I use to connect to Windows Server 2003 via remote desktop. While I am in the remote desktop connection I try to attach a file to an email in outlook and I get the following error message - "\\tsclient\c\documents and settings\user_name\my documents is not accesible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Access is denied.". This error message won't go away and reders the remote desktop session useless however If I browse to \\tsclient I can access the local resources of the laptop without a problem. The problem seems to be that outlook (and other office applications) are looking for the documents and settings folder which does not exist in windows vista. I have tried to replicate the problem using a Windows XP based laptop and the problem does not appear (hence the reason why this post is in the Vista section.

Any suggestions on fixing this problem? Thanks in advance.

Edited June 18, 2007 by Jimmy Niko

[cluberti]

What happens if you delete and recreate your profile in Windows, and don't connect to it with XP? Does it then look in the correct Vista location (\\tsclient\c\users.....\)?

[Jimmy Niko]

As the profile resides on a Windows 2003 server, deleting it is out of the question (the user is part of a domain etc). However, I just created a new user on the server and setup outlook in it and tried to replicate the problem. The problem does not appear. It seems somewhere in the registry (the area specific to that user) theres a entry storing the path that outlook uses (and other MS office programs i suspect).....

[cluberti]

That's what I was hinting at - at this point, I would suggest running process monitor while opening outlook to see where specifically it's reading this info from, and from that you should be able to change it.

[Jimmy Niko]

Any suggestions on a good process monitor?

[cluberti]

Well, Process Monitor and Process Explorer (from sysinternals) are a good combo.

[Jimmy Niko]

FINALLY found the obscure registry entry that relate to this..

HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word\Options\DOC-PATH

changed the value to \\tsclient\c and the error no longer appears.