Remote Desktop Stopped Working?

[andrewcrystal]

Hi all,

Still consider myself to be well within the realms of newbie here.......

As part of my new I look after our companies small business 2000 server and network.

I was concerned about the server not being up to date, downloaded and ran MBSA and the Shavlik add-on.

I also ran microsoft update and updated all of the windows components and the ISA 2000 ones. Firstly ISA stopped letting users browse the net which I tracked down to an issue on the net and fixed by changing authentification from basic/integrated to just inttegrated.

As far as I am aware the only issue that I currently have now is that remote desktop no longer works. VPN works fine but RD does not work either from within the network or from external. There is no immeadiate error, but eventually the non responding error comes up. I have been searching for an answer this morning and have just found a reference to the MS05-041 update which a user said had caused the same problem and had changed the listener port. I found instructions on how to do this but not sure it is the correct method?

I am also more wary of applying all of the exchange patches as I know very little about the workings of exchange if they cause any problems.

Any advice would be much appreciated.

 

[Hondy]

a couple of checks:

first check that the option is still enabled on the servers you are trying to reach ("remote" tab in System Props)

Check if port 3389 is listening locally(on the server do start>cmd>telnet 127.0.0.1 3389)

if not then its not running else running on a different port. If it is running then perhaps a firewall is blocking access to this port - or perhaps the interface is filtering that port out?

 

[andrewcrystal]

Hi,

Thanks for the advice. I tested as follows:

There wasnt a remote tab in system props like there is in XP (and I guess SBS 2003) so could not check that from there - do you know where I can check it from?

On telnet, I just got a blank cmd screen with a flashing cursor - couldnt type anything in there - rather like the delay in using the rdp client.

I also checked ISA and it is definately allowing traffic through on port 3389.

I also tried changing the port number used via the registry, went to services and tried to stop and restart terminal services but did not have that option despite being the admin. At this point I tried telnet again and jsut got a cannot connect message so it must be doing something on 3389 I guess. I assume restting terminal services needs a restart and I cant do that now so have changed it back to 3389.

Any further tests would be great - not sure how to pursue the telnet testing.