Trying to get Windows 8.1 Remte Desktop to work on a newly cleaned laptop












2














I have two laptops both Windows 8.1. One of which I am trying to setup now as it has just been factory reset after getting too much rubbish on it.



I am trying to remote desktop into a server in France that a company I work for owns but everytime I try and connect with the exact same computer name/IP address and username that my other laptop uses (that works), it comes back with the "Remote Access to the server is diasabled, The remote computer is turned off, the remote computer is not availalble on the network" message.



I know the server is not turned off as I can remote desktop into it fron the other laptop.



I have checked the firewall rules and I cannot see anything different between the two laptops and the remote server is set to allow my IP address in so either laptop should work.



If I run netstat -a -b -f -n -o on the laptop which can connect to the server, once connected I get this line for mstc.exe (Which I understand is the program I am looking for - plus it has the remote servers IP address next to it)



TCP - 192.168.1.195:3376 - 178.XX.XX.XX:3389 (remote server) - ESTABLISHED - 6298 (Process ID)
[mstsc.exe]



However when trying to run it on my laptop that doesn't connect I get



TCP - 192.168.1.151:50712 - 178.XX.XX.XX:3389 (remote server) - SYN_SENT - 5492 (Process ID)
[mstsc.exe]



So it looks like its getting to the handshake stage but then being refused for some reason.



Also if I try and do a ping to that servers IP address on this laptop I just get Request timed out messages but on the working laptop I can ping it ok.



I had a problem before on Virgin ISP where it was down to their URL auto correcting option > http://blog.strictly-software.com/2010/08/problems-connecting-to-remote-desktop.html but now I am on BT. I would have thought a similar issue would affect both laptops.



I am guessing it must be something on my side seeing that the other laptop can connect and the server allows connections from this IP address.



Does anyone have a checklist of things to check to get Remote Desktop working on this new computer. The virus checkers are just Malaware/Windows Defender at the moment and I haven't installed much apart from Chrome/FF/Filezilla.



Thanks in advance for any tips or advice to get this working.










share|improve this question













migrated from serverfault.com Dec 13 at 9:34


This question came from our site for system and network administrators.















  • Do you have any internet access on the bad laptop? Your gateway IP address may be bad.
    – Appleoddity
    Nov 27 at 23:50
















2














I have two laptops both Windows 8.1. One of which I am trying to setup now as it has just been factory reset after getting too much rubbish on it.



I am trying to remote desktop into a server in France that a company I work for owns but everytime I try and connect with the exact same computer name/IP address and username that my other laptop uses (that works), it comes back with the "Remote Access to the server is diasabled, The remote computer is turned off, the remote computer is not availalble on the network" message.



I know the server is not turned off as I can remote desktop into it fron the other laptop.



I have checked the firewall rules and I cannot see anything different between the two laptops and the remote server is set to allow my IP address in so either laptop should work.



If I run netstat -a -b -f -n -o on the laptop which can connect to the server, once connected I get this line for mstc.exe (Which I understand is the program I am looking for - plus it has the remote servers IP address next to it)



TCP - 192.168.1.195:3376 - 178.XX.XX.XX:3389 (remote server) - ESTABLISHED - 6298 (Process ID)
[mstsc.exe]



However when trying to run it on my laptop that doesn't connect I get



TCP - 192.168.1.151:50712 - 178.XX.XX.XX:3389 (remote server) - SYN_SENT - 5492 (Process ID)
[mstsc.exe]



So it looks like its getting to the handshake stage but then being refused for some reason.



Also if I try and do a ping to that servers IP address on this laptop I just get Request timed out messages but on the working laptop I can ping it ok.



I had a problem before on Virgin ISP where it was down to their URL auto correcting option > http://blog.strictly-software.com/2010/08/problems-connecting-to-remote-desktop.html but now I am on BT. I would have thought a similar issue would affect both laptops.



I am guessing it must be something on my side seeing that the other laptop can connect and the server allows connections from this IP address.



