How to configure Remote desktop connection double sign-on?

All dear,
I need help. I install a terminal server 2012, but when I try to remote login, only once sign on. How can I to configure the server to double sign-on.
Thanks

If I understand you right you have custom credential provider on the server. In this case Microsoft says that it is impossible to overcome double sign-on, just search for the "RDC and Custom Credential Providers" on the Internet.

Similar Messages

How to install remote desktop connection?

I have been trying to install RDC on my mac with the latest OSx which is 10.8.5. However, the installation process keeps telling me that it requires OSx version 10.6 or higher. I have got my mac checked at the apple store and there is nothing wrong with it. But the installation still doesnt work.

CoRD: Remote Desktop for Mac OS X

I have a time capsule connected directly to fiber connection. I have connected a windows server directly to TC and configured it for remote desktop connection. From my interanet I can access srvr but not from my home. What config I need on TC?

I have a time capsule directly connected to fibre optic point out. All pcs and macs are connected wirelessly to the internet. I have connected a windows server pc to TC. When configured for Remote desktop connection, I can access windows server from within interanet but don't know how to access it from internet. I guess I need to change some settings in TC to get some ip adress for the remote desktop connection from my home. Anyone who can help me out? Appreciate it.
Narmin

I am a little lost now.. I have read again your title and your first post.. and they seem inconsistent.
In the title you state.
From my interanet I can access srvr but not from my home.
Interanet is not a word I know.. I assumed intranet...are you talking about internet or intranet? And just to be clear say WAN or LAN.. !! Is your home part of the interanet??
In the first post you state,
I can access windows server from within interanet but don't know how to access it from internet.
Now this is more normal.. the issue is not in the home at all, it is accessible from there but fails from internet. If this is correct, then you can do a few obvious things to determine where the problem is.
But first I need to know are you actually testing from a different internet connection to your home lan.. you are not just trying the public IP from inside the LAN as that will fail due to the TC not doing NAT Loopback.
I am also assuming the TC is the only router in the network, and has the public IP on the WAN interface.
And I am also assuming you have turned on the ping responder and you can actually ping your public ip from the internet and get a response. This helps no end in figuring out where there are issues. Strange but I have no idea if there is a ping responder in the TC WAN so you might need to forward that as well. Also if you have a dynamic public ip address are you using dyndns or no-ip or some other service to connect.
1. Test bypassing the TC.. plug the internet connection straight into the windows server,, and test if you have access. If yes, the TC is the problem.. if not, your setup on the windows server is wrong.. look at firewall in particular.
2. Assuming from test 1 the TC is the problem, Post the screen shots of the port forwarding setup for us to look at.. that is by far the easiest way to check it out.
There are lots of references to port forwarding in the TC.. eg
http://must-know-mac.blogspot.com/2008/07/how-to-port-forward-time-capsule.html
The things that generally go wrong are firewall on the computer that is accepting the port.
The ISP doesn't allow connections on a particular port. (not likely in your case)
The router is behind another router.. double NAT will kill any port forward.
Upnp has already allocated a port.. not an issue as TC doesn't use upnp although a reboot of everything after you set port forwards is well worth it.. amazing how things don't stick properly without a reboot.
IP on the receiving device is not static and so changes.
Not enough or right type of ports are opened. This is always messier than it looks as one port is often not enough for two way communications.

How to Configure Remote Connections To SQL Server 2008 R2 Express

