Dvr Remote Desktop Failed To Initialize Application

57 views
Skip to first unread message

Thechosen Wong

unread,
Jun 28, 2024, 7:27:46 PM6/28/24
to noudisgebo

I have an Ubuntu virtual machine to which I need to do remote desktop. I do not have physical access to that machine and I can do only ssh to the machine. I wanted to do remote desktop and came up with lot of options (vnc, xrdp, opennx). I used xrdp and I installed the necessary packages in the ubuntu machine (xrdp and dependent). Then I enabled the remote access in the ubuntu using the following command line option.

To make the connection secure edit the /etc/xrdp/xrdp.ini file so that the address becomes 127.0.0.1. This will be the localhost address of the ssh server. SSH encryption will be used underneath to tunnel the vnc traffic.

dvr remote desktop failed to initialize application


DOWNLOAD ★★★ https://ssurll.com/2yLQvQ



I'm not familiar with xrdp in particular, but the first thing I'd check is to see if the port its using is a) listening for connections and b) open to the outside world. The default port for RDP is 3389.

Next, you need to make sure that the machine is accessible to the Internet on that port, which involved two things: making sure that the firewall on the machine itself isn't blocking connections to that port, and making sure that any network device (i.e. a router) between the computer you're trying to connect to and the Internet isn't blocking connections. PortForward.com can help with the latter; the first depends on what kind of firewall is installed on your machine, if any.

I finally got this to work for me;setup: older laptop running ubuntu 13.10 running standard unity; I have installed cairo dock (which makes it much more usable for me); still not used to the left side app bar;

From my win7 box, I opened an rdp window and used the laptop's IP address to get in; a window did open up but just a standard x11 windows screen (cross-hatch pattern with x cursor); no links, icons or menus to use.

This worked. At first, on initial start-up of rdp session, I got the same blank screen but after 10 seconds (probably because I am using a win7 VDI at work from a remote location) up popped a usable xfce xubuntu desktop; not as nice as gnome but very usable.

By the way i had to install more than just the Xrdp and i did a few more commands for a fall back if Xrdp failed, all seems good at the minute for me, give it a go sure and lets know whats cooking or not. Good luck.Ps.. its frecking great when it works, stay with it.

If only port 22 is being permitted through the firewall, and you lack control over your network path, you may want to use ssh tunneling to tunnel your chosen port on the remote box through to your local system.

where the first 3390 is the local port number and the second 3389 is the remote port number; you would then RDC to 127.0.0.1:3390 to connect. Note that the tunnel is tied to the ssh session - if you close that ssh session, the tunnel will also close and your connection to the remote desktop will drop. Make sure you use an unused port for the local side.

Once the tunnel is established you can use your chosen RDP client to connect. Several of the other answers address this part of the setup (personally I wound up following the xfce4-session suggestion.)

We have an RD farm with two session hosts and a gateway that has been working. It has been in use for several months and I don't think anything was changed. I was informed that it stopped working and I do see evidence of this. I've been troubleshooting and see that the hosts both left the farm last week with this error message:

I have RemoteFX USB Redirection up and running. However i have a device that when redirected if accessed will cause the VM to Blue Screen. I am looking for ideas here. Its an intraoral camera sopro 617. I have tried both windows 7 and server 2012 as the VM and both crash

We have a terminal server that users from other sites RDP into. If they are on the default domain, they can use saved credentials just fine. However if their saved credentials is one of our child domains, then they get the logon screen with the domain set to the default domain - so
their saved credentials do not work.

I do not believe this is a setting on the client's end - I can test from one of the child domains, and provided I use saved credentials from our primary domain, I can log in without prompting. However if I use saved credentials from a child domain, then I get the logon screen with the domain set back to the primary domain.

Originally, the following setting was set to the primary domain: Computer Configuration > Policies > Administrative Templates > System > Logon > Assign a default domain for logon. I have now set this to disabled.

I also noticed a custom ADM template with a registry setting SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Winlogon \ DefaultDomainName set to the primary domain - I have set this to not configured, removed the template, and deleted the registry key and rebooted the server.

