Remote Desktop is Broken

G

Guest

I have rolled out a bunch of machines running Windows XP Pro. Depending on
the software we install, Remote Desktop will work.

When we run the batch files for one of the departments, it breaks the remote
desktop server. I would like to know if there is a way to install the
software again (the RDP Server) or does anyone have a list of all the files
used by remote desktop so I can compare the versions against a working
machine. I have the feeling one of the setup files is replacing something it
shouldn't.

Thanks.
 
P

Pegasus \(MVP\)

EdNetman said:
I have rolled out a bunch of machines running Windows XP Pro. Depending on
the software we install, Remote Desktop will work.

When we run the batch files for one of the departments, it breaks the remote
desktop server. I would like to know if there is a way to install the
software again (the RDP Server) or does anyone have a list of all the files
used by remote desktop so I can compare the versions against a working
machine. I have the feeling one of the setup files is replacing something it
shouldn't.

Thanks.

The remote desktop host must run the Terminal Server service. Does
it run on the broken machines?

The default port for Remote Desktop is 3389. Can you telnet to this
port? Is is getting blocked by the firewall?
 
G

Guest

Thanks Pegasus,

The Terminal Server service is running and set to Auto. I had to enable
Telnet ( we have it disabled by default) and was not able to connect to that
port. Windows Firewall is disabled via domain policy, so I don't think that
has anything to do with it.

I can telnet into the machine using port 23, and the only IP that is
listening on that port is 0.0.0.0. On my machine (one of the ones that
works) port 3389 is listening on 0.0.0.0 as well as the DHCP address I
aquired.
 
G

Guest

I did a security scan of the machine using LanGuard N.S.S. and saw that port
3389 is open on the remote machine.
 
P

Pegasus \(MVP\)

Here is what you're supposed to see on the Remote Desktop host
when telnetting to it from another machine (port 3389). I ran the
command netstat -an | find "3389"

TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 192.168.44.44:3389 192.168.44.1:2050 ESTABLISHED

Host address: 192.168.44.44
Client address: 192.168.44.1
 
G

Guest

I've got this:

TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING

but since I can't connect, I never get the established part.
 
P

Pegasus \(MVP\)

I can think of two reasons why this would happen:
- A firewall blocks port 3389
- Remote Desktop is no longer enabled.
 
G

Guest

No Firewall. It's disabled.
Remote Desktop is enabled.

Do you have a list of all the files used by remote desktop so I can compare
the versions against a working machine?
 
P

Pegasus \(MVP\)

Sorry, I have no such list. You could try sfc.exe (System File Checker).
 

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

Top