Hi,
I am having an issue with Terminal Services on Windows Server 2008. I have a Linux server that is a database for my company. The application that we use to access the database is shared through a Samba share. I have no issues accessing this executable on the server itself but when I RDP into the server with a client, the client cannot access this database program. If I create a shorcut using the DNS name as reference the shortcut is broken and cannot find the file. If I create a shortcut using the IP address I can run the program but cannot login to it as it cannot locate it's user direcory. As I said before though I have no issues accessing or even logging into the program when I am locally on the Server (using either DNS or IP for the shortcut), just remotely.
Can anyone explain to me why this works like this and please let me know if there is anyway to fix, or perhaps even a way to get around this issue.
I am having an issue with Terminal Services on Windows Server 2008. I have a Linux server that is a database for my company. The application that we use to access the database is shared through a Samba share. I have no issues accessing this executable on the server itself but when I RDP into the server with a client, the client cannot access this database program. If I create a shorcut using the DNS name as reference the shortcut is broken and cannot find the file. If I create a shortcut using the IP address I can run the program but cannot login to it as it cannot locate it's user direcory. As I said before though I have no issues accessing or even logging into the program when I am locally on the Server (using either DNS or IP for the shortcut), just remotely.
Can anyone explain to me why this works like this and please let me know if there is anyway to fix, or perhaps even a way to get around this issue.