XP Professional Remote Desktop connectivity issue affecting multiple machines. Connection was ended because of a network error
Posted on 2006-06-09
We have several model Dell systems with several different images at our company. Many of the systems that were previously able to be controlled by other XP Pro systems using RDC, are now receiving the error.
"REMOTE DESKTOP DISCONNECTED
The connection was ended because of a network error. Please try connecting to the remote computer again."
Here are some system details and troubleshooting steps that have already been done without success. ALSO, two of the systems corrected themselves somehow over several weeks(users called and asked what I did to fix it, that's how I know). These systems are usually always on in order to receive updates.
-All referenced systems are XP Professional Sp1a w/o ICF enabled, and have all worked at one time.
-These systems are part of an Active directory, and the problem does not care whether you are on the same LAN segment or not.
-All problematic systems have the ability to control other systems, but cannot be controlled.
-Reimaging the systems with known working images takes about 20 minutes and DOES NOT solve the issue.
-Reimaging the systems with different names that are newly added to the AD doesn't work.
-Reimaging the systems with even newer names on different LAN segments than they were originally on doesn't work.
-3389 is listening
-MSlicensing key was deleted, but never came back even after launching RDC.
-I used a different version of MSTSC.exe that allows you to remote into yourself for testing, and that error comes up "The terminal server has ended the connection"
-Terminal services is running
-looked for the GlobalPolicy folder in system32, but it wasn't there to delete.
-Different profiles were used, without conflicting permissions, all tested accounts were part of the administrator's group as well as remote desktop users group. tests were done with all different combos of this.
-Imported MSLicensing key from a working system, and no go.
-Expensive Microsoft tech support does not know that you cannot RDC into yourself using XP RDC and all subsequent suggestions were of even less help, because they did not take into consideration the above details.
The ONLY system i was given full control of that had all of the reimaging done, was from a user who pimarily uses Macs, and her issue was resolved, and I am not sure what caused this to work and not the reimaging, but by installing XP from scratch, and I tested that RDC worked after being in workgroup, added to domain, and tested after each software installation, and the user is as happy as can be. My issue is that the main PC user's on this campus don't all have the luxury of giving me their PC for this "possible" fix to be applied, and I don't have the time if it turns out that the majority of the 1,500+ users here run into this issue, especially since we use the images on new systems and they work fine. The one thing I am thinking of that may make this an AD issue or some sort of DHCP/DNS/WINS cache thing, is that when I rebuilt the system from scratch, it had not been on the network for about 4 hours versus being reloaded and popped back on within 20 minutes, and maybe something kept the MAC address and corresponding information. All I know is that the other wonderful departments (server and networking) won't touch this because they are lazy and/or really think this is a desktop issue.
Thanks in advance for ANY additional input on this. this is my first post and the impetus for joining you guys here, I hope to return the favor one day!