Chenlo
New Member
- Joined
- Jan 22, 2016
- Messages
- 8
- Thread Author
-
- #1
Hello all, this is my first post in the forum, New member here...
I upgraded to win10 recently and RDP keeps giving me error above... I have tried with both accounts I have and I can't rdp in. Can anyone tell me how to fix this problem? I've been trying for a few days already and everything seems to be setup OK...
This is a workgroup PC not on a domain and it used to work fine when I was in WIN7...I also notice that my public share also prompts me for a user and password and I get the same error ... as above ...
Things I have tried:
-Verified RDP is enabled and allowed on settings and firewall
-RDP port -- Open
-Firewall down tests
-Removed AV
-I'm able to ping IP
-login using computername\accountname
I hope someone has the answer to this one so I can stop scratching my head
Thank You All
I upgraded to win10 recently and RDP keeps giving me error above... I have tried with both accounts I have and I can't rdp in. Can anyone tell me how to fix this problem? I've been trying for a few days already and everything seems to be setup OK...
This is a workgroup PC not on a domain and it used to work fine when I was in WIN7...I also notice that my public share also prompts me for a user and password and I get the same error ... as above ...
Things I have tried:
-Verified RDP is enabled and allowed on settings and firewall
-RDP port -- Open
-Firewall down tests
-Removed AV
-I'm able to ping IP
-login using computername\accountname
I hope someone has the answer to this one so I can stop scratching my head
Thank You All
Solution
You can get that error if the connection is blocked. Might want to install wireshark and filter for tcp.port == 3389 and see what you get.
- Joined
- Jul 4, 2015
- Messages
- 8,998
Well I just popped up a WinXP VM and Win 10 VM and I was able to RDP from XP to 10. The only changes I made were on the Win 10 box. Enabled Allow Remote Desktop, set the network type to Private and Allowed RDP through the firewall.
Chenlo
New Member
- Joined
- Jan 22, 2016
- Messages
- 8
- Thread Author
-
- #8
Yeah, that's why this is driving me crazy....I have all those settings correct...Well I just popped up a WinXP VM and Win 10 VM and I was able to RDP from XP to 10. The only changes I made were on the Win 10 box. Enabled Allow Remote Desktop, set the network type to Private and Allowed RDP through the firewall.
No idea why It's not working ...
Chenlo
New Member
- Joined
- Jan 22, 2016
- Messages
- 8
- Thread Author
-
- #11
Set-NetConnectionProfile -NetworkCategory PrivateYou may want to switch Win 7 to Private you can switch it from an elevated powershell prompt with Set-NetConnectionProfile -NetworkCategpry Private
The term 'Set-NetConnectionProfile' is not recognized as the name of a cmdlet, function, script file, or operable progr
am. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:25
+ Set-NetConnectionProfile <<<< -NetworkCategpry Private
+ CategoryInfo : ObjectNotFound: (Set-NetConnectionProfile:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Chenlo
New Member
- Joined
- Jan 22, 2016
- Messages
- 8
- Thread Author
-
- #17
It is running ...You did turn it on?
View attachment 31705
Last edited by a moderator:
- Joined
- May 22, 2012
- Messages
- 4,568
so you can ping the wx computer name... not just it's ip address?-I'm able to ping IP
if you can ping the computer name and it replies then it most likly is your w7 username / password that is getting blocked but at this point I want some screen shots of the errors you get so we can see the issue please
Similar threads
- Replies
- 10
- Views
- 2K
- Replies
- 1
- Views
- 1K
- Solved
- Replies
- 5
- Views
- 2K
- Solved
- Replies
- 7
- Views
- 2K