Trouble with Firefox plugin on RD Server

Trouble with Firefox plugin on RD Server

avatar

We have Remote Desktop Manager installed on a 2012R2 RDS server. We use a shared SQL database for all connections. When we create a new Firefox connection in RDM, on the 2012R2 server, then test it, it will not fill in the credentials on the web page (the option is there, but credentials will not populate on the page). HOWEVER if I then open that same connection with a PC, it will fill in the credentials as it should. It seems to be some sort of permissions error on the RDS Server, perhaps.
Other connections that were made on the PC, will open fine on the RDS server.
Please help.

All Comments (10)

avatar

Hi,
Do you use the browser extension or it's embedded in RDM?

David Hervieux

avatar

The browser extension

avatar

hmmm, is the URL public so we can test a few things?

Maurice

avatar

I don't think that will be possible.

avatar

I could setup a TeamViewer session with you on that server, so I could monitor your activity while you check on it. I'm leaving for the day, but we could do this on Monday.

avatar

Do you have multiple sessions opened on this server? We open an html port to communicate and it's possible that it blocked by another account logged.

David Hervieux

avatar

Yes, usually. It is a Remote Desktop Services server. (Terminal Server). That is it's purpose. Multiple users simultaneously.

avatar

I have assign this. I suspect that it's a limitation that we have. RDM create a small web server to achieve a secure communication and it's the same port for all the instance. So in TS you can't open multiple applications on the same port.

David Hervieux

avatar

I haven't heard from you on this in a few days. What does "I have assign this" mean?
Also... I am now having similar (intermittent) issues from a PC. I will start another thread for this issue. But you may want to look at that too.

avatar

I mean that I have entered a feature request and we will try to add this for the next browser extension update. Unfortunately we don't have a simple solution. The workaround would be to use it embedded instead.

David Hervieux