Syfer22 Posted August 18, 2014 Posted August 18, 2014 So at work, they use Remote Desktop. My work computer at home used to connect to it fine. Then work updated the Remote Desktop, and now my computer can no longer connect to it. Ironically, my other computers can -- Just not the computer I designated for work. What happens is, when I use the RDS client it just works on initiating connection for a long period of time before giving an error message which I've attached to this post. It never asks me for my log in credentials. I know that error message is wrong because other computers (both my other personal computers and other people at work) are connecting just fine. I've made sure Remote Desktop connection is enabled, I've deactivated my firewall, did a reboot of my computer, router and modem, and so far nothing works. I run Windows Home Premium 64bit. Can anyone help me? It makes no sense that: A.) My computer used to be able to connect, and now no longer can and B.) Other computers can connect just fine -- Just not the computer I've designated for work. I know that the simple answer is to just use one of the other computers, but my other computers are laptops while my work computer is the one with access to my dual monitors (which I need for work).
jonemery99 Posted August 18, 2014 Posted August 18, 2014 The clock if it's more than a 5 mins out it can cause issues, or in wrong time zone
Syfer22 Posted August 18, 2014 Author Posted August 18, 2014 Ah ha, gotcha. My computer is set at the same time as all the other computers.
bossman Posted August 18, 2014 Posted August 18, 2014 It looks more like a network issue, something to do with your firewall settings on the port forwarding side, I have had this issue when our firewall checked out one evening. I would check your firewall settings or get someone to check them for you.
Syfer22 Posted August 19, 2014 Author Posted August 19, 2014 It looks more like a network issue, something to do with your firewall settings on the port forwarding side, I have had this issue when our firewall checked out one evening. I would check your firewall settings or get someone to check them for you. I hear you on that one. I tried both connecting with Firewall up and with Firewall off, but it's the same thing regardless -- It never asks for my credentials, it just gets stuck on Initiating Connection followed by that error message. I've also tried DNS flushing.
MordyT Posted August 19, 2014 Posted August 19, 2014 Firewall - both pc and network. Try telnet into the port to confirm the firewall is open.
Syfer22 Posted August 27, 2014 Author Posted August 27, 2014 Okay, well... None of the above worked, but I did some monkeying around on my own. I figured since the old file worked and the new one doesn't, I'd download the old file and see what happened when I tried to connect. Naturally it didn't connect, but it at least got past the "initiating connection" part. So after a bit of head scratching, I just decided to edit the old file with the new info and... Voila. NO idea why that worked, but it did. Considering the new file works on two of my laptops, I'm still thoroughly confused but I'll take it. Thanks for all your help and suggestions!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now