Forum Discussion
Chris_P_15522
Nimbostratus
NimbostratusFirepass static application tunnel for RDP not working XP sp3 & IE8
Hi I have recently upgraded to 6.10 on a 4300 and have recently tried to do RDP by a static application tunnel.
The end user testing is not showing the "domain" information in the RDP client on their end system.
Is there a way of displaying the Firepass network domain information on the end user machine.
RDP via terminal services works ok, it's a user migrating from contivity to FIrepass who requires this feature for his work flow.
ADDITIONAL:
I have been able to re-create this issue. If the Client is logged onto a local domain the available domains in the RDP pull down do not update. However if logging on to a PC that is not logged onto a domain, the problem doesn't occur.
Regards
Chris
Mike_61719Cirrus
Well I am not sure what you mean because it is hard to read what you are writing.
The only way to add the domain is to have a custom .RDP file. I assume you are launching RDP like so... %SystemRoot%\System32\mstsc.exe /v:%host% /f
Can you provide some more details?
Chris_P_15522the setup is the user is on their local domain, They log into the firepass of the other organisation. They run a static application tunnel on RDP port. The user starts up the local RDP client, puts in the server 127.x.x.x address for the connection, Once the login popup on the machine being connected to opens with username, password and login to (domain) the option for the remote machines domain is not there? The other minor issue is that the local server will not reply by name, FQDN but only it's 127.x.x.x address on the tunnel. Only the local domain info is present. This doesn't occur is I login from a PC that is not logged into any domain, ie home PC. Regards Chris- Chris_P_15522UPDATE: just noticed that port 3389 was not connecting and 3390 was opened by the firepass, so RDP had to include the port number, this now works.
new problem, some of the static java application tunnels are now only giving a local address of 127.0.0.1 rather than a 127.x.x.x any suggestions? Thanks - Mike_61719Can you expand on the 3389 vs 3390?
I would create a CR for the Java local port. - Chris_P_15522Thanks, C681021 has been raised...
- Chris_P_15522The 3389 vs 3390 when the static application tunnel formed 3389 was not available locally and this was in the static application tunnel dialogue box, 3390 was what it used in stead. Then rdping to : 3390 this worked.
- Chris_P_15522The root cause for the 127.0.0.1 for the static tunnels was found, thanks to the help desk. A duplicate server name was in 2 different application tunnels, then the 2nd one was activated a bad address was populated 127.0.0.1. thanks for your help.