Remote Desktop Connection via AirCard AC790s

I have an Aircard AC790s that one of my staff takes to locations so access the internet.This computer is set up with Remote Desktop and a Dynamic DNS program.Is it possible to remote into the computer when it is connected with the AirCard?When they are at their house, I can access and control their computer without any problem.I can ping the IP of the Aircard also without issue.Thanks

So you are trying to access PC inside your WIFI network?
This may not work unless your router APN is telstra.extranet and you have GPTEXB3 code added to your account. Definitelly not possible in pre-paid account, found the hard way. Check this out
http://forums.whirlpool.net.au/archive/2229138

Similar Messages

I want to remote desktop connect via Bluetooth

I have two laptops on a little pan network. I can share folders and files between them. But I additionaly want to be able to establish a remote desktop connection between the two laptops. I'm not having too much success here. Can someone point me in the right direction? Thank you.
Oh - XP Professional SP3. Toshiba BlueTooth Stack which hasnt been upgraded.
Thanks again.

I use remote desktop access - mstsc.exe - to remote all my servers at work.
So I have my PAN at home on two XP Pro SP3 laptops w/ internal bluetooth. I run mstsc.exe and cannot see my other computer across the PAN. I can share folders without issue. Both laptops are in the same workgroup but mstsc.exe fails.
I'm missing something.
Ahhhh. Figured it out. The remote desktop access network configuration is in it's options. The computer field has a drop down menu, I was expecting it to populate being a drop down menu. But there were no menu items listed. That throw me off. But I just typed my other computer's name in the field and it connected me to the log in screen and my other comuter is now listed in the drop-down menu. That how its done.
It's slow though. But I knew that.

Problems conencting via Remote Desktop Connection to a server

hello! i have a problem connecting to one of our servers via Remote Desktop Connection. The story goes like this: the server works fine, i can connect using my credentials with no problems, the firewall is up. But, when i restart the server, after loading
windows, the server wont respond. I try to ping its IP Address and no respond. The only way so far to fix this bug is to log on localy (without remote) and disable the Windows firewall. Instantly the server starts to respond and i can connect to it via remote
desktop conenction. If i restart the server, the problem appears again and the solution to it this time is to enable the windows firewall back again. This enable/disable firewall thing doesnt seem right. Does anyone have any idea?
thank you!

Hi Dede,
Your box is up to date with windows updates.
Witch windows server are you using?
Maybe review the firewall exceptions.
Att,
Nicolas Rojas

Trouble Printing to Network Printer via Remote Desktop Connection

Specs:
Macbook Pro, early 2013,
Mavericks (10.9.2),
Microsoft Remote Desktop Connection v.8.0.5 (latest),
Connecting to Windows Server 2008 standard
Printer, HP LaserJet P2035n, connected via the network
When on the Mac connected to the server, the printers from the Mac are redirected so you're supposed to be able to print from Remote Desktop to the HP printer. However, when you select something to print, the job goes to the print and keeps printing over and over and over again until you cancel the print job, which it usually allows you to do, or turn off the printer, which you have to do when it won't let you cancel the job.
Any advice on how to get the printer connection running normally?

What you haven't told us is what method you use to connect/setup the printer on Windows. There are two ways - Bonjour for Windows (free software from Apple), and TCP/IP raw port 9100. If you have a problem using one, try the other.

Dymo Labelwriter printers not working via Mac Remote Desktop connection into Windows Server 2008