Does anyone have a checklist of things to check to get Remote Desktop working on this new computer. The virus checkers are just Malaware/Windows Defender at the moment and I haven't installed much apart from Chrome/FF/Filezilla.



Thanks in advance for any tips or advice to get this working.










share|improve this question













migrated from serverfault.com Dec 13 at 9:34


This question came from our site for system and network administrators.















  • Do you have any internet access on the bad laptop? Your gateway IP address may be bad.
    – Appleoddity
    Nov 27 at 23:50














2












2








2







I have two laptops both Windows 8.1. One of which I am trying to setup now as it has just been factory reset after getting too much rubbish on it.



I am trying to remote desktop into a server in France that a company I work for owns but everytime I try and connect with the exact same computer name/IP address and username that my other laptop uses (that works), it comes back with the "Remote Access to the server is diasabled, The remote computer is turned off, the remote computer is not availalble on the network" message.



I know the server is not turned off as I can remote desktop into it fron the other laptop.



I have checked the firewall rules and I cannot see anything different between the two laptops and the remote server is set to allow my IP address in so either laptop should work.



If I run netstat -a -b -f -n -o on the laptop which can connect to the server, once connected I get this line for mstc.exe (Which I understand is the program I am looking for - plus it has the remote servers IP address next to it)



TCP - 192.168.1.195:3376 - 178.XX.XX.XX:3389 (remote server) - ESTABLISHED - 6298 (Process ID)
[mstsc.exe]



However when trying to run it on my laptop that doesn't connect I get



TCP - 192.168.1.151:50712 - 178.XX.XX.XX:3389 (remote server) - SYN_SENT - 5492 (Process ID)
[mstsc.exe]



So it looks like its getting to the handshake stage but then being refused for some reason.



Also if I try and do a ping to that servers IP address on this laptop I just get Request timed out messages but on the working laptop I can ping it ok.



I had a problem before on Virgin ISP where it was down to their URL auto correcting option > http://blog.strictly-software.com/2010/08/problems-connecting-to-remote-desktop.html but now I am on BT. I would have thought a similar issue would affect both laptops.



I am guessing it must be something on my side seeing that the other laptop can connect and the server allows connections from this IP address.



Does anyone have a checklist of things to check to get Remote Desktop working on this new computer. The virus checkers are just Malaware/Windows Defender at the moment and I haven't installed much apart from Chrome/FF/Filezilla.



Thanks in advance for any tips or advice to get this working.










share|improve this question













I have two laptops both Windows 8.1. One of which I am trying to setup now as it has just been factory reset after getting too much rubbish on it.



I am trying to remote desktop into a server in France that a company I work for owns but everytime I try and connect with the exact same computer name/IP address and username that my other laptop uses (that works), it comes back with the "Remote Access to the server is diasabled, The remote computer is turned off, the remote computer is not availalble on the network" message.



I know the server is not turned off as I can remote desktop into it fron the other laptop.



I have checked the firewall rules and I cannot see anything different between the two laptops and the remote server is set to allow my IP address in so either laptop should work.



If I run netstat -a -b -f -n -o on the laptop which can connect to the server, once connected I get this line for mstc.exe (Which I understand is the program I am looking for - plus it has the remote servers IP address next to it)



TCP - 192.168.1.195:3376 - 178.XX.XX.XX:3389 (remote server) - ESTABLISHED - 6298 (Process ID)
[mstsc.exe]



However when trying to run it on my laptop that doesn't connect I get



TCP - 192.168.1.151:50712 - 178.XX.XX.XX:3389 (remote server) - SYN_SENT - 5492 (Process ID)
[mstsc.exe]



So it looks like its getting to the handshake stage but then being refused for some reason.



Also if I try and do a ping to that servers IP address on this laptop I just get Request timed out messages but on the working laptop I can ping it ok.



I had a problem before on Virgin ISP where it was down to their URL auto correcting option > http://blog.strictly-software.com/2010/08/problems-connecting-to-remote-desktop.html but now I am on BT. I would have thought a similar issue would affect both laptops.



