RDM Enterprise + SQL potential problems
I just wanted to let everyone know about a potential problem with using RDM and SQL. This is not a problem at all with RDM but more an obstacle that some of you will face. Charter for one, I can now confirm definitely blocks outbound ports 1433/1434 in my area due to potential virus problems. This stumped me for several hours today when we decided to move RDM to a public facing server so we could enforce "no work offline". We could connect to RDM from some locations but not others. It ended up beng a simple fix but figuring out why I could not connect remotely drove me half insane. You can force SQL to bind to an alternative port for the database itself (I chose 14330). SQL Browser however I don't believe can be changed but you can live without it if you force the database onto a specific TCP port. Then you just change your server name in data sources to "servername.domain.com,14330" for example.
http://social.msdn.microsoft.com/Forums/en-US/sqlexpress/thread/97a0ddf7-d23e-4723-b49f-463943180172
The second post there shows how to accomplish this change along with my instructions above for RDM. Everything is working perfectly now running on Windows Server 2008 R2 Enterprise, SQL Server Express 2008 R2, and RDM 5.9.0.0. If everyone finds this post useful enough it would be worth incorporating into the FAQ as it could save some people a lot of time. Thanks again Devolutions for an Awesome product!!!
edited by appnet on 11/17/2010
All Comments (2)
Hi,
Thank you for this post, I will try to add this to our FAQ. I just to see the the second post with the instructions for RDM ?
David Hervieux
The link in my previous post shows the instructions for changing the port in the SQL database. For RDM its really quite simple, under the server name you just put "server.domain.com,14330" <-- no spaces, without quotes. I wasn't sure if RDM supported forcing an SQL connection on a non-standard port but it absolutely does. I can now connect from everywhere including behind charter cable internet. Thanks again for all your hard work, we will be a lifelong customer.