About Remote Desktop on Windows...

[Dephin -PC-]

I have enabled everything I could find to make this work but it just keeps saying it's to busy. Could someone point me to a tutorial that could help me out??

[Dephin -PC-]

The exact error message is:

The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connection. Please try connecting again later. If the problem continues to occur, contact your administrator.

That's when I put the IP of the computer in. I can't browse because it says I have no computer on the terminal. I know it has something to do with my network, just not sure how to fix. I just have a simple "Home Network" with all the computers connected through a router/modem. Thanks...

[faulkner132]

What is the address you are entering into the Remote Desktop Connection client?

[Dephin -PC-]

The IP address for the computers. I've always tried entering the computers name. I pulled up the cmd prompt and did an IP Config to pull up my IP. It's the 192.168.X.XXX router IP address for the few computers we have...

[glc]

Is remote desktop enabled in the XP firewall exception list?

[Dephin -PC-]

I have it enabled on the "System/Restore" control configuration, the "Windows Firewall/Advanced/LAN Settings" control list, and on the "Windows Firewall/Exceptions" list...

[faulkner132]

What happens when you run this from the command prompt (enter appropriate router IP):

telnet 192.168.x.xxx 3389

If the screen goes blank everything is good with respect to your firewall.

[ITlover]

I think GLC is talking about Exception list in Firewall setting where you have to put a check on each services that you dont want firewall to block, it is not the Advance tab.

GLC, if their is 2 network connected to each other via router, and If I want to access a destination Computer in 2nd network, then in remote desktop connection window do I have to mention the IP address of the router's interface with which my network is connected or do I simply have to mention the IP address of the destination Computer in remote desktop connection?

As far as I know an admin has the privallege by default to connect to the destination computer via remote desktop connection.
Can their be a problem in the cables connected to the routers interface with which his network is connected?

[glc]

In order to access a computer that is behind a NAT router, port 3389 has to be forwarded to the local IP of the computer you wish to access and you have to connect to the WAN IP.

This does not apply to the thread starter's situation, he is simply trying to access computers on his single LAN.

To see if it's a firewall issue, disable the firewall completely.

[ITlover]

Should I start another thread in "Networking and Internet connection" to discuss what I have just asked here?

[Alaron]

Originally Posted by ITlover Should I start another thread in "Networking and Internet connection" to discuss what I have just asked here?

Yes, so you don't take over Dephin's thread.

[ITlover]

ok, I have started the thread in "networking and internet connection" forum.

[Dephin -PC-]

Originally Posted by faulkner132 What happens when you run this from the command prompt (enter appropriate router IP): telnet 192.168.x.xxx 3389 If the screen goes blank everything is good with respect to your firewall.

I tried the IP address to the computer I ran the cmd on and the following message appeared.

Could not open the connection to the host, on port 3389.
Connect failed

I tried connecting to a different IP on the network and it says the same failed connection...

[Dephin -PC-]

Originally Posted by ITlover I think GLC is talking about Exception list in Firewall setting where you have to put a check on each services that you dont want firewall to block, it is not the Advance tab.

I did go to the firewall settings and check those boxes... I was just showing the tabs and parts I went to... I went to control panel... Clicked on the firewall settings... and so on and so on...