Post written June 10, 2010 and pertains to:
SQL Server 2008 R2 Express on both my server and local machines: SQLX_SRV,
SQLX_LOC
SQL Server 2008 R2 Management Studio on both my server and local machines:
MS_SRV, MS_LOC
Windows Server 2008 R2 Enterprise installed on a Hyper-V VPS: WS
SQL Server Configuration Manager on both my server and local machines:
CMGR_SRV, CMGR_LOC
Server Manager: SMGR
I am connecting to my hosting server via Remote Desktop Connection: RDC
I installed SQLX_SRV and MS_SRV on my hosting server and SQLX_LOC and MS_LOC on my local development machine. I am able to use MS_LOC to connect to SQLX_LOC and to use MS_SRV to connect to SQLX_SRV. However I am not able to use MS_LOC to connect
with SQLX_SRV. Here's what I have done so far:
SMGR -> Configuration -> Windows Firewall to turn off the Windows Firewall for Domain, Private and Public profiles. Obviously I'll change this later, but until I can connect I want to remove as many variables as possible.
CMGR_SRV -> SQL Server Services to confirm that both SQL Server (SQLEXPRESS) and SQL Server Browser services were running.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS to ENABLE the Shared Memory, Named Pipes, and TCP/IP protocols and DISABLE the deprecated VIA protocol.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS -> double click TCP/IP to open the TCP/IP properties dialogue. On the Protocol tab Enabled: Yes, Keep Alive: 30000, changed Listen All to No. I've tried it both
ways, but I've got six IP addresses on my server and I wanted to configure SQLEXPRESS to listen to only the first and primary IP. On the IP Addresses tab went to IPALL and cleared the TCP Dynamic Ports field and entered 1433 in the TCP Port field.
For my first and primary IP Address I made sure that Enabled was Yes, I cleared the TCP Dynamic Ports field, and entered 1433 in the TCP Port field. For all other IP Addresses Enabled was set to No and I cleared both the TCP Dynamic Ports and TCP Port
fields.
CMGR_SRV -> SQL Server Services -> SQL Server (SQLEXPRESS) right click and Restart. This of course stopped and restarted my instance of SQLX_SRV enabling the TCP/IP configuration in the previous step to take effect.
On my server, SQLX_SRV is the only instance of SQL Server running and so it's easy to hard wire it to the default port 1433.
The instance name for both SQLX_SRV and SQLX_LOC is the default "SQLEXPRESS". My server machine name is "SERVER1" on the EnglishBrains.com domain. So the proper local name (local within the context of my remote server as connected via RDC) for
my instance of SQLX_SRV would be:
SERVER1\SQLEXPRESS
Note the use of a backslash NOT a forward slash.
Of course to connect remotely from my development machine, which is not on the same domain as my hosting server, I would need to specify the domain as well, so the SQL Server name becomes:
SERVER1.EnglishBrains.com\SQLEXPRESS
I must also use SQL Server Authentication. Before I can use such a remote connection, however, there are still several configuration steps required. So on my server (connected via RDC) I used MS_SRV to connect to SQLX_SRV using SERVER1\SQLEXPRESS
for the server name and Windows Authentication. Once connected I performed the following steps:
MS_SRV -> right click the connected parent SERVER1\SQLEXPRESS instance node at the top -> Properties -> Security -> Server authentication: select "SQL Server and Windows Authentication mode". This will enable connections using either type
of authentication.
Next, leaving the Server Properties dialogue open, Connections -> check "Allow remote connections to this server" box.
Click OK to save these changes and close the Server Properties dialogue.
MS_SRV -> Security -> right click Logins and select "New Login...", the Login - New dialogue opens.
On the General page Enter a name for your new login
Select SQL Server Authorization
Enter and confirm a password
Uncheck Enforce password expiration
Select the default Database and Language
On the ServerRoles page Public will be checked, also check SysAdmin. This is probably not a good idea and I'll uncheck this as soon as I can connect to the SQLX_SRV.
On the User Mapping page select the databases you want your new Login to access and enter the Default Schema of "dbo".
At the bottom of the User Mapping page you'll see the Database Roles table. Public will be selected by default. Also select db_Owner. Again this is probably not a good idea, and I'll refine this once I can connect.
On the Status page confirm that "Grant" is checked under "Permission to connect to database engine" and "Enable" is checked under "Login".
Click OK to save all changes and close the Login - New dialogue.
With these steps completed you should now be able to use MS_SRV to connect to SQLX_SRV using SQL Server Authentication by supplying the name and password for your new Login. I tried this and it worked fine. Next I tried to use this same login
remotely, that is I went to my local development machine and used MS_LOC to try and connect to SQLX_SRV by using
SERVER1.EnglishBrains.com\SQLEXPRESS
and opting for SQL Server Authentication and supplying the name and password of my new login.
THIS DID NOT WORK?? Instead I get the following error message:
Cannot connect to SERVER1.EnglishBrains.com\SQLEXPRESS.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click:
http://www.microsoft.com/products/ee/transform.aspx?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1
If you follow the suggested help link, you are told:
The SQL Server client cannot connect to the server. This error could be caused by one of the following reasons:
A specified SQL Server instance name is not valid.
The TCP, or named pipes protocols are not enabled.
The firewall on the server has refused the connection.
The SQL Server Browser service (sqlbrowser) is not started.
WRONG on all 4 counts! The instance name IS valid. Both TCP/IP and Named Pipes protocols are enabled. The firewall has been shut down, so it is not relevant. Finally the SQL Server Browser IS started.
The next thing I tried was to circumvent discovery by the SQL Browser service by using the following syntax to specify the IP address and port directly when specifying the SQL Server name.
tcp:68.71.134.186,1433
Using this in the Server Name field I was able to use MS_SRV to successfully connect to SQLX_SRV (using SQL Server Authentication of course) with or without the SQL Browser service running.
However when I tried to connect from MS_LOC to SQLX_SRV using this same login (WITH SQL Browser service running just for good measure) it does not work?? I get the following error message:
Cannot connect to tcp:68.71.134.186,1433.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
If you follow the help link you are told:
"The SQL Server client cannot connect to the server. This error could occur because either the firewall on the server has refused the connection or the server is not configured to accept remote connections."
However, the firewall has been shut down and the server HAS been configured to accept remote connections!
I confirmed that i could indeed Ping to 68.71.134.186 and running NetStat -a |find /i "listening" on the server shows that the server is indeed listening at 68.71.134.186 Port 1433 -- which is why I was able to connect to SQLX_SRV using MS_SRV with
tcp:68.71.134.186,1433 .
IN SUMMARY: Even though I can connect to my SQLEXPRESS instance multiple ways from the server itself, I cannot connect remotely from my development machine!
If anyone can help me figure out why I would be very, very grateful!

