Problem with Remote Desktop ...

J

Joe Duchtel

Hello -

I have a problem where I cannot connect to an XP machine (SP2) that
has Remote Dektop turned on. I checked unter the properties of My
Computer under the Remote tab that the Remote Desktop is checked and
that my username is in the list of users.

I also turned off our firewall but it still will not connect.

The strange thing is that I don't even get an error message. The
client just blinks and nothing happens. No error message about it not
being able to connect ... nothing.

It seems to find the computer but somehow the computer blocks the
connection. What else could block the remote desktop other than a
firewall.

I have co-workers who have the exact same XP image than I do and we
can connect to their machines just fine.

Is there any tool that I could use to analyze what is going on? I did
check the netstat and it shows port 3389 as listening.

Thanks,
Joe
 
J

Joe Duchtel

Are you running WinXP SP3?

cf.http://support.microsoft.com/kb/951607












- Show quoted text -

Hello -

I am running Windows XP SP2. I checked the article and it talked
about a remote connection using a web browser. I want to use the
Remote Desktop under Start > Programs > Accessories > Communications >
Remote Desktop Connection.

Thanks!
Joe
 
P

Pegasus \(MVP\)

Joe Duchtel said:
Hello -

I have a problem where I cannot connect to an XP machine (SP2) that
has Remote Dektop turned on. I checked unter the properties of My
Computer under the Remote tab that the Remote Desktop is checked and
that my username is in the list of users.

I also turned off our firewall but it still will not connect.

The strange thing is that I don't even get an error message. The
client just blinks and nothing happens. No error message about it not
being able to connect ... nothing.

It seems to find the computer but somehow the computer blocks the
connection. What else could block the remote desktop other than a
firewall.

I have co-workers who have the exact same XP image than I do and we
can connect to their machines just fine.

Is there any tool that I could use to analyze what is going on? I did
check the netstat and it shows port 3389 as listening.

Thanks,
Joe

What do you get when you open a Command Prompt on the remote machine and
type this command:

telnet YourServer 3389
 
J

Joe Duchtel

What do you get when you open a Command Prompt on the remote machine and
type this command:

telnet YourServer 3389- Hide quoted text -

- Show quoted text -

Hello -

I just tried the telnet but it hung up not doing anything. The
"server" is actually another XP (SP2) machine and I'm not sure the
telnet service is enabled on that one by default.

Thanks,
Joe
 
P

Pegasus \(MVP\)

What do you get when you open a Command Prompt on the remote machine and
type this command:

telnet YourServer 3389- Hide quoted text -

- Show quoted text -

Hello -

I just tried the telnet but it hung up not doing anything. The
"server" is actually another XP (SP2) machine and I'm not sure the
telnet service is enabled on that one by default.

Thanks,
Joe

=============

No, telnet did not "hang". It is perfectly normal for the telnet command to
clear the screen when the host responds. Try this variant:
telnet YourSMTPServer 25
Same reaction but this time the server responds with a reply.

Your first test means that port 3389 on the "server" is responding. I would
now run this command from a Command Prompt:
mstsc /v:YourServer
 
J

Joe Duchtel

Hello -

I just tried the telnet but it hung up not doing anything.  The
"server" is actually another XP (SP2) machine and I'm not sure the
telnet service is enabled on that one by default.

Thanks,
Joe

=============

No, telnet did not "hang". It is perfectly normal for the telnet command to
clear the screen when the host responds. Try this variant:
telnet YourSMTPServer 25
Same reaction but this time the server responds with a reply.

Your first test means that port 3389 on the "server" is responding. I would
now run this command from a Command Prompt:
mstsc /v:YourServer- Hide quoted text -

- Show quoted text -

Hello -

Okay ... makes sense!

I tried the mstsc and I can only see a window with Connecting to
MyServer for a fraction of a second before it returns with the command
prompt in the shell. Is there a log on the server I can check?

Thanks!
Joe
 
P

Pegasus \(MVP\)

Hello -

I just tried the telnet but it hung up not doing anything. The
"server" is actually another XP (SP2) machine and I'm not sure the
telnet service is enabled on that one by default.

Thanks,
Joe

=============

No, telnet did not "hang". It is perfectly normal for the telnet command
to
clear the screen when the host responds. Try this variant:
telnet YourSMTPServer 25
Same reaction but this time the server responds with a reply.

Your first test means that port 3389 on the "server" is responding. I
would
now run this command from a Command Prompt:
mstsc /v:YourServer- Hide quoted text -

- Show quoted text -

Hello -

Okay ... makes sense!

I tried the mstsc and I can only see a window with Connecting to
MyServer for a fraction of a second before it returns with the command
prompt in the shell. Is there a log on the server I can check?

Thanks!
Joe
=================
I have no idea what's wrong with your machine. In such cases I run a few
tests, hoping that one of them might turn up something. Here are a few
thoughts:
- Direct the mstsc.exe command to some other WinXP Professional machine. If
it works then you know that there is nothing wrong with the remote machine.
- Check the event viewer on the host machine.
- Use msconfig.exe on the host machine to disable every startup task except
your virus scanner.
- Use msconfig.exe on the host machine to disable every service except for
your virus scanner and the Microsoft services.
 
J

Joe Duchtel

Hello -

Okay ... makes sense!

I tried the mstsc and I can only see a window with Connecting to
MyServer for a fraction of a second before it returns with the command
prompt in the shell.  Is there a log on the server I can check?

Thanks!
Joe
=================
I have no idea what's wrong with your machine. In such cases I run a few
tests, hoping that one of them might turn up something. Here are a few
thoughts:
- Direct the mstsc.exe command to some other WinXP Professional machine. If
it works then you know that there is nothing wrong with the remote machine.
- Check the event viewer on the host machine.
- Use msconfig.exe on the host machine to disable every startup task except
your virus scanner.
- Use msconfig.exe on the host machine to disable every service except for
your virus scanner and the Microsoft services.- Hide quoted text -

- Show quoted text -

Hello -

I was actually able to figure out what the problem was. It was the
driver of my ATI video card! I downloaded the latest version of it
and now everything seems to be working correctly ...

Thanks a lot for your help!
Joe
 
P

Pegasus \(MVP\)

Hello -

I was actually able to figure out what the problem was. It was the
driver of my ATI video card! I downloaded the latest version of it
and now everything seems to be working correctly ...

Thanks a lot for your help!
Joe

=============

Thanks for the feedback. I wouldn't have guessed something like this but it
makes sense that an incompatible driver can interfere with a Remote Desktop
session.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top