Remote Desktop cannot connect to the remote windows 8 computer from windows 7
up vote
2
down vote
favorite
I have computer with installed windows 8 pro at home. This computer plugged in to router via LAN cable. I configured remote desktop on this computer: System Properties -> Remote -> Allow remote connections to this computer ("Allow connections only from computers running Remote Desktop with Network Level Authentication" unchecked). I also configured router to forward the Remote Desktop port (3389) from the Internet IP address of router to the Local IP of my host. I checked forwarding at http://www.yougetsignal.com/tools/open-ports/ - Port 3389 is open.
I can connect to windows 8 pc from my mobile phone (windows phone 7.8, via RemoteDesktop application). But it is not convenient.
I can't connect to home pc from work (Windows 7 Pro). I have the following error:
"Remote desktop can't connect to the remote computer for one of these reasons:
1) Remote access to the server is not enabled
2) The remote computer is turned off
3) The remote computer is not available on the network
Make sure the remote computer is turned on and connected to the network, and that remote access is enabled. "
I can connect to home pc from work via mobile phone, but from work pc I get error. Is on work PC any other configurations to connect to win 8?
UPD: I have to use proxy server at work, is it might cause problems?
windows remote-desktop
migrated from stackoverflow.com Mar 12 '13 at 10:07
This question came from our site for professional and enthusiast programmers.
add a comment |
up vote
2
down vote
favorite
I have computer with installed windows 8 pro at home. This computer plugged in to router via LAN cable. I configured remote desktop on this computer: System Properties -> Remote -> Allow remote connections to this computer ("Allow connections only from computers running Remote Desktop with Network Level Authentication" unchecked). I also configured router to forward the Remote Desktop port (3389) from the Internet IP address of router to the Local IP of my host. I checked forwarding at http://www.yougetsignal.com/tools/open-ports/ - Port 3389 is open.
I can connect to windows 8 pc from my mobile phone (windows phone 7.8, via RemoteDesktop application). But it is not convenient.
I can't connect to home pc from work (Windows 7 Pro). I have the following error:
"Remote desktop can't connect to the remote computer for one of these reasons:
1) Remote access to the server is not enabled
2) The remote computer is turned off
3) The remote computer is not available on the network
Make sure the remote computer is turned on and connected to the network, and that remote access is enabled. "
I can connect to home pc from work via mobile phone, but from work pc I get error. Is on work PC any other configurations to connect to win 8?
UPD: I have to use proxy server at work, is it might cause problems?
windows remote-desktop
migrated from stackoverflow.com Mar 12 '13 at 10:07
This question came from our site for professional and enthusiast programmers.
When you connect from work via mobile phone do you use work wireless or 3G/4G? This may answer why it works on your phone all the time - it's using your 3G/4G data allowance. When using work computer do you know if your work block outbound connections to port 3389? - my work do.
– Kinnectus
May 11 '15 at 15:51
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I have computer with installed windows 8 pro at home. This computer plugged in to router via LAN cable. I configured remote desktop on this computer: System Properties -> Remote -> Allow remote connections to this computer ("Allow connections only from computers running Remote Desktop with Network Level Authentication" unchecked). I also configured router to forward the Remote Desktop port (3389) from the Internet IP address of router to the Local IP of my host. I checked forwarding at http://www.yougetsignal.com/tools/open-ports/ - Port 3389 is open.
I can connect to windows 8 pc from my mobile phone (windows phone 7.8, via RemoteDesktop application). But it is not convenient.
I can't connect to home pc from work (Windows 7 Pro). I have the following error:
"Remote desktop can't connect to the remote computer for one of these reasons:
1) Remote access to the server is not enabled
2) The remote computer is turned off
3) The remote computer is not available on the network
Make sure the remote computer is turned on and connected to the network, and that remote access is enabled. "
I can connect to home pc from work via mobile phone, but from work pc I get error. Is on work PC any other configurations to connect to win 8?
UPD: I have to use proxy server at work, is it might cause problems?
windows remote-desktop
I have computer with installed windows 8 pro at home. This computer plugged in to router via LAN cable. I configured remote desktop on this computer: System Properties -> Remote -> Allow remote connections to this computer ("Allow connections only from computers running Remote Desktop with Network Level Authentication" unchecked). I also configured router to forward the Remote Desktop port (3389) from the Internet IP address of router to the Local IP of my host. I checked forwarding at http://www.yougetsignal.com/tools/open-ports/ - Port 3389 is open.
I can connect to windows 8 pc from my mobile phone (windows phone 7.8, via RemoteDesktop application). But it is not convenient.
I can't connect to home pc from work (Windows 7 Pro). I have the following error:
"Remote desktop can't connect to the remote computer for one of these reasons:
1) Remote access to the server is not enabled
2) The remote computer is turned off
3) The remote computer is not available on the network
Make sure the remote computer is turned on and connected to the network, and that remote access is enabled. "
I can connect to home pc from work via mobile phone, but from work pc I get error. Is on work PC any other configurations to connect to win 8?
UPD: I have to use proxy server at work, is it might cause problems?
windows remote-desktop
windows remote-desktop
asked Mar 12 '13 at 8:03
Rigidit
migrated from stackoverflow.com Mar 12 '13 at 10:07
This question came from our site for professional and enthusiast programmers.
migrated from stackoverflow.com Mar 12 '13 at 10:07
This question came from our site for professional and enthusiast programmers.
When you connect from work via mobile phone do you use work wireless or 3G/4G? This may answer why it works on your phone all the time - it's using your 3G/4G data allowance. When using work computer do you know if your work block outbound connections to port 3389? - my work do.
– Kinnectus
May 11 '15 at 15:51
add a comment |
When you connect from work via mobile phone do you use work wireless or 3G/4G? This may answer why it works on your phone all the time - it's using your 3G/4G data allowance. When using work computer do you know if your work block outbound connections to port 3389? - my work do.
– Kinnectus
May 11 '15 at 15:51
When you connect from work via mobile phone do you use work wireless or 3G/4G? This may answer why it works on your phone all the time - it's using your 3G/4G data allowance. When using work computer do you know if your work block outbound connections to port 3389? - my work do.
– Kinnectus
May 11 '15 at 15:51
When you connect from work via mobile phone do you use work wireless or 3G/4G? This may answer why it works on your phone all the time - it's using your 3G/4G data allowance. When using work computer do you know if your work block outbound connections to port 3389? - my work do.
– Kinnectus
May 11 '15 at 15:51
add a comment |
5 Answers
5
active
oldest
votes
up vote
0
down vote
I had a similar problem and scratched my head over it for ages. It turned out that I use Kaspersky anti-virus and by default the Kaspersky firewall silently blocks Remote Desktop connections.
Check your AV/firewall settings are ok on your work PC ....
answered Mar 12 '13 at 8:05
Roger Rowland
1313
Firewall settings are ok. I can connect to pc from mobile phone using the 3G connection. So, port 3389 is enabled.
– Rigidit
Mar 12 '13 at 8:09
I mean your outgoing firewall restrictions on your work PC.
– roger_rowland
Mar 12 '13 at 8:13
It looks like that outgoing tcp 3389 is enabled. I checked it in Windows Firewall -> Advanced settings. I also added outbound rule that allow 3389 tcp port. But I have the same error.
– Rigidit
Mar 12 '13 at 8:40
Another quick way to check is to temporarily disable your firewall on your work PC.
– roger_rowland
Mar 12 '13 at 8:42
1
Yes, I found it, I have 2 checked "Remote Desktop" - 1) "Remote Desktop" checked for Domain, Home/Work()Private, Public, Group Policy - Yes; 2) "Remote Desktop" checked for Domain, Home/Work()Private, Public, Group Policy - No;
– Rigidit
Mar 12 '13 at 8:54
|
show 2 more comments
up vote
0
down vote
I'm quite certain this has nothing to do with Windows 7 -> Windows 8. Just the other day I was able to do this.
The nature of that error message indicates the computer that initiated the session was never able to reach or never got a response from the target computer.
This could have happened if the remote address, ip address, etc is incorrect. Firewall/AV settings, proxys would also do this.
Additionally, all the 'pre-setup' configuration you did sounds correct... except for the proxy and or firewall settings and infos.
answered Dec 26 '13 at 2:40
Joe
140129
add a comment |
up vote
0
down vote
You might want to check the security settings. What I mean by this is how the authentication is being passed in the RDP session. I would lower it all the way down and see if that works. If it does, you can increase it until it doesn't work. Make sure the settings are the same on both ends. I had this issue once before and the authentication was the issue.
answered Mar 28 '14 at 17:04
3ngin33r
596
add a comment |
up vote
0
down vote
The problem is that you have to use a proxy at work as you say in the last line.
When you use a proxy for connecting to Internet the computer usually don't have direct/NAT access to Internet, instead programs designed to use a proxy (mostly browsers) connect to the proxy server, then the proxy server retrieves the requested content from Internet (or from a local cache in some cases) and pass it back to your computer.
Most of the time proxies are used for web browsing (and maybe for email), but a lot of programs that use other protocols, including Remote Desktop, needs a direct or NAT connection to Internet.
answered Sep 9 '17 at 16:29
Alberto Martinez
1,217711
add a comment |
up vote
-1
down vote
Try using remote support tools such as LogMeIn, GoSupportNow, GoToMyPC etc. in order to remotely access Windows 8 computer from Windows 7. Check if they work.
edited Aug 28 '13 at 8:10
Jawa
3,15982435
answered Aug 28 '13 at 6:58
user249119
1
add a comment |
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I had a similar problem and scratched my head over it for ages. It turned out that I use Kaspersky anti-virus and by default the Kaspersky firewall silently blocks Remote Desktop connections.
Check your AV/firewall settings are ok on your work PC ....
answered Mar 12 '13 at 8:05
Roger Rowland
1313
Firewall settings are ok. I can connect to pc from mobile phone using the 3G connection. So, port 3389 is enabled.
– Rigidit
Mar 12 '13 at 8:09
I mean your outgoing firewall restrictions on your work PC.
– roger_rowland
Mar 12 '13 at 8:13
It looks like that outgoing tcp 3389 is enabled. I checked it in Windows Firewall -> Advanced settings. I also added outbound rule that allow 3389 tcp port. But I have the same error.
– Rigidit
Mar 12 '13 at 8:40
Another quick way to check is to temporarily disable your firewall on your work PC.
– roger_rowland
Mar 12 '13 at 8:42
1
Yes, I found it, I have 2 checked "Remote Desktop" - 1) "Remote Desktop" checked for Domain, Home/Work()Private, Public, Group Policy - Yes; 2) "Remote Desktop" checked for Domain, Home/Work()Private, Public, Group Policy - No;
– Rigidit
Mar 12 '13 at 8:54
|
show 2 more comments
up vote
0
down vote
I had a similar problem and scratched my head over it for ages. It turned out that I use Kaspersky anti-virus and by default the Kaspersky firewall silently blocks Remote Desktop connections.
Check your AV/firewall settings are ok on your work PC ....
answered Mar 12 '13 at 8:05
Roger Rowland
1313
Firewall settings are ok. I can connect to pc from mobile phone using the 3G connection. So, port 3389 is enabled.
– Rigidit
Mar 12 '13 at 8:09
I mean your outgoing firewall restrictions on your work PC.
– roger_rowland
Mar 12 '13 at 8:13
It looks like that outgoing tcp 3389 is enabled. I checked it in Windows Firewall -> Advanced settings. I also added outbound rule that allow 3389 tcp port. But I have the same error.
– Rigidit
Mar 12 '13 at 8:40
Another quick way to check is to temporarily disable your firewall on your work PC.
– roger_rowland
Mar 12 '13 at 8:42
1
Yes, I found it, I have 2 checked "Remote Desktop" - 1) "Remote Desktop" checked for Domain, Home/Work()Private, Public, Group Policy - Yes; 2) "Remote Desktop" checked for Domain, Home/Work()Private, Public, Group Policy - No;
– Rigidit
Mar 12 '13 at 8:54
|
show 2 more comments
up vote
0
down vote
up vote
0
down vote
I had a similar problem and scratched my head over it for ages. It turned out that I use Kaspersky anti-virus and by default the Kaspersky firewall silently blocks Remote Desktop connections.
Check your AV/firewall settings are ok on your work PC ....
answered Mar 12 '13 at 8:05
Roger Rowland
1313
I had a similar problem and scratched my head over it for ages. It turned out that I use Kaspersky anti-virus and by default the Kaspersky firewall silently blocks Remote Desktop connections.
Check your AV/firewall settings are ok on your work PC ....
answered Mar 12 '13 at 8:05
Roger Rowland
1313
answered Mar 12 '13 at 8:05
Roger Rowland
1313
answered Mar 12 '13 at 8:05
Roger Rowland
1313
answered Mar 12 '13 at 8:05
Roger Rowland
1313
1313
Firewall settings are ok. I can connect to pc from mobile phone using the 3G connection. So, port 3389 is enabled.
– Rigidit
Mar 12 '13 at 8:09
I mean your outgoing firewall restrictions on your work PC.
– roger_rowland
Mar 12 '13 at 8:13
It looks like that outgoing tcp 3389 is enabled. I checked it in Windows Firewall -> Advanced settings. I also added outbound rule that allow 3389 tcp port. But I have the same error.
– Rigidit
Mar 12 '13 at 8:40
Another quick way to check is to temporarily disable your firewall on your work PC.
– roger_rowland
Mar 12 '13 at 8:42
1
Yes, I found it, I have 2 checked "Remote Desktop" - 1) "Remote Desktop" checked for Domain, Home/Work()Private, Public, Group Policy - Yes; 2) "Remote Desktop" checked for Domain, Home/Work()Private, Public, Group Policy - No;
– Rigidit
Mar 12 '13 at 8:54
|
show 2 more comments
Firewall settings are ok. I can connect to pc from mobile phone using the 3G connection. So, port 3389 is enabled.
– Rigidit
Mar 12 '13 at 8:09
I mean your outgoing firewall restrictions on your work PC.
– roger_rowland
Mar 12 '13 at 8:13
It looks like that outgoing tcp 3389 is enabled. I checked it in Windows Firewall -> Advanced settings. I also added outbound rule that allow 3389 tcp port. But I have the same error.
– Rigidit
Mar 12 '13 at 8:40
Another quick way to check is to temporarily disable your firewall on your work PC.
– roger_rowland
Mar 12 '13 at 8:42
1
Yes, I found it, I have 2 checked "Remote Desktop" - 1) "Remote Desktop" checked for Domain, Home/Work()Private, Public, Group Policy - Yes; 2) "Remote Desktop" checked for Domain, Home/Work()Private, Public, Group Policy - No;
– Rigidit
Mar 12 '13 at 8:54
Firewall settings are ok. I can connect to pc from mobile phone using the 3G connection. So, port 3389 is enabled.
– Rigidit
Mar 12 '13 at 8:09
Firewall settings are ok. I can connect to pc from mobile phone using the 3G connection. So, port 3389 is enabled.
– Rigidit
Mar 12 '13 at 8:09
I mean your outgoing firewall restrictions on your work PC.
– roger_rowland
Mar 12 '13 at 8:13
I mean your outgoing firewall restrictions on your work PC.
– roger_rowland
Mar 12 '13 at 8:13
It looks like that outgoing tcp 3389 is enabled. I checked it in Windows Firewall -> Advanced settings. I also added outbound rule that allow 3389 tcp port. But I have the same error.
– Rigidit
Mar 12 '13 at 8:40
It looks like that outgoing tcp 3389 is enabled. I checked it in Windows Firewall -> Advanced settings. I also added outbound rule that allow 3389 tcp port. But I have the same error.
– Rigidit
Mar 12 '13 at 8:40
Another quick way to check is to temporarily disable your firewall on your work PC.
– roger_rowland
Mar 12 '13 at 8:42
Another quick way to check is to temporarily disable your firewall on your work PC.
– roger_rowland
Mar 12 '13 at 8:42
1
1
Yes, I found it, I have 2 checked "Remote Desktop" - 1) "Remote Desktop" checked for Domain, Home/Work()Private, Public, Group Policy - Yes; 2) "Remote Desktop" checked for Domain, Home/Work()Private, Public, Group Policy - No;
– Rigidit
Mar 12 '13 at 8:54
Yes, I found it, I have 2 checked "Remote Desktop" - 1) "Remote Desktop" checked for Domain, Home/Work()Private, Public, Group Policy - Yes; 2) "Remote Desktop" checked for Domain, Home/Work()Private, Public, Group Policy - No;
– Rigidit
Mar 12 '13 at 8:54
|
show 2 more comments
up vote
0
down vote
I'm quite certain this has nothing to do with Windows 7 -> Windows 8. Just the other day I was able to do this.
The nature of that error message indicates the computer that initiated the session was never able to reach or never got a response from the target computer.
This could have happened if the remote address, ip address, etc is incorrect. Firewall/AV settings, proxys would also do this.
Additionally, all the 'pre-setup' configuration you did sounds correct... except for the proxy and or firewall settings and infos.
answered Dec 26 '13 at 2:40
Joe
140129
add a comment |
up vote
0
down vote
I'm quite certain this has nothing to do with Windows 7 -> Windows 8. Just the other day I was able to do this.
The nature of that error message indicates the computer that initiated the session was never able to reach or never got a response from the target computer.
This could have happened if the remote address, ip address, etc is incorrect. Firewall/AV settings, proxys would also do this.
Additionally, all the 'pre-setup' configuration you did sounds correct... except for the proxy and or firewall settings and infos.
answered Dec 26 '13 at 2:40
Joe
140129
add a comment |
up vote
0
down vote
up vote
0
down vote
I'm quite certain this has nothing to do with Windows 7 -> Windows 8. Just the other day I was able to do this.
The nature of that error message indicates the computer that initiated the session was never able to reach or never got a response from the target computer.
This could have happened if the remote address, ip address, etc is incorrect. Firewall/AV settings, proxys would also do this.
Additionally, all the 'pre-setup' configuration you did sounds correct... except for the proxy and or firewall settings and infos.
answered Dec 26 '13 at 2:40
Joe
140129
I'm quite certain this has nothing to do with Windows 7 -> Windows 8. Just the other day I was able to do this.
The nature of that error message indicates the computer that initiated the session was never able to reach or never got a response from the target computer.
This could have happened if the remote address, ip address, etc is incorrect. Firewall/AV settings, proxys would also do this.
Additionally, all the 'pre-setup' configuration you did sounds correct... except for the proxy and or firewall settings and infos.
answered Dec 26 '13 at 2:40
Joe
140129
answered Dec 26 '13 at 2:40
Joe
140129
answered Dec 26 '13 at 2:40
Joe
140129
answered Dec 26 '13 at 2:40
Joe
140129
140129
add a comment |
add a comment |
up vote
0
down vote
You might want to check the security settings. What I mean by this is how the authentication is being passed in the RDP session. I would lower it all the way down and see if that works. If it does, you can increase it until it doesn't work. Make sure the settings are the same on both ends. I had this issue once before and the authentication was the issue.
answered Mar 28 '14 at 17:04
3ngin33r
596
add a comment |
up vote
0
down vote
You might want to check the security settings. What I mean by this is how the authentication is being passed in the RDP session. I would lower it all the way down and see if that works. If it does, you can increase it until it doesn't work. Make sure the settings are the same on both ends. I had this issue once before and the authentication was the issue.
answered Mar 28 '14 at 17:04
3ngin33r
596
add a comment |
up vote
0
down vote
up vote
0
down vote
You might want to check the security settings. What I mean by this is how the authentication is being passed in the RDP session. I would lower it all the way down and see if that works. If it does, you can increase it until it doesn't work. Make sure the settings are the same on both ends. I had this issue once before and the authentication was the issue.
answered Mar 28 '14 at 17:04
3ngin33r
596
You might want to check the security settings. What I mean by this is how the authentication is being passed in the RDP session. I would lower it all the way down and see if that works. If it does, you can increase it until it doesn't work. Make sure the settings are the same on both ends. I had this issue once before and the authentication was the issue.
answered Mar 28 '14 at 17:04
3ngin33r
596
answered Mar 28 '14 at 17:04
3ngin33r
596
answered Mar 28 '14 at 17:04
3ngin33r
596
answered Mar 28 '14 at 17:04
3ngin33r
596
596
add a comment |
add a comment |
up vote
0
down vote
The problem is that you have to use a proxy at work as you say in the last line.
When you use a proxy for connecting to Internet the computer usually don't have direct/NAT access to Internet, instead programs designed to use a proxy (mostly browsers) connect to the proxy server, then the proxy server retrieves the requested content from Internet (or from a local cache in some cases) and pass it back to your computer.
Most of the time proxies are used for web browsing (and maybe for email), but a lot of programs that use other protocols, including Remote Desktop, needs a direct or NAT connection to Internet.
answered Sep 9 '17 at 16:29
Alberto Martinez
1,217711
add a comment |
up vote
0
down vote
The problem is that you have to use a proxy at work as you say in the last line.
When you use a proxy for connecting to Internet the computer usually don't have direct/NAT access to Internet, instead programs designed to use a proxy (mostly browsers) connect to the proxy server, then the proxy server retrieves the requested content from Internet (or from a local cache in some cases) and pass it back to your computer.
Most of the time proxies are used for web browsing (and maybe for email), but a lot of programs that use other protocols, including Remote Desktop, needs a direct or NAT connection to Internet.
answered Sep 9 '17 at 16:29
Alberto Martinez
1,217711
add a comment |
up vote
0
down vote
up vote
0
down vote
The problem is that you have to use a proxy at work as you say in the last line.
When you use a proxy for connecting to Internet the computer usually don't have direct/NAT access to Internet, instead programs designed to use a proxy (mostly browsers) connect to the proxy server, then the proxy server retrieves the requested content from Internet (or from a local cache in some cases) and pass it back to your computer.
Most of the time proxies are used for web browsing (and maybe for email), but a lot of programs that use other protocols, including Remote Desktop, needs a direct or NAT connection to Internet.
answered Sep 9 '17 at 16:29
Alberto Martinez
1,217711
The problem is that you have to use a proxy at work as you say in the last line.
When you use a proxy for connecting to Internet the computer usually don't have direct/NAT access to Internet, instead programs designed to use a proxy (mostly browsers) connect to the proxy server, then the proxy server retrieves the requested content from Internet (or from a local cache in some cases) and pass it back to your computer.
Most of the time proxies are used for web browsing (and maybe for email), but a lot of programs that use other protocols, including Remote Desktop, needs a direct or NAT connection to Internet.
answered Sep 9 '17 at 16:29
Alberto Martinez
1,217711
answered Sep 9 '17 at 16:29
Alberto Martinez
1,217711
answered Sep 9 '17 at 16:29
Alberto Martinez
1,217711
answered Sep 9 '17 at 16:29
Alberto Martinez
1,217711
1,217711
add a comment |
add a comment |
up vote
-1
down vote
Try using remote support tools such as LogMeIn, GoSupportNow, GoToMyPC etc. in order to remotely access Windows 8 computer from Windows 7. Check if they work.
edited Aug 28 '13 at 8:10
Jawa
3,15982435
answered Aug 28 '13 at 6:58
user249119
1
add a comment |
up vote
-1
down vote
Try using remote support tools such as LogMeIn, GoSupportNow, GoToMyPC etc. in order to remotely access Windows 8 computer from Windows 7. Check if they work.
edited Aug 28 '13 at 8:10
Jawa
3,15982435
answered Aug 28 '13 at 6:58
user249119
1
add a comment |
up vote
-1
down vote
up vote
-1
down vote
Try using remote support tools such as LogMeIn, GoSupportNow, GoToMyPC etc. in order to remotely access Windows 8 computer from Windows 7. Check if they work.
edited Aug 28 '13 at 8:10
Jawa
3,15982435
answered Aug 28 '13 at 6:58
user249119
1
Try using remote support tools such as LogMeIn, GoSupportNow, GoToMyPC etc. in order to remotely access Windows 8 computer from Windows 7. Check if they work.
edited Aug 28 '13 at 8:10
Jawa
3,15982435
answered Aug 28 '13 at 6:58
user249119
1
edited Aug 28 '13 at 8:10
Jawa
3,15982435
edited Aug 28 '13 at 8:10
Jawa
3,15982435
edited Aug 28 '13 at 8:10
Jawa
3,15982435
3,15982435
answered Aug 28 '13 at 6:58
user249119
1
answered Aug 28 '13 at 6:58
user249119
1
answered Aug 28 '13 at 6:58
user249119
1
1
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f564592%2fremote-desktop-cannot-connect-to-the-remote-windows-8-computer-from-windows-7%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
When you connect from work via mobile phone do you use work wireless or 3G/4G? This may answer why it works on your phone all the time - it's using your 3G/4G data allowance. When using work computer do you know if your work block outbound connections to port 3389? - my work do.
– Kinnectus
May 11 '15 at 15:51