My two cents to help you out on c# code example to configure the remote sql server express.
Hope it helps. It works, but you have to be extra carefull to read it all and setup the server configuration and netsh commands; also the port fowarding on the router.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Data.SqlClient;
namespace sqlremoteconnection
class Program
static void Main(string[] args)
// this is the local sql server connection
// 192.168.1.101\SQLEXPRESS
// now, the configuration for remote access:
// activate SQL SERVER BROWSER - set it to start "automatic"; then START UP
// SQL Server Configuration Manager
// --> SQL SERVER BROWSER -> properties -> Service -> Start Mode -> automatic -> apply
// --> Log On -> Start -> Ok
            // netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = all profile = CURRENT
            // netsh firewall set portopening protocol = UDP port = 1434 name = SQLPort mode = ENABLE scope = all profile = CURRENT
            // netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = any profile = PUBLIC
            // netsh advfirewall firewall add rule name = SQLPort dir = in protocol = udp action = allow localport = 1434 remoteip = any profile = PUBLIC
// VERY IMPORTANT FOR REMOTE ACCESS: you have to add the rules on port fowarding
// on the router!!!
// TCP: 1433
// UDP: 1434
// or just a personal port like TCP 31433/UDP 31434
// read carefully the netsh commands above
// server name: 123.132.24.177\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,1433 <<-- regular port
// server name: anyurl.myftp.org\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,31433 <<-- WOW different PORT here!!!
SqlConnection myConnection = new SqlConnection(
"user id=sa;" +
"password=password_goes_here!;" +
"server=anyurl.myftp.org\\SQLEXPRESS,31433;" +
//"Trusted_Connection=no;" +
"database=database_name_here; " +
"connection timeout=30");
try
myConnection.Open();
catch (Exception e)
Console.WriteLine(e.ToString());
try
SqlDataReader myReader = null;
SqlCommand myCommand = new SqlCommand("select * from mytable", myConnection);
myReader = myCommand.ExecuteReader();
while (myReader.Read())
Console.WriteLine(myReader["tab01_name"].ToString());
Console.WriteLine(myReader["tab01_age"].ToString());
catch (Exception e)
Console.WriteLine(e.ToString());
try
myConnection.Close();
catch (Exception e)
Console.WriteLine(e.ToString());
Adelino Araujo

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+

I have an Ipad 2 and here is what I am trying to accomplish. On my laptop I connect to a remote desktop connection to access a shared program we use for reporting. How do I set up my Ipad to access this remote server? Thanks for the help.

I have an Ipad 2 and here is what I am trying to accomplish. On my laptop I connect to a remote desktop connection to access a shared program we use for reporting. How do I set up my Ipad to access this remote server? Thanks for the help.

