Answered by:
Unable to Remote Connect to Client PC

Question
-
Server has WHS 2011 with all available updates as of 12/21/2011. Client PCs have the client app installed and are running XP Home SP3 and Win 7 Pro. Router is D-Link DIR-825 with latest firmware and ports 80, 443, 3389 and 4125 forwarded to the WHS IP. When I go to the xxxx.homeserver.com and login, I see the two client PCs listed. I know that I cannot connect to the XP Home box. I am trying to connect to the Win 7 box and it says "available". If I click on the Connect button, I get a message that "Remote Desktop can't find the computer "xxxx"". This might mean that "xxxx" does not belong to the specified network...." Tried pinging the client from the server and it cannot find the box. The client is set for DHCP using the router as the DHCP server. Router, server and client are on same subnet. Client can connect to WHS via shared folders or dashboard. I did notice that the clients were listed in a different workgroup than the WHS box but I learned in another thread on this forum that this is not factor as WHS will manage the clients no matter which workgroup is listed. Seems like a DNS type issue but I cannot figure out how to proceed further. Would appreciate any guidance in resolving this issue.Wednesday, December 21, 2011 7:43 PM
Answers
-
Solved it. The client had Norton 360 v5 installed on the workstations. Once I went into the Network settings and applied "Full Trust" on all network PCs, the remote login began to work. I should have thought of this in the first place.
Thanks for the feedback.
- Marked as answer by 75080Bill Friday, December 30, 2011 6:27 PM
Friday, December 30, 2011 6:27 PM
All replies
-
Yes, Workgroup is not the issue here.
Firstly, as far as Remote access from the Internet is concerned, you actually only need Port 443 forwarded to your Server (for https:// access) and optionally Port 80 (http:// access - albeit the Dashboard will complain that your router is not working if not forwarded but you can still access it with https://). However, Remote Access is also not your problem as you have internal network issues (can't ping Client from Server).
What happens if you try pinging the Client from the Server using the Client IP address? Equally can you ping the Server with both name and IP address? In your router, does it show both Client and Server as DHCP connected clients? Try restarting firstly your router and then Server if you have not already done so.
Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.Wednesday, December 21, 2011 8:00 PM -
I am having the same (i think) problem. I have the WHS2011 server with two WIN7 ultimate PCs (one 64 bit, the other 32 bit O/S). I can connect thru WHS2011 to the 64bit PC but the 32bit give the error BILL mentioned.
Everything shows as available when first connected th WHS2011. Also, once I remote into 64bit system I can then remote int 32bit system; just can't got frm WHS DIRECTLY TO 32bit. I've compared everything I can think of, everything looks the same.
Help?
Wednesday, December 21, 2011 8:17 PM -
Solved it. The client had Norton 360 v5 installed on the workstations. Once I went into the Network settings and applied "Full Trust" on all network PCs, the remote login began to work. I should have thought of this in the first place.
Thanks for the feedback.
- Marked as answer by 75080Bill Friday, December 30, 2011 6:27 PM
Friday, December 30, 2011 6:27 PM -
I saw something mentioned about this on PC world or CNET that only has this problem with XP. I also read the warning that were posted about a headless install where you have to leave pacific time loaded on your new install, no where your at in the world. Then leave it online for 24 hours for some reason, after the same new install, then you can start adjusting things on the server. I didn't have that problem, but I did see it on PC world technet.Monday, May 28, 2012 3:07 AM