I'm having a really hard time getting Dymo labelwriters (models 335 turbo and 450 turbo) to work over a remote desktop connection and I'd appreciate any help you can offer.
To briefly describe the situation, I'm working for a Doctor's office, moving their IT from a remotely-hosted environment where employees connect to their Windows Server 2008 virtual machines (hosted off-site) via Windows 7 machines through Microsoft's remote
desktop software.
The new setup will have new servers running in-house instead of remotely and will be based on Apple's Mac Mini machines running Windows 7 for some tasks through Parallels virtualization
software running directly on each employee's Mac Mini.
We have 3 of the Dymo 450 Turbo products and one 330 Turbo, each connected directly to a Mac Mini.
Here's the problem: I have Microsoft's Remote Desktop software running on the Macs natively, connected to each employee's virtual machine on the remote server for now, until the time comes to make the switch to using the new in-house server. The remote desktop
software works fine - employees are able to connect successfully and access their desktops fine. I have the "Forward Printing Devices" option checked in the Microsoft Remote Desktop app so that the hosted virtual desktops can see the local labelwriters.
However, the Dymo Label software running on the remote server will not recognize that a labelwriter is present.
If I go to the Printers and Devices window on the remote server, the labelwriter shows up fine, named "dymo labelwriter 450 turbo (redirected 10)" however running the Dymo Label software gives an error, "Dymo label says no printer connected:
dymo label printer requires a dymo label printer be installed and connected ..."
To try and narrow down the cause of the problem, on the same Mac, I ran Windows 7 via Parallels and set up a new remote desktop connection within that Windows VM. Just to be clear, instead of using the RDC software running in the Mac OS, this new connection
is using a Windows virtual machine running on the same Mac, with the RDC being established from within that Windows VM. Again, I forward printing devices and the labelwriter shows up in Printers and Devices on the remote server as "dymo labelwriter 450
turbo (redirected 10)" This time, the Dymo Label software recognizes the attached labelwriter and runs fine.
I'd appreciate any advice you can give on why, as far as the remote server is concerned, a forwarded labelwriter from Microsoft remote desktop running natively on a Mac isn't recognized
but it is if forwarded from within Windows, bearing in mind that the labelwriter shows up on the remote server in both instances and is called the same name in devices and printers.
Sorry for the long-winded question. I hope you can help me.

Hi,
Thank you for posting in Windows Server Forum.
Firstly please check whether you have driver capable for your printer with MAC MRD. Also I would like you to check with updated MRD version 8.0.9 for MAC OSX.
https://itunes.apple.com/in/app/microsoft-remote-desktop/id715768417?mt=12
Because as you have commented it can work with windows RDP, so please also try to contact Dymo Labelwriter printer and inquire regarding the issue.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Remote Desktop Connection Client 9.3.9600 unable to connect to Server 2012 RDS via Gateway

Hi,
I have a Windows Sever 2012 R2 RDS environment with two Gateways servers configured in high availability mode (RD Web Access, RD Gateway, RD Connection Broker roles installed) and four Windows Server 2012 R2 RDS Session Hosts. The servers are all running
the most recent public server updates. With this configuration I when connecting externally using a Windows 7 computer with the older Remote Desktop Connection client (6.1.7601) I am able to connect without any problems however when I try connecting with a
newer client from a computer running Windows 8.1 and the 9.3.9600 client I am unable to connect.
At the moment a NAT rule is configured to pass 80/443 traffic to only one of the RDS gateway servers, I've removed our load balancer from the configuration for the moment to reduce the complexity.
No error is generated by the client when it tries to connect it just stops trying to connect after a while.
On the Gateways servers event logs for
Things I have looked into so far.
- I've double and triple checked the RDS configuration and checked it against one of my other clients configurations that is working and they are identical.
- Connecting from an older client version works fine.
I'm not sure what else can be checked does anyone have any ideas?

Hi,
1. What entries are you seeing in the RD Gateway's log? Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-Gateway
2. How come you are not forwarding UDP port 3391 in addition to TCP port 443? It should work without UDP, but you will not have UDP support which is one of the benefits of RDP 8.0/8.1.
3. Are there any non-default group policy settings being applied to the servers and/or client PCs? To be clear, I'm asking if any changes have been made to the default local and domain security policies, group policy objects, new GPOs that may have
been added, etc., that are applicable to the servers and or client PCs.
-TP

Why, when I successfully connect to Server 2012 Essentials R2 via Anywhere Access does the Remote Desktop Connection use the self signed certificate for RDP instead of the SSL certificate I installed when I set up access anywhere?

