Bellone
asked on
Access terminal server from Citrix desktop
I have a client who would like to access a database we provide on a remote desktop server, running Server 2008 R2. The client's users' PCs are configured whereby they connect to a Citrix desktop on log-in, and the RDP files I have provided them with don't work.
Can anyone please recommend a work-around for this problem?
Can anyone please recommend a work-around for this problem?
by batch file or shortcut, just launch it as mstsc /v:hostname
any specific error, or event log error
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your comments guys, I am trying them out. The messages didn't really help, just the usual 'can't connect to server'.
their firewall needs to allow outgoing port 3389 TCP
I have a client who would like to access a database we provide on a remote desktop server
> where is your client ? outside firewall or internal client ?
> Citrix desktop can connect but rdp client cannot ? did u check client 's firewall ?
> right click and edit your rdp file to see the config is it approiate to client.
> if client u meant is outside your company then your server should allow 3389 TCP port.
and client side 's IT should allow they outbound TCP 3389
> where is your client ? outside firewall or internal client ?
> Citrix desktop can connect but rdp client cannot ? did u check client 's firewall ?
> right click and edit your rdp file to see the config is it approiate to client.
> if client u meant is outside your company then your server should allow 3389 TCP port.
and client side 's IT should allow they outbound TCP 3389
ASKER
Thanks npsingh123 - it seems your solution did the trick. We had emailed them RDP files created on a normal desktop, but they apparently needed versions created on their own Citrix desktops.
Thanks too to everybody else who answered - we had tried all the usual 3389 solutions, but to no effect.
Thanks too to everybody else who answered - we had tried all the usual 3389 solutions, but to no effect.