Remote Desktop Connection using the WRT54GC

I replaced a wired router with a Linksys WRT54GC wireless router. Connected to the wired router was a wireless router configured as an access point. I have 2 laptops and I successfully connected to the Internet from both. I was also able to connect to one of the laptops through the wireless access point using Remote Desktop Connection. The only difference between the configuration with the previous router and the Linksys is that the laptop with the Remote Desktop software (the host) was hard wired. Using the Linksys I can successfully access the Internet from both laptops. I can also get to the host computer over the LAN using Remote Desktop Connection. I CANNOT however access the host computer outside the LAN. I configured the router correctly using port forwarding and a 3389 port. I checked "enabled" and entered the IP Address of the host laptop (the one with the Remote Desktop Function). I disabled all security in the router. I have a dynamic address through dyndns.org and have setup the DNS portion of the router accordingly. Can you explain why I can no longer access my home computer remotely using Remote Desktop with the Linksys.

Are you able to access Remote Desktop Connection directly connecting to the modem.

Similar Messages

  • 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+

  • Using a remote desktop connection with the Macbook pro.

    I use the remote desktop connection on the Macbook pro and am unable to exchange info between the mac and the remote connetion windows. For example, if I am writing an email from the remote connection and want to attach a document, photo etc. that I created on the Mac, it just doesn't work. It seems like the Mac and the desktop connection are completely seperated eventhough they are both on the screen in front of me. the systems I use for work are not Apple compatible and will not work on anything other than windows explorer and in my case the remote desk top connection. Any ideas!

    Welcome to Apple Discussions
    Try running in 'ClamShell' mode (MacBook Pro lid closed and using an external keyboard and mouse) with the Gateway connected and then run System Preferences/Displays, it should show then ...
    My 1920x1080 monitor shows the following:

  • Remote desktop connection blocked by cisco security agent

    Hi,
    I have a deployment of a Management Center for Cisco Security Agents 6.0.2 and i just noticed that the agent is blocking the remote desktop connection to the hosts, the agent installed on the server shows me the event but i'm not able to see it logged on the Management Center (i can see logged any other events), i'm not sure what rule should i enable in order to allow this connection.
    Do you have any ideas???
    Thanks in advance...

    Hi,
    Remote desktop connection uses the highest possible security level encryption method between the source and destination.
    In Windows Vista or later versions of Windows, the remote desktop connection uses the SSL (TLS 1.0) Protocol and the encryption is Certificate-based.
    TS Gateway can also make the connection more secure, enhance security, see detailed information in this link
    http://technet.microsoft.com/en-us/library/cc731264(WS.10).aspx
    Don't forget some known offical antii-virus software, they can also protect the connetion from network attack.
    Yolanda Zhu
    TechNet Community Support

  • Remote Desktop Connection MAC to MS

    I work in the USA and connect to a server in Australia. I have been using a PC with a MS OS with great success. I just bought this Mac Book Pro Retina 15" and have not used a Mac before. I am not sure I can keep it if I cannot get better performance when working connected remote to the Australian server. This would be a shame because it is a fantastic machine. I have been using a free MS Remote Desktop Connection for Mac program to connect and work. Does anyone have experience working from a remote desktop connection using the Apple $79 Remote Desktop Connection program and is connecting to a MS OS server?
    The main issue is speed, and the view does not fill the screen. It does not fill the screen with either view options, "Fill or Full Screen". There is about 1 1/8 on either side with the best option of "Full Screen" and 1 1/2 to the edge of the lid. The program always creates an error message as well, but it is just a cert warning.
    I have some time left to decide if I can keep this Mac Book or need to go back to a PC. I really do not want to spend another $85 if the Apple program is not much better than the MS free program?
    Any experience with connecting using the Apple software to a server for tasks like email in MS Outlook and data base work would be appreciated.
    Thanks,

    Apple Remote Desktop is intended for managing networked Macs. While it can be used to connect to a Windows system by running VNC on the Windows box, it's no better than Microsoft's RDC and is often tricky to set up. I've been using iTap Mobile RDP, available in the Mac App Store or from the company's web site, to connect to my Windows systems. iTap Mobile is much faster than either Microsoft RDC or CoRD (a freeware RDC client), in my experience, and very stable and has been well worth the money.
    You can get a trial version of iTAp Mobile here and test for yourself before purchasing:
    http://itap-mobile.com/desktop/rdp
    Regards.
    Disclaimer: any product suggestion and link given is strictly for reference and represents my opinion only. No warranties express or implied. I get no personal benefit from the sale of any product I may recommend in any of my posts in the Discussions. Your mileage may vary. Void where prohibited. You must be this tall to ride. Objects in mirror may be closer than they appear. Preservatives added to improve freshness. Contestants have been briefed on some questions before the show. No animals were harmed in the making of this post.

  • Remote Desktop Connection Security

    I have several computers in very geographically distributed areas of the world on their own networks behind substantial firewalls. Remote desktop connectivity is about the only really effective means to communicate with them however, short of VPN appliances
    BorderGuards, etc. I have been ask by my security officer if the remote desktop connections we've been using have been encrypted? I didn't know the answer myself, and research on the internet didn't provide definitive answers. Was there a chance or is
    there a chance that our session traffic could have been read by anyone along the way?
    VR/JW--Sunblock1960

    Hi,
    Remote desktop connection uses the highest possible security level encryption method between the source and destination.
    In Windows Vista or later versions of Windows, the remote desktop connection uses the SSL (TLS 1.0) Protocol and the encryption is Certificate-based.
    TS Gateway can also make the connection more secure, enhance security, see detailed information in this link
    http://technet.microsoft.com/en-us/library/cc731264(WS.10).aspx
    Don't forget some known offical antii-virus software, they can also protect the connetion from network attack.
    Yolanda Zhu
    TechNet Community Support

  • Since upgrade to Windows 8, cannot save .rdp files under the Remote Desktop Connection application on the Desktop

    Since I upgraded to Windows 8, I am no longer able to save individual Remote Desktop Connection files as .rdp files. I am talking about the traditional Remote Desktop Connection application on the Desktop that was in previous Windows versions, not the
    Remote Desktop App from the Windows 8 store.
    When I try to click on the Save button I get "An error occurred while saving to file"
    When I try to click on the Save As button I get "Unable to open connection file" with the file address being where I tried to save it with the file name at the end.
    Also when I upgraded to Windows 8, my .rdp files disappeared from my Documents folder.
     I need to create different .rdp files for different programs that my employees get into on my server. Now I have to hand type all the info each time into the Programs tap on the Remote Desktop Connection window, because I can't save to an
    .rdp file.
     I like the Remote Desktop App from the Windows store but it won't let me designate specific programs to use using standard dos notation (ie c:\program files\ etc..). It just goes to my server desktop.
     I want to promote Windows 8 to my employees but I need either .rdp files for the traditional Remote Desktop Connection or the ability to open specific programs using dos notation in the Windows Store Remote Desktop App.

    I know this is an old post but others might still be having the problem. Here's what I did.
    Create a new text file and open it in notepad. Copy the below into it and edit for your environment. (IP, screen size).
    screen mode id:i:2
    desktopwidth:i:1920
    desktopheight:i:1080
    session bpp:i:24
    auto connect:i:0
    full address:s:192.168.x.x
    compression:i:0
    keyboardhook:i:2
    audiomode:i:2
    redirectdrives:i:1
    redirectprinters:i:1
    redirectcomports:i:1
    redirectsmartcards:i:1
    displayconnectionbar:i:1
    username:s:USERNAME
    domain:s:DOMAIN
    alternate shell:s:
    shell working directory:s:
    disable wallpaper:i:1
    disable full window drag:i:1
    disable menu anims:i:1
    disable themes:i:1
    bitmapcachepersistenable:i:1
    use multimon:i:0
    winposstr:s:0,3,0,0,800,600
    audiocapturemode:i:1
    videoplaybackmode:i:1
    connection type:i:7
    networkautodetect:i:1
    bandwidthautodetect:i:1
    enableworkspacereconnect:i:0
    allow font smoothing:i:0
    allow desktop com:0
    disable cursor setting:i:0
    redirectclipboard:i:1
    redirectposdevices:i:0
    drivestoredirect:s:*
    autoreconnection enabled:i:1
    authentication level:i:2
    prompt for credentials:i:0
    negotiate security layer:i:1
    remoteapplicationmode:i:0
    gatewayhostname:s:
    gatewayusagemethod:i:4
    gatewaycredentialssource:i:4
    gatewayprofileusagemethod:i:0
    promptcredentialonce:i:0
    gatewaybrokeringtype:i:0
    use redirection server name:i:0
    rdgiskdcproxy:i:0
    kdcproxyname:s:
    You don't need to worry too much about what's in here. Save the text file as
    filename.rdp then rightclick on the file and select edit. The familiar GUI rdp session editor will open. You can make changes in the GUI and
    save or save as a different session.
     Hope this helps.

  • Remote Desktop Connection on PowerBook, not x86 iMac

    My office uses SBS2003 with VPN enabled.
    Without VPN, on my PowerBook & the intel-iMac, I can "Remote Desktop Connection" into the server, then subsequently into a workstation through the server.
    With the VPN connected, I can use RDC to connect directly to my workstation (say, unit01).
    With VPN connected, the iMac can't connect directly to the workstation, yet it can still go through the server to the workstation as usual.
    I'm suspecting this is an issue with Rosetta emulating Microsoft's Remote Desktop Connection and not allowing the domain name to be recognized through the VPN.
    Both computers are using the exact same settings for the VPN and attempting to use RDC exactly the same.

    i've been using just the netbios name, simply because it works on my powerbook. I still don't understand why it wouldn't work on this intel-mac.
    I was mainly following this guide:
    http://www.smallbizserver.net/Default.aspx?tabid=266&articleType=ArticleView&art icleId=84

  • 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

  • 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

  • Remote Desktop Connection Manager hang

    I work at a win8.1 client. I use Remote Desktop Managr to access my servers and clients.
    It was working fine till it goes in hanging state and the the screen freez when i am tring to remote login to any PC.
    The version of RDM is 2.2 build 2.426 by Julian Burger.
    I uninstall it and install again, but still the same problem.
    can anybody help me to fix this problem?

    Hi,
    Is this the RDCman you downloaded?
    Remote Desktop Connection Manager
    The system requirements told that it's supported OS is Windows 7, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Vista, so there might be some compatiblity issues when using in Windows 8.1.
    Here is another thread talking about the RDCMan version:
    Where to download Windows Remote Desktop Manager
    V2.5
    Best regards
    Michael Shao
    TechNet Community Support

  • 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.

  • Remote Desktop Connection Expert Question...

    I am looking for someone with a lot of experience with Windows Remote Desktop Connection to answer a basic question or two...
    I have a WireShark capture (only one side unfortunately) which shows 880 MBytes sent from the client running the Remote Desktop Connection, to the host; but I have no WireShark capture of the packet volume coming from the host to the client IP address. The
    capture is for a period spanning 32 hours. I am being asked to try and determine (guestimate) the amount of data that might have been sent from the host to the client... I know this is a real out there question; which is why I'm looking for someone with
    real Remote Desktop Connection experience.  
     Given that if the volume of traffic from the client to the host is 880MBytes over 32 hours; is there any way at all of guessing how much might have been sent from the host to the client?
    Please be kind, this is important and I am presenting all of the information I have.
    Thank you!

    Hi,
    Agreed with T.Murr here. Only based on the networks traces from one way connection, is hard to determine what happens on the other side.
    Besides, hope the following information would be helpful here:
    Top 10 RDP Protocol Misconceptions – Part 1
    Best regards
    Michael Shao
    TechNet Community Support

  • Remote Desktop Connection not working

    I am able to remote desktop connect to my home computer from work; however, I can't remote desktop connect to my work comptuer and server. I believed it has something to do with my Linksys E3000 access point settings but I'm not sure where to look for and verify. I took my home laptop to work and able to do remote desktop connect to the server. I also took a laptop that's working fine with remote desktop connect to the server home and tried to remote desktop connect to the server at work and it's not working. Therefore, I've concluded that it has something to do with the access point and not the settings in the computer because it works fine when I took it out of my home network. I also VPNP in to my work place so that it has the same IP address as at work and still, remote desktop connection from home to work is not working. Any suggestion is much appreciated.

    thebluemamba_24 wrote:
    Connecting from home to your remote desktop server has nothing to do with your router. Certain ports are needed to be opened from the server’s end in order to host an application. Try to connect your computer to your modem or to another wireless network just to check if your work’s remote desktop will work. In case it will not work, then contact your IT guy.
    If you read my previous post it said:
    "I took my home laptop to work and able to do remote desktop connect to the server. I also took a laptop that's working fine with remote desktop connect to the server home and tried to remote desktop connect to the server at work and it's not working. Therefore, I've concluded that it has something to do with the access point and not the settings in the computer because it works fine when I took it out of my home network."
    I think my above statement answers your question of "Try to connect your computer to your modem or to another wireless network just to check if your work’s remote desktop will work." However, your statement prompts me think of something else. What I have tried is bring my laptop to work and tried connect via RDC to the server and it works but it just not working when trying at home. What I have not done is instead of brining my laptop to work and try RDC there, perhaps I should I try it on a friend's or relative's network and see if I can do RDC to my server at work. If this does not work as well, then, could it be that at work there is something something outside RDC coming? But even if this is so, why can't VPN work?

  • Remote Desktop Connection between Windows Mobile 6.5 and server 2012

    Hi all,
    We have problem with remote desktop connection. The server that I want to connect is 2012 R2.
    We have no trouble with server 2008. I searched from internet, there are solutions on server side(I am not sure if these suggestions solve the problem), but our customers don’t want to solve this problem
    on server side because it is diffucult and risky.
    Is there a solution on handheld terminal side to do?
    Operating system: WM 6.5 classic(Professional o.s. has no effect, same error continues)
    Any help will be appreciated from your side.
    With Best Regards.

    Hi,
    What is the precise error message you are seeing?  What are the exact symptoms?
    I don't remember what version of RDP/featureset is supported by Windows Mobile 6.5.  Perhaps the client does not support Network Level Authentication, which is required by default on Server 2012 R2.  You can enable non-NLA connections by
    unchecking Allow connections only from computers with Network Level Authentication in Server Manager -- RDS -- Collections -- Properties of collection -- Security tab.
    Lack of NLA may not be the cause of the issue you are experiencing, however, if it is the only way to solve it would be to change the server setting or to potentially install a new client on the device that supports NLA.
    -TP

Maybe you are looking for