Hi I recently installed Server 2012 and started with RDS installation. After I performed 1st time quick installation (Web Access, Broker, Session host), installation failed according to the setup, but I was able to start remote apps, connect to webaccess page locally... Because it failed I removed Roles/Features and I started again, and from that moment I have ghost files (2x calc, paint ... which was left from the prevoius installation ) and I am able to connect to web access, but I was not able to start any of the programs. Error is " This computer can't connect to the remote computer. Try connection again if it continues contact the owner of the computer or your Administrator". So I removed roles several times including IIS but still nothing .

From the outside I use SBS 2011 as a gateway and it doesn't show any application, I can log into to SBS Web access but it won't show anything (empty page like no app is published). This happened also from the first time so I thought that it is because installation failed so sessions are not registered. I must say here that I have server 2008 in parallel and when I change in gateway web access which server to look, and if I choose 2008 everything works without any problem, with this I concluded that it must be something with Server 2012.

I have windows server 2012 foundation with remote desktop services, I have activated license server but i found a warning. A yellow triangle withan exclamation mark. Two lines oflicenses installedinstead ofa

I have an SBS 2011 Standard Server with a member Windows 2012 Server that is acting as a remote app host. User are able to log onto the server and run the remote app. However Group Policy is only working if the the user is logging on from a domain joined computer. If the user logs on from a home computer certain Group Policies don't work: for example the Group Policy is set to sign off the user rather than disconnect when the user exits the remote app. This works on the domain but not when the user connect over the internet. The user is not signed off.

We are working on an new desktop for our users, it will be based on 2008 file and DC's and 2012 RDS Servers, we have the 2012/Windows 8 ADMX templates loaded, At the moment we are in the testing phase and we notice som strange behavior.

2: When it is an new user profile (also traditional or in an UPD) the shortcut will be added to the Apps part, but NOT to the main start screen, also you can logon, logoff or change the type of shortcut in the GPP, it will never be added to the user first start screen (but it is in the All Apps part)

Are these cals to be used with RDS? I have multiple copies of 2008 r2 all of which came with a card that says CALs for Microsoft Windows Server 2008, but none of which actually include a license which means I can't install the license.

It seems there is a lot of information related to 2008 server but I specifically want 2008 R2 for Remote Desktop Gateways services. This is for a call center that wants 100 remotes to be able to access the 3 existing enterprise servers acting as remote desktop servers in a round robin configuration.

I have found some documentation but, it seems outdated. Another question would be if I should go with a never version of server. Would I need to get new licensing for all clients internally and externally? would there be issues in connecting with the 2008 servers on the back end? This would become cost prohibitive.

I am currently building a new Remote Desktop farm in Windows 2008 R2 with 2 hosts who holds the roles of Session Host, Web Access and Connection Broker (using DNS Round Robin and failover cluster management).

The client will be Thin Client starting an RDP session which gives them a full desktop, and also Windows XP and Windows 7 computers.
The Windows XP and Windows 7 computers will use the Remote Desktop farm to access some applications on them via the RD Web Access (using single sign on).

Whenever I use RDP through a ICA session it was always choppy since windows 7 / 2008. XP / 2003 was never an issue. I found that in windows 7 / 2008, you chose the "Basic" theme under personalize and all was good, this is not the same in 2012. How can we make it speed up?

Windows server 2012 remote desktop services, two connection broker servers high available with SQL server 2008 R2 database on a separate server. And two windows server 2012 session broker servers high available configured with a hardware load balancer balancing session load. IP address redirection is disabled on all servers so hardware load balancer is balancing load and initiating the RDP session. Session persistence is managed by connection broker.

Everything working fine with my solution, session persistence and load balancing is also works as expected. Except some of the users connecting from remote branch experience connection disconnect when minimized the Remote desktop connection and also while working.

Then I have configured the keep-alive setting on session host servers using group policy and Restart servers to apply them. I have checked clients using network monitor, they are receiving the keep-alive packet from hardware load balancer IP. but I have still facing the problem of client disconnecting when minimized, but this is not occur to every user.

7fc3f7cf58
Reply all
Reply to author
Forward
0 new messages