I am guessing it must be something on my side seeing that the other laptop can connect and the server allows connections from this IP address.



Does anyone have a checklist of things to check to get Remote Desktop working on this new computer. The virus checkers are just Malaware/Windows Defender at the moment and I haven't installed much apart from Chrome/FF/Filezilla.



Thanks in advance for any tips or advice to get this working.







windows networking remote-desktop ping






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 27 at 23:41









MonkeyMagix

1111




1111




migrated from serverfault.com Dec 13 at 9:34


This question came from our site for system and network administrators.






migrated from serverfault.com Dec 13 at 9:34


This question came from our site for system and network administrators.














  • Do you have any internet access on the bad laptop? Your gateway IP address may be bad.
    – Appleoddity
    Nov 27 at 23:50


















  • Do you have any internet access on the bad laptop? Your gateway IP address may be bad.
    – Appleoddity
    Nov 27 at 23:50
















Do you have any internet access on the bad laptop? Your gateway IP address may be bad.
– Appleoddity
Nov 27 at 23:50




Do you have any internet access on the bad laptop? Your gateway IP address may be bad.
– Appleoddity
Nov 27 at 23:50










1 Answer
1






active

oldest

votes


















0














LOL - Sorry - total dinlow, just did a ping to the sites domain on the server and got a reply and noticed that nslookup returned a different IP address I was using 178.xx on the working machine and 173.xx on this one - oh my eyes must be really going to miss that one!!



Techies Law strikes again, as soon as I ask for help I find a fix and end up looking stupid!






share|improve this answer





















  • It's a little like rubber duck debugging... :)
    – Stese
    Dec 13 at 9:47











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1383245%2ftrying-to-get-windows-8-1-remte-desktop-to-work-on-a-newly-cleaned-laptop%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














LOL - Sorry - total dinlow, just did a ping to the sites domain on the server and got a reply and noticed that nslookup returned a different IP address I was using 178.xx on the working machine and 173.xx on this one - oh my eyes must be really going to miss that one!!



Techies Law strikes again, as soon as I ask for help I find a fix and end up looking stupid!






share|improve this answer





















  • It's a little like rubber duck debugging... :)
    – Stese
    Dec 13 at 9:47
















0














LOL - Sorry - total dinlow, just did a ping to the sites domain on the server and got a reply and noticed that nslookup returned a different IP address I was using 178.xx on the working machine and 173.xx on this one - oh my eyes must be really going to miss that one!!



Techies Law strikes again, as soon as I ask for help I find a fix and end up looking stupid!






share|improve this answer





















  • It's a little like rubber duck debugging... :)
    – Stese
    Dec 13 at 9:47














0












0








0






LOL - Sorry - total dinlow, just did a ping to the sites domain on the server and got a reply and noticed that nslookup returned a different IP address I was using 178.xx on the working machine and 173.xx on this one - oh my eyes must be really going to miss that one!!



Techies Law strikes again, as soon as I ask for help I find a fix and end up looking stupid!






share|improve this answer












LOL - Sorry - total dinlow, just did a ping to the sites domain on the server and got a reply and noticed that nslookup returned a different IP address I was using 178.xx on the working machine and 173.xx on this one - oh my eyes must be really going to miss that one!!



Techies Law strikes again, as soon as I ask for help I find a fix and end up looking stupid!







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 27 at 23:52









MonkeyMagix

1111




1111












  • It's a little like rubber duck debugging... :)
    – Stese
    Dec 13 at 9:47


















  • It's a little like rubber duck debugging... :)
    – Stese
    Dec 13 at 9:47
















It's a little like rubber duck debugging... :)
– Stese
Dec 13 at 9:47




It's a little like rubber duck debugging... :)
– Stese
Dec 13 at 9:47


















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1383245%2ftrying-to-get-windows-8-1-remte-desktop-to-work-on-a-newly-cleaned-laptop%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How do I know what Microsoft account the skydrive app is syncing to?

When does type information flow backwards in C++?

Grease: Live!