[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 294
  • Last Modified:

Remote Desktop Connection ERROR: "The client could not connect to the remote computer"

Remote Desktop Connection ERROR: "The client could not connect to the remote computer"

          On my home WAN I have always connected to my desktop using remote desktop on my laptop until I had to reset my D-link router (DI-824vup) the other day. I had to do a factory reset on the router and I also released and renewed the desktop IP (I don’t know if that means anything).
           I configured the firewall settings in the router config- and the firewall is disabled - windows pro settings have not changed since before the router reset and everything is still setup for allowing remote desktop connections in windows XP- windows firewall port is open, R. Desktop is enabled under system properties etc etc etc.

Any suggestions? What else could I have overlooked in my router config.? (I assume the router has a setting I overlooked because as I mentioned earlier the settings in windows pro have not been modified).

Thanks in advance!
0
scottsch27
Asked:
scottsch27
  • 3
  • 2
1 Solution
 
baconyiCommented:
since the router was reset, you have to renew the ip on the desktop, make sure when you connect with remote desktop that it is pointing to the right ip address.
Billy
0
 
scottsch27Author Commented:
OK, that worked - I used the ip from ipconfig in CMD just now...

So why is this new ip just an extension of my router ip address- like 192.168.0.343 ?? Before my desktop ip was unique from the router ip...  

Will I be able to use this new ip away from home or will it only work on my home WAN ? Does this make sense?
0
 
baconyiCommented:
i dont know why your desktop ip was different from the router's, it should be on the same network unless you had 2 routers connected to each other... default network address is usually 192.168.1.X.  the router's address is usually .1, and then in the router settings, it is configured to hand out ip addresses usually a range of .50-100, or .100-.150 so for instance if your router is 192.168.6.1, then your dhcp range should be 192.168.6.50 - 192.168.6.100, and whatever computer connected to this router will have an ip between those numbers, only the last number changes.  BTW - if your subnet address is 255.255.255.0 then your ip address can only range from .1 -to .254

also, i dont know how you had it set up to access from outside, but before that can be done, you must first have some kind of authentication method to be on the same network, 192.'s are internal network addresses or Local Area Network addresses (LAN's).  WAN is Wide Area Network which is what you refered to. Your current set up will only allow LAN access (your home network).

there are methods to create virtual tunnels so outside can access in, but thats a whole different topic that can get complicated.  certain software/hardware may be needed to acheive this.  for instance a hardware firewall device like SonicWall that can do something called site to site VPN(Virtual Private Network) that links 2 locations as if it was one.  OR some devices have port forwarding which when you remote to the WAN address, it will then forward that request to a specific IP address.  for example, if you set up port forwarding on your home router to have the WAN address forward remote desktop to your desktop's IP address, then whatever computer from outside your home LAN can VPN to that external address(WAN) and then it directs(forwards) that request to your desktop.
i think the easiest way without all that configuring is pc anywhere or something like that.

ok that was just the basic explanation.  any other questions feel free to ask, or if you wanted me to clear up on something in this post.
Billy
0
 
scottsch27Author Commented:
wow more info than i wanted but thanks-

i used to connect to remotely from insdie and outside my home wan with the ip address i got from the internet site like whatsmyip.com- that ip address was always different from the router- and it always worked without any extra hardware or configuration.. i have never connected remotely with a router ip- so thanks again - its working (at home anyway).
0
 
baconyiCommented:
ok, then someone did setup port forwarding on your router, because when you do the whatsmyip.com or myipaddress.com it tells you your WAN address, then your router was configured to forward that to a specific address on your LAN.  remember WAN is outside address, anyone can see that address, LAN is your internal(home) address and only anyone that can get on the same router can see those addresses.

btw, if you want to set up the forwarding again, post another question with specific brand/model/version or firmware version of the router so people can help set that up for you.
good luck
Bill

0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now