Close ... before going for a specific Cisco app ... lets find out some details:
Host we need more details:
What is your server environment (Windows Server, or Mac OS X Server, or Linux)?
What security is implemented in your environment - as what is restricted (RDP for all or specifc credentials on all machines? Are you part of local admin group to the server you wish to connect)?
Does your environment Support CISCO IPSec connection? If so use Settings> VPN and IPSec tab to enter VPN details, if not then go with above suggestion. IF your restricted to RSA then either built in VPN settings or 3rd party app for RSA would suffice.
Finally, there are many RDP applications out there I use "Mocha RDP Light" (free minimal ads when launched not when connecting).

How do I find out my MBP's 'server name?' to run Remote Desktop Connection?

How do I find out my MBP's 'server name?' to run Remote Desktop Connection?

Hi Dave,
You need to type the server name that was assigned by your mail administrator for the server running Exchange. So please ask your administrator for the Server name. Thanks for your understanding.
For more information, here is an article for your reference.
Add or remove an e-mail account
https://support.office.com/en-ca/article/Add-or-remove-an-e-mail-account-ff7c7735-6117-4b0d-aef6-8aa8a072f60f
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

I have Remote desktop connection for my mac running osx 10.6.8 and I have a windows xp laptop, I want to have my mac be able to run the windows xp from my pc, how do I do it?

I have Remote desktop connection for my mac running osx 10.6.8 and I have a windows xp laptop, I want to have my mac be able to run the windows xp from my pc, how do I do it?

Hello Fiona,
Congratulations on your new iPhone! You can sync information to your iPhone from your MacBook Pro using the Info tab in iTunes when your iPhone is connected. Use the steps in the following article:
iOS: Syncing your data with iTunes
http://support.apple.com/kb/ht1386
Thank you for using Apple Support Communities.
Best,
Sheila M.

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

Server 2012 R2 Remote Desktop Connection Broker

I have installed RDS on a server named PLUTO on which Windows 2012 R2 datacenter is in. There is a domain controller (domain name: AGROSY) running on a Linux server. We have used Samba 3.6.6 to control the file sharing system.
When I attempt to install RDS in Server Manager, it states as following: could not retrieve the deployment information from RD connection broker server pluto.AGROSY.
Then, I searched a lot of solutions, e.g. and tried as following:
Enter-PSSession -ComputerName pluto --> which works;
but Enter-PSSession -ComputerName pluto.AGROSY --> which gives the error message as: Enter-PSSession : Connecting to remote server pluto.AGROSY failed with the following error message : WinRM cannot process the request. The following
error with errorcode 0x80090311 occurred while using Kerberos authentication: There are currently no logon servers available to service the logon request.
If I ping the pluto.AGROSY, it works as well.
I have no idea how it can be solved, please help me out. Thanks a lot!

Hi,
Thanks for your comment. Sorry for late reply.
Initially please enable the PowerShell remoting in your case.
Enable-PSRemoting
http://technet.microsoft.com/en-us/library/hh849694.aspx
For FQDN name, please see that RDCB is properly configured and also certificate which you have used for RDS environment must be trusted with its private key and must match the FQDN name of the server. Did you seen the certificate has been properly used and
configured. You can go through following article for certificate and also for configuring RDCB role.
Configuring RDS 2012 Certificates and SSO
Configuring HA for the Remote Desktop Connection Broker in a 2012 RDS Farm
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

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 stopped working

I made a change to my Verizon TV and Internet package, downgrading from Ultimate HD to Extreme HD and from 35/35 to 25/25. This morning, when I ran a speed test it showed the new speed. I went out for a few hours, and when I returned, my internet connection was not working at all.
I called Verizon's support number and, after talking to two different people, one who wanted to swap out my router, and one who wanted to send a tech to check out my ONT, they finally figured out the problem was with their configuration, not any of the hardware in my house, and got me running again at the correct speed.
During the trouble shooting process, they had me do multiple soft and hard reboots of my router, they remotely rebooted it, and had me push the recessed reset button once, restoring it to factory defaults. This led to problems with my wireless devices, so I loaded a configuration file to the router that I had thankfully saved some time prior to this problem, and everything seemed to be working properly.
Then, I tried to open a remote desktop connection from one of my machines to another one, both on my internal home network, a connection that had worked flawlessly up until now, and it would not work. Moreover, trying to ping the "remote" machine from the one trying to initiate the connection gets no reply, but pings are replied to in the other direction. And, both machines can see and access each other's shared folders and files, and both can see each other in the network map in the networking and sharing control panel app.
I never made any configuration changes to either machine during the trouble shooting process, but to be sure, I used system restore on both machines and took them back to restore points made yesterday, when everything was working.
I am at a loss to understand what has gone wrong, and would appreciate any constructive and helpful suggestions as to how to remedy this situation.
ps
I am running two different web servers on the target machine, and am running stunnel on it to provide secure nntp connections to a news client that doesn't have that capability built in, and none of these servers are available from other machines. Nothing seems to be getting through to the target pc except windows network sharing!

