REMOTE CONTROL (W2K3) doesn't work on WXP Pro SP2

[rlebrun1]

Our server has W2K3 on it, and we use Remote Control (Terminal Services Manager) on our local network as a better alternative to Remote Desktop. Everything works OK as long as the working stations have WXP Pro SP1.

But if we update the working stations that have WXP Pro from SP1 to SP2, then the Terminal Services Manager can’t see them anymore. The only thing that happens every time we try to connect to the updated station is that an error message shows up saying: "You could not be authenticated on this server" (referring to the station we are trying to connect to with the Remote Control).

¿What changes do we have to make (we suppose...) on the working stations to be able to use the Remote Control on those stations again?

(All the policies and parameters on the server side were already sat up and work fine, the problem happens when the stations get updated). We were looking for a comment or solution in the Knowledge Base but there wasn't any article specifically related to this situation.

Any idea? We need a solution very badly 'cause we strongly rely on Remote Control for our daily support to the users...

Thanks,

 

[BadBigBen]

From what I have read and gathered, this is a problem due to the SIMPLE FILE SHARING being active...

try deactivating them...

good read on FILESHARING:

http://www.practicallynetworked.com/sharing/xp/filesharing.htm

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[Bobg1]

Sp2 automaticlly starts the firewall.
You will have to either turn it off or
set the proper exceptions.

 

[AcquisitiveOne]

I agree with Bobg1 more than likely this is due to the Firewall being turned on by default. Try turning off the Windows Firewall (Windows ICF) and then attempt to connect to the PC. If it works great than you know what your problem was caused by.

Acquisitive - 1. Characterized by a strong desire to gain and possess. 2. Tending to acquire and retain ideas or information