Scenario:
Windows Server 2012 R2 Essentials
I purchased an SSL Cert from GoDaddy and I managed (after some challenges) to set up Anywhere access to use that new SSL Cert. I to rebooted the server and I am able to login to Anywhere Access vis https (using the SSL certificate) from PC, Mac and iOS.
So far so good.
The problem I am having is that when I click to launch a remote desktop connection to the server RDP connection wants to use the self signed SSL certificate of the server rather than the SSL Certificate I installed into Anywhere Access. As a result, I get
a security warning like this: "The identity of the remote computer cannot be verified. Do you want to connect anyway?"
The name in the certificate appears as ACME-SERVER.ACMEDOMAIN.local instead of the SSL Certificate I installed, which is
remote.acmedomain.com
If I lick to accept, RDP does work fine, it;s just using a self signed certificate. I want it to use the trusted certificate that I purchased and installed.
My guess is that there must be an additional step to tell Anywhere Access that when it generates the RDP session that it should use the cert? OR, is this just how it works?

Because....
the server does not have a 'trusted' certificate assigned to it.
Only the RDP Gateway has the trusted certificate for the external name.
If you want to remove that error, you have to do one of the following:
Make sure your domain uses a public top level domaim, and get a public trusted certificate for your server.
So, something like,
server.domain.publicdomain.com
Or,
Install that certificate on your remote computer so it is trusted.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

Remote Desktop Connection to Windows 8 PC from other computers crashing

Hi all.
Was hoping someone would be able to help me with an issue I'm having.
I'm trying to get a LAN remote desktop connection established to my Windows 8 laptop. It's an HP ENVY 17t-2100 CTO 3D Edition Notebook PC. Note that I'm running Windows 8 Pro only - not 8.1 as HP haven't released 8.1 graphics drivers for this laptop and probably
never will. The computer has a single user profile that has full administrator rights.
I have followed numerous web tutorials on how to turn on Remote Desktop. I've gone into Advanced System Settings > System Properties > Remote > checked "Allow Remote connections to this computer". All seems ok to me.
The problem comes when I try to establish a connection. When the connection is made, it almost instantaneously crashes the session on the computer or device trying to connect. The RDP client on my Windows 7 laptop, Mac OSX or Mac running Windows 8.1 Pro just
crashes, while the RDP iPhone or iPad app simply flickers for a few seconds then goes back to the main screen. Meanwhile, the HP ENVY loads the lock screen and displays a message saying XXX device is connected remotely and it won't let me log back in to kill
the connection or do anything. I have to restart the computer from then to be able to use it again.
I'm convinced there's not a problem with my local network as the HP ENVY can RDP into the Windows 7 laptop or Mac running Windows 8.1 without any problems. All computers are connected via Ethernet to a Linksys/Cisco wireless ADSL modem router which supports
Gigabit. The iPhone and iPad of course connect to the wifi network from the Cisco/Linksys modem router
I've also had a brief look at the RDP local connection logs. From what I can make out, they confirm that a user has successfully logged in, but they don't provide a crash log or a log of the user ever disconnecting, probably because I have to restart the computer
to continue using it. Dead end there, it seems.
The HP ENVY is connected to 3 external HP LED monitors. I've disconnected them and tried all devices with no luck. I've also played round with the RDP client settings to not mount drives or printers and the HP ENVY has no printers connected anyway, though I've
done all I can to remove any printer drivers as I've read elsewhere that they are what could cause the problem, but I've had no luck.
If anyone can suggest anything more that I can try, I would be unbelievably grateful! I'm more than happy to provide screenshots or videos of what happens when I try connecting. I'm not sure what you experts would find immediately helpful so just ask away if
you think I can provide anything.
Thanks in advance!
rugbyreff