dslr595148 wrote:
#1 In the router go to Advanced -> Universal Plug and Play OR to Advacned -> UPnP (what ever exist in your router).
#2 If you do not have at least two special computers that support Universal Plug and Play (UPnP) where you can not define the ports that they use, turn off UPnP.
A perfect example. At least two game consoles. Any two (Two Xboxes, two Playstations, One Xbox and one Playstation).
#3 If you have at least two special computers that support UPnP where you can not define the ports that they use....
Do you only use one at time or are there times when at least two are on?
#4 In the router go to Advanced -> IP Address Distribution Or to Advanced -> Private LAN
#5 What is the Starting and Ending IP Address, that is listed in there?
We have two Xboxes and a Logitech Revue. I have Windows Media Sharing enabled on three computers, and am also running a beta of Logitech Media Server on one. It is possible that there are times when two or more streaming clients are in operation, but that is a very rare occasion. Two of the computers, the ones I mention in my original post, are on almost continuously.
In Advanced -> Universal Plug and Play, both Allow Other Network Users to Control Wireless Broadband Router's Network Features and Enable Automatic Cleanup of Old Unused UPnP Services are checked, and WAN Connection Publication: is set to Publish Only the Main WAN Connection.
In Advanced -> IP Address Distribution, under Dynamic IP Range it says192.168.1.2 - 192.168.1.254. However, in Advanced -> IP Address Distribution -> Connection List I have set all the lease types to Static, because I was having problems using the Verizon web page to access my set top boxes, particularly the MRDVR. The Static IP addresses for the computers, game consoles, Bluray player etc. are in the range 192.168.1.2 - 192.168.1.12, and the set top boxes are at 192.168.1.100 & 192.168.1.101.
One thing I did not mention in my original post is that I have two unmanaged gigabit ethernet switches in my home network. There are two computers, the ones I mention in my original post, and the Logitech Revue plugged into one switch. That switch plugs into another switch which also has one pc, an Xbox, and a Bluray player plugged into it, and that switch then plugs into one of the ports on my Verizon supplied Actiontec MI424-WR Rev C, firmware version 4.0.16.1.56.0.10.14.4. All of the other ethernet ports on the router are unused. In addition, we have a laptop, a notebook, another Xbox, and a Wii that connect through the Actiontec's wireless.
I don't know if media streaming is still working and I don't really care if it is because we use it so seldomly. It never worked consistently or to our satisfaction. When we want to watch or listen to media from one computer on another, we copy it over the network from shared folders. We have a Homegroup, to which all of the computers belong. If we want to watch or listen to media on one of the game consoles, we copy it to a flash drive. The Bluray player is only connected to the network for firmware updates and for discs with network enabled content.
This same setup was operating before the problem developed, and I can't figure out what has changed to create the problem. The router configuration file that I am using is from June of 2011, and I'm pretty sure that everything was working fine then, and don't recall making any changes to the router's configuration since then.

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 in windows 7 pro

I have a problem accessing remote desktop connection using windows 7 64 bit.
My remote desktop connection shell version 6.3.9600 shows the Network Level Authentication is not supported.
My other computer also win 7 pro 64 bit has a different shell version 6.2.9200 that supports Network Level Authentication.
How do I go backwards to shell 6.2.9200?
I have been trying use remote desktop using the more robust security and could not figure out why I could not log.
I have screen shots of the two shells and my system screens

Hi,
Configure Network Level Authentication
Click Start, click Run, type regedit, and then press ENTER.
In the navigation pane, locate and then click the following registrysubkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
In the details pane, right-click Security Packages, and then click Modify.
In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.
In the navigation pane, locate and then click the following registrysubkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
In the details pane, right-click SecurityProviders, and then click Modify.
In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK.
Exit Registry Editor.
Restart the computer.
Hope this helps!
Andy Altmann
TechNet Community Support

