Computer not listed after setting up Remote Desktop.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have just set-up the Remote Desktop on my Xp Pro, but when I try to make the connection from the "Computer" pull down on Remote Desktop Connection, my computer is not in the list. The firewall is disabled and security has been set to allow Everyone on my intranet access. What am I missing?
 
Browsing for RD enabled boxes does not work in a work group environment, but you can perform a
registry hack to get this to work. Otherwise simply use the LAN IP or NetBIOS name to call.

http://support.microsoft.com/default.aspx?scid=kb;en-us;281307

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

Ron said:
I have just set-up the Remote Desktop on my Xp Pro, but when I try to make the connection from the
Click to expand...
"Computer" pull down on Remote Desktop Connection, my computer is not in the list. The firewall is
disabled and security has been set to allow Everyone on my intranet access. What am I missing?
 
I have tried that and i get an error stating that the client could not connect to the remote computer. It says that the computers RD might not be enabled or it is too busy. Neither is the case, unless the problem is is that the other computer has a user logged on.
 
On my home LAN it takes a few seconds for my work group to be seen. Then I need to expand the work
group to see the PCs, I have three XP Pro boxes, on my LAN in the browser window.

So RD is enabled on the target PC?

http://www.microsoft.com/windowsxp/pro/using/howto/gomobile/remotedesktop/default.asp

Is this on a LAN? Can you call using the LAN IP of the PC you want to RD into?

Have you checked to see if RD is actually listening on TCP Port 3389 on the PC? See if RD is
actually listening on TCP Port 3389. On the target XP Pro machine go to "Start -> Run", type 'cmd'
(without the quotes). At the command line type the command 'netstat -a' (without the quotes). Look
for a line like this.

TCP <Your PC>:3389 <Your PC>:0 LISTENING

For example on my XP Pro desktop, Ashtabula, the line looks like this using the default port 3389.

TCP ashtabula:3389 ashtabula:0 LISTENING

The line should be present...If the Remote Desktop host is not running, then you will not see a line
like that and you will not be able to connect. If you run services.msc on the target machine is the
"Terminal Services" service started? Also, check the Event log to see if anything stands out when
you try to connect.

Also, you can't call your own PC...:-)

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

Ron said:
I have tried that and i get an error stating that the client could not connect to the remote
Click to expand...
computer. It says that the computers RD might not be enabled or it is too busy. Neither is the
case, unless the problem is is that the other computer has a user logged on.
 
Yes it is...but i found out the problem. I was trying to connect with a Xp to a Win2K and that doesn't work. It only works from the 2K to the Xp. If you have any tricks to making it work the other way, i would be most interested.
 
Remote desktop (or terminal services) isn't available on Windows 2000
Professional. It IS available on Windows 2000 server versions.

For Windows 2000 pro, NetMeetings remote desktop sharing, or third-party
apps like VNC as mentioned elsewhere in this thread, I think--are needed.


Ron said:
Yes it is...but i found out the problem. I was trying to connect with a
Click to expand...
Xp to a Win2K and that doesn't work. It only works from the 2K to the Xp.
If you have any tricks to making it work the other way, i would be most
interested.
 
Well, my company is converting all our Win2K systems to Xp, so i guess i can wait.

Thank you guys for all your help.

----- Bill Sanderson wrote: -----

Remote desktop (or terminal services) isn't available on Windows 2000
Professional. It IS available on Windows 2000 server versions.

For Windows 2000 pro, NetMeetings remote desktop sharing, or third-party
apps like VNC as mentioned elsewhere in this thread, I think--are needed.


Ron said:
Yes it is...but i found out the problem. I was trying to connect with a
Click to expand...
Xp to a Win2K and that doesn't work. It only works from the 2K to the Xp.
If you have any tricks to making it work the other way, i would be most
interested.
 
Back
Top