RDM server proxy
I am also very interested in this request.
@anpa
How do you envision this functionality to work in practice? What limitations are acceptable? Is any IP traffic needed or could it be limited to only TCP and port forwarding?
Depending upon the requirements I think that different solutions are possible. Some solutions may be configured to work in conjunction with RDM.
Cisco VPN problem
I would guess that only connected VPN tunnels should be marked as running in RDM. But I am not sure I completely understood the question. I think in the case with the Cisco VPN client it should be possible to use the command line options to print the current running profile (connection entry) with for example "vpnclient.exe stat tunnel".
To be able to maintain a correct running status in RDM for VPN tunnels perhaps some type of functionality is needed that can be scheduled to periodically run some sort of configurable script or command per VPN entry in RDM to report back the tunnel status to RDM. Such scripts or commands could for example: run ping commands, check existing routes, check network adapters, or whatever that can tell status for specific VPN tunnels.
Cisco VPN problem
Could it be possible to check the Windows Registry for an open VPN? At least in case with the Cisco VPN client. The documentation for the Cisco VPN Client (http://www.cisco.com/en/US/products/sw/secursw/ps2308/products_qanda_item09186a00801c2dbe.shtml#mis) says the following:
Q. How can I tell if a VPN client is connected to the VPN concentrator?
A. Check the registry key named HKLM\Software\Cisco Systems\VPN Client\TunnelEstablished. If a tunnel is active, the value is 1. If no tunnel is present, the value is 0.
Port number for RDP sessions
No, the XML file is not read-only. I have now also tested with changing to an XML file in the other installation and the result is the same as in the first installation. The port information is for some reason lost. When I created a new session and entered all the correct information directly the port information is being stored in the XML-tag <Url> but not in the XML-tag <Host>.
Port number for RDP sessions
There we have at least one difference. I now looked at the data sources settings in the problematic installation and it has been configured to use an XML file. In the working installation there the data source is an Access database.
Port number for RDP sessions
Hi.
Sorry, if I have had you do some work in vain. I did now install RDM on another similar machine and there it works so it must be something wrong in my first machine. I wonder what we have done on that machine. I have to recall that. I installed RDM yesterday on the first machine and then I and some colleagues tested with that installation quite a lot. We did not do any connections with RDP to any non-standard ports then. But today when I tried that scenario it did not work. I will make a post if I find any differences between the installations.
Regards.
Port number for RDP sessions
Hi again.
I have now exported the test session to a .rdm file and the content is presented below. I have noticed that the information about the port number is not stored. If I enter the port number in the edit session dialog, click on OK, and open the edit session dialog again then the port number information is removed.
<?xml version="1.0"?>
<ArrayOfConnection>
<Connection>
<ConnectionType>RDPConfigured</ConnectionType>
<CreatedBy>WIN-XP-PRO-01\Test User</CreatedBy>
<CreationDateTime>2010-07-13T16:09:11.6472941+02:00</CreationDateTime>
<Events />
<Group>Site\Domain\System</Group>
<Host>10.0.0.10</Host>
<ID>144809aa-7009-47a5-b069-9cd13dab1333</ID>
<MetaInformation />
<Name>Service</Name>
<RDP>
<UserName>Test User</UserName>
</RDP>
<UpdateDateTime>2010-07-13T16:06:33.6801485+02:00</UpdateDateTime>
<UpdatedBy>WIN-XP-PRO-01\Admin</UpdatedBy>
<Url>10.0.0.10</Url>
<UserName>Test User</UserName>
</Connection>
</ArrayOfConnection>
Regards.
Port number for RDP sessions
Hi.
I have tested both modes without any success.
Regards
Port number for RDP sessions
Hi.
I am trying to set a non-standard port for the RDP-sessions but the port information is ignored by RDM and it is connecting on the standard port. I was trying to use the ip-adress followed by :<port number> (for example "10.0.0.10:3388") but it will not work. I am using version 5.8.1.0 of RDM on Windows XP Sp3 with RDP version 6.0.6001.18000. What is wrong?
Regards.