Remote Desktop Connection with WRT54G from Novice

Well, I’m usually pretty good at using Google and forums to eventually figure out how to fix my problem but this one absolutely has me stumped and I’m hoping someone out there has an answer for me. For the record, I have probably a beginner/intermediate knowledge of computers so if you know the answer to my problem, try to explain it simply! ****TO ANYONE WHO TAKES THE TIME TO READ THIS THING AND CAN OFFER SOME ADVICE-THANK YOU!!!!***
THE PROBLEM
I would like to be able to use Remote Desktop to log into either of my home computers from basically any computer on the internet.
THE SETUP
I have two computers, whose names are LAPTOP and DESKTOP that are both running Windows Vista Ultimate. Both of the computers are connected to a Linksys WRt54G Router ; one wired, the other wirelessly. The Linksys router is then connected to a Westell DSL Modem that connects to AT&T’s internet service.
SETTINGS
My DSL service only provides me with a dynamic IP address so I signed up with no-ip.com. Through that site, I bought a domain name and downloaded their small program that runs in the background of my desktop computer. The program checks what my IP address is every couple of seconds and if it changes, it notifies their server so that anyone who types in my domain name is directed to the new IP address.
ROUTER (Firmware 4.20.6)
Basic Setup Page: The Router Name is just the model number, the Server Name is my DSL provider and the Domain Name is the name I chose and registered with No-IP.com. (www.mydomainname.com, for example.) DHCP Server is ENABLED. DDNS Service is DISABLED. Under Advanced Routing, it is set in GATEWAY mode.
Security Page: Firewall Protection is ENABLED. Block Anonymous Internet Requests is NOT checked. Filter Multicast, Filter Internet NAT Redirection and Filter IDENT ARE checked.
Applications and Gaming Page: I chose two port numbers, one for each computer that I want to connect to. On the first line, I have Application: RDP, Port Range: 49200 to 49200, Protocol: Both, IP Address (The IP address of the computer I want to connect to) and the Enable box IS checked. [I did the same thing with the second line for the other computer, but with a different port number and that computer’s IP address)
Administration Page: Access Server is HTTP, Wireless Access Web is ENABLED, Remote Management is ENABLED through Port 8080, and UPnP is ENABLED.
WINDOWS VISTA SETTINGS
First, I went to the Remote Desktop Settings of the target computer and ENABLED Remote Desktop Connection and allowed computers running any version of Windows. I also confirmed that the box labeled “Allow This Computer To Be Controlled Remotely” WAS checked. I then made sure that I had a user name, it had a password associated and that it had Administrator priveledges. I went back to the Remote Connections screen and added the user name as being allowed to connect. (I think this is redundant since it’s both the owner of the computer and has Administrator Status.)
Next, per Randomly Googled Internet Advice, I went into the registry and changed the port number that Remote Desktop listens for incoming connections to Port 49200 to match the router settings. [Registry Entry that I modified was: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp]
Finally, I went to the Windows Firewall and Added (opened) port 49200 for use as a Remote Connection. I kept the protocol as TCP and confirmed the scope was set for Any Computer.
CURRENT STATUS
If I go to Explorer and enter my IP address with a colon and the specify port 8080, I can get the login screen for the router. Same thing happens if I just enter my domain name and port 8080. However, if I switch the 8080 port and use one of the ports I chose (49200), it cannot connect, either using the Public IP address or the domain name. (I’m trying to connect using a wireless card and not connected to my local network so I know it’s the same as if I was anywhere else.)
I’m not sure why it won’t let me connect; it feels like the router will not allow the connection to pass through it to the port I’m asking it to forward to. I’m guessing someone out there who took the time to read it is shaking their head at all the information I provided and knows the one dumb thing I missed!
Thanks again!

I'm attempting to do the same thing with my home network. the only differences are that i have cable internet from comcast and i'm running vista business. my router is the wrt54gs. i'm assuming that the web page is similar for adjustmants. To be honest i cannot figure out how to do a remote destop too. so i went to www.logmein.com and installed the program. once installed to to every computer you want to have access too and log into the website. then click on the add computer icom. full control app sharing etc... even better when you connect you have the option to deactivate the local host mouse and screen to prevent anyone seeing what your doing.
If you resolve the router issue would you let me know. plz thanks
Forest

How to configure Remote desktop connection double sign-on?

Similar Messages

Maybe you are looking for