The first thing that I would try is to uncheck all of the boxes for local resources on computer running the RDP client. It is possible that a device, such as a printer or other redirected device, is causing the crash. You can also look under Event Viewer
in the event logs of both systems and see if anything unusual appears when you attempt the remote connection.
Brandon
Windows Outreach Team- IT Pro
The Springboard Series on TechNet
Hi Brandon
Many thanks for your suggestions. There's nothing in the logs that I could find, like I said in the original post. I've also tried connecting with bare minimum settings on all devices (FYI the iPad and iPhone version don't support the use of printers) and
this still hasn't helped.
If you have any other ideas I'd be very glad to hear them!
rrugbyreff
"If it's worth doing, it's worth overdoing" -- MythBusters

HP LaserJet Pro MFP M127fn and Remote Desktop Connection

So, my pc operates on Win7-64bit. I use Remote Desktop Connection to log in to the company server, running on MS Server 2008. I purchased the HP MFP M127fn today after confirming that it is compatible with both OS listed above. I successfully installed it directly to the server via usb cord - to make sure the correct drivers downloaded to the server. I was able to test-print and print from an app while physically connected to the server. I then disconnected the printer from the server and successfully connected it to my local pc. I can test-print and print from an app on my desktop. When connect to the server via RDC, it recognizes the MFP M127fn as my default printer, and sends a print job to my local pc. I can see the job in the server print queue, I can see the print job in queue on my desktop....it spools, then says it prints, however no actual print job ever materializes.
If I select to print to the MFP M127fn fax from the server, it will open the fax window on my desktop, allow me to enter a phone number, and will dial out and send the fax. So, that driver is functioning properly.
So, my question is this: If the printer and fax claim to be successfully installed, why do I not get the print job that is sent via the server and appears in my local print queue? I get no error, either on the server side or the local desktop. They both truly think the job has printed.....but no paper ever comes out.
Our company has used several other HP printers over the years with this same set-up and have never had a problem until now. The last one was also an HP MFP - the CM1312. So, I am now completely stumped by this. I called HP support and was routed through 4 different areas before I was told that no one had a clue what the problem might be. I then called the Easy-Tech desk at Staples, where I bought the printer, and was told that it was most-likely a hardware issue and I should return the printer to swap it out for another one. If nothing would print at all, I would agree it's hardware. But, as I can print locally, I'm more-inclined to think it's driver-related......any suggestions?

Hi,
The M127fn uses the PCLmS printing language which is a lightweight printing language, a such is not supported for RDP printing.
As a reference you may find the following socument about Citrix, Terminal Services and RDP Printing, as you may find listed the M127 is not supported for a such:
http://h20195.www2.hp.com/v2/GetDocument.aspx?docname=4aa0-8465enw&404m=secure-erc
That is clearly not an harware issue, however I suggest returning the printer and replacing it with a different model which better feet such a task.
The M225dn as an example uses a PCL 6 print driver and should provide a better feet for RDP printing using HP UPD.
Regards,
Shlomi
Say thanks by clicking the Kudos thumb up in the post.
If my post resolve your problem please mark it as an Accepted Solution

Remote desktop connection not working in windows 7 Pro x64 bit sp1 3389 port not working

i have still facing same problem in last two week in my system RDC not working . i have installed in my system windows 7 x64 bit Pro sp1 then i check 3389 port working or not in my system use the command netstat -a -o command in
command prompt but this is my bad luck its not woking in my machine after i have decide to change RDC listening port via registry i have change it 3389 to 3391 after restart my system, and
after again testing using same command but no any change again rdc not listening . After i have search this issue on search engine google bing and microsoft , i have found more solutions but i have try one
uninstalled two microsoft updates first is kb KB2621440 second is KB2667402 and after again restart my system and again installed KB 2667402 But not change i have already enabled Remote Desktop connection in windows 7 and select the option
any version computer running , i have try three and four time enable disable remote desktop connection in my machine . but not change i have all windows firewall disable and uninstalled anti virus they intalled in my machine , and using the Mcafee
stinger tools to scan my machine to remove virus but stinger is not found any thread in system. ihave already run this command in my system sfc /scannow Please Can you help me to fix this issue.

Hi,
When you try to start the Remote Destop Connection, what errors it showed out?
Could the other PCs connect this PC with the RDC?
So you have read this blog?
RDP connections might fail due to a problem with KB2621440 - MS12-020
Did you reinstalled the KB2621440?
Besides, did you follow this guide to enable the RDC connection?
Connect to another computer using Remote Desktop Connection
And also this guide?
Why can’t I connect using Remote Desktop Connection?
Please take a check with those settings again.
Best regards
Michael Shao
TechNet Community Support

Remote Desktop Connection and printing issues

Hi,
I am using Windows 7 on my desktop and also connected to Windows Server 2008 R2 to run applications in Windows Server. However, I noted there is problem with the printer issues. Sometimes, when I tried to print some documents using applications
in Windows Server with my local printer in my room connected to desktop, it won't work.
Moreover, I need to go to Windows Server, Component Service to restart printer spooler so it will work again. This is a pain.
I also noticed there is about 30 seconds wait to process any document to print.
Unlike if I print documents directly from my local desktop computer running Windows 7 and connected to local printer, it only takes seconds to print.
My desktop is connected to Windows Server 2008 via local area network. I should not expect such a significant delay in printing.
I also wonder why printer spooler needs to be restarted when printer is not working.
Can anyone advise me about this? Can Microsoft looks into this problem and release updates to fix the bug to improve the system?
Thanks
Regards,
Clement

Hi,
Please check if you turn on this settings:
You need to set this up just before you connect. The setting will be saved so that you won't need to change it the next time you connect.
1. Open Remote Desktop Connection by clicking the Start button, clicking
All Programs, clicking Accessories, and then clicking
Remote Desktop Connection.
2.Click Options, and then click the Local Resources
tab.
3.Under Local devices and resources, select the Printers check box.
4.Click Connect to start the session.
Make sure that you select your printer in the Print dialog box each time you print.
Karen Hu
TechNet Community Support

Remote Desktop connection and retina display

I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop. it's really important that that this staff works as good on my new computer. The problem is that when I open the connection on MacBook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resolution settings, making it bigger or smaller but the display is still not great. Any suggestions or advice would be greatly appreciated.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resultion settings, still the same.
Any suggestions/help would be much appreciated.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resultion settings, still the same.
Any suggestions/help would be much appreciated.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resolution settings, still the same.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resolution settings, still the same.

Should I assume from your reply that the solution lies with my corporate IT?

Remote Desktop Connection keeps disconnecting

I have BT Hub 3 (recently upgraded to Broadband Unlimited at the end of Jan 2015).
Up until recently I was able to Remote Desktop into my work computer (via VPN tunnel) with no problems at all.
Around March 6th, I began to experience problems with the Remote Desktop Connect (RDP), in that it now makes an initial connection and then disconnects (typically within a few seconds, occasionally after a couple of minutes).
It will then cycle through a number of reconnection attempts, all with the same result, before it finally drops altogether with the message:
'The Remote Desktop Services Session has ended. Connection to the remote computer was lost, possibly to network connectivity problems'.
I have tried restoring both machines back to a date when i know the connection was working - no joy. I've also tried deleting an re-creating now VPN and RDP connections - no joy. I've researched online and tried various other things, but still have the same problem.
I've tried connecting using a laptop (via my wirelss connection) with the same result. My manager has RDP'd in from his home machines and has had no problem at all.
This leads me to consider whether the problem is with the router/BT Hub itself. I've tried the online diagnostic tools with no resolution to this problem.
Has anyone else experienced the same problem?

Oh well, I suppose that after more than 2 months of frustration with this issue, the BTCare Community is unable to help me.
I can be fairly sure that it's not my machine as it's also happened using a laptop, plus I've even reset my PC right back to its original factory state just to sure that nothing had become corrupted.
The network guys where I work have also looked at this and can find nothing at that end to cause this problem.
I've even borrowed another BT Hub and tried it through that - same problem.
So where does the answer lie? VPN issue? I've tried other VPN options - same problem. RDP problem? I've practically exhausted the list of suggested solutions that can be found by trawling the internet.
I even upgraded the broadband cable to replace the cheap old thing that has been working perfectly well in terms of broadband, again, to eliminate this as a possibility. Now I'm stumped.
To me, it looks like the problem lies between my router and the workplace network, i.e. a physical problem among the miles of lines connecting the two. Of course I don't want to shell out for a BT engineer to come out to investigate, so I thought that the combined wisdom of this community may have been able to help.
Sadly not.

Remote Desktop Connection

I'm running bootcamp Windows 8 on a MacBook Pro and a MacMini (on home network).
I have them set up for remote access. At home on the same network, I can remote desktop to the MacMini using the local IP address with no problems.
I then wanted to access it from an external network so I enabled the default 3389 port in my firewall settings and set up this port to my MacMini in my router settings. I reserved the IP address for the MacMini as well.
I was able to successfully connect from an external network at least once but once my external IP address changed, I was no longer able to get it to work after updating the IP address. The computer is on because I can access it using TeamViewer and I use
that to check the current IP address of the MacMini when I'm trying to connect.
To get around the dynamic IP problem, I signed up for a dyndns account and set up a host name. I can use a port check and the host name ***.dyn-o-saur.com resolves to the correct IP address (i.e., the whatismyip.com result on the MacMini).
I have tried changing the port to 8888 in case TeamViewer or some other application was using 3389 but that hasn't fixed the problem either. I've checked the port (using http://www.t1shopper.com/tools/port-scan/) and I get this message:
***.dyn-o-saur.com is responding on port 8888 (ddi-tcp-1).
I have the dynUpdater v5.0.1 installed on both computers and it says the host is inactive (however since the hostname is resolving properly I assume this means the app is not working but it shouldn't be affecting my ability to connect?).
Some help please?

Hi,
Firstly, we need to refer to this article and configure the settings.
Allow Remote Desktop connections from outside your home network
http://windows.microsoft.com/en-us/windows7/allow-remote-desktop-connections-from-outside-your-home-network
From you description, I think you have done this part. However, please keep to use port 3389 and make sure that you can RDP to your Windows 8 via the
Public IP address from Internet.
Then, as you have dynamic public IP address, we need some way to track the changes of your public IP address. Yes, dyndns is one of the methods, you need to make sure that it
can resolve the host name you registered to the correct Public IP address so that you can always RDP you Windows 8 via host name when you outside your home.
If you need assistance about dyndns, please contact their support.
Thanks.
Jeremy Wu
TechNet Community Support

Remote Desktop Connection With Custom Certificate on Windows 8.1 fails

I'm trying to establish a secured remote desktop connection without success.
The setting
There are some local pcs with windows 8.1 Pro and windows 7 Pro, no server-edition. I've created a self signed ca-certificate with openssl for Windows. I used this to sign custom certs for the local windows-pcs, which are installed at mmc -> certificate
snap-in for local computer -> My Certificates -> Certificates. The networkdriver has the right to read the key. The sha1-fingerprint of the custom signed certs are registered at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
-> SSLCertificateSHA1Hash = sha-1 hash of the custom local cert. Additionally the revocation-list is restrained to the local list by setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp -> UseCachedCRLOnlyAndIgnoreRevocationUnknownErrors
= 1.
The results
The connection form win 8.1 to win 7 works. The connection info confirms that it is a veryfied connection. The connection to windows 8.1 fails after entering the credentials with error: No connection possible. Network Level Authentication is set, but other
level don't work as well. The log (Event Views -> Applications and Services Logs -> Microsoft -> Windows -> TerminalServices-RemoteConnectionManager -> Admin) says "Remote Desktop Services has taken too long to load the user configuration
from server" and "The Local Security Authority Cannot Be Contacted" (error 0x80090304)
Aditional information
The connection via linux (remmina) works for win 7 and win 8.1, but I have no information about the encryption. It is the same with the Microsoft Remote Desktop Tool for Android.
Maybe it is accociatet with a different cert handling by Windows 8.1 but I couldn't find further information or a solution in the internet.
Best regards
abditus

I solved the problem!
The default openssl certificate signature algorithm is md5RSA but it doesn't work with windows 8.1.
It is at least sha1RSA needed.
By adding "default_md = sha1" to the openssl.cnf you create certs with sha1RSA and it works fine.
Beste Gegards
abditus

Remote Desktop Connection via AirCard AC790s

Similar Messages

Maybe you are looking for