when my lan was running XP Pro/Vista Business O/S's, I had Remote Destop Connections set up correctly with all systems able to rdc into each other.

Just came across a problem & not getting any sense out of the win 7 manual/help files.

D1 can rdc into all systems with all the others able to rdc into each other, WITH 1 exception....they cannot rdc into D1, my main workstation. If router problem, none should be able to rdc.....if D1 problem, it shouldn't be able to rdc into the others.....

Spent last 4 hrs reading, testing with no joy. Any help or pointers on what could be wrong will be greatly appreciated......

HEY THERE SIRIUS B
WELL I CAN'T HELP YOU OUT WITH THAT PROBLEM. IT SOUNDS LIKE REAL PAIN.

I JUST SWITCHED OVER ALL MY XP BOXES OVER TO WIN 7 AND NO PROBLEMS SO FAR.
WIN 7 IS A WHOLE LOT BETTER THAN ANYTHING THEY HAVE HAD SO FAR. ALTHOUGH STILL VERY OVERPRICED AND OVERSIZED IT SHOWS THAT MICROSHIT IS STARTING TO GET IT ALL TOGETHER. MAYBE IT WAS GATES STEPPIN BACK THAT HELPED IT EVOLVE BETTER. IT REMINDS ME MORE OF UBUNTU 9.10 THAN ANYTHING ELSE BUT EVERYTHING WORKS FASTER WITH A FRESH INSTALL.
I TRIED WIN 7 WHEN IT WAS RELEASED UNDER DEVELOPMENT AND IT LOOKED BETTER THAN VISTA BUT STILL NOT WHAT I LIKED, BUT IT IS NOW PRETTY SLICK.
SO FAR SO GOOD.

yeah, this one is gonna be a real devil to resolve. Used RDC on all rigs to access each other, again, no problems except no rdc to d1, yet d1 can rdc into the rigs that can't access it. Really weird. Still waiting on Microsoft to get back to me on this one.

Atm the only other solution is to relocate d1 to workarea, but would prefer to leave it where it as.

Have you enabled remote connections to the box in the remote tab of systems properties?

Yep, all settings enabled. Got issue resolved. A Microsoft MVP came up with the answer... Run.... cmd /k netstat -a for a list of all ports open. 3389 was open & listening (needed for remote access) so he suggested checking firewall.

On doing so, found Remote Desktop disabled in the firewall. Now, got to find out what disabled it. Ran AV & anti-malware & everything came up clean.......puzzling......

This problem reared it's ugly head again just after Xmas. Haven't really bothered with it since as been busy. Several weeks ago, ran a test on SBS 2011 Essentials. It looked good, so put it into production. Bad move - somehow it corrupted all client machines.

It got so bad, that I eventually did a clean install on all clients & reverted back to WHS connections.

What I find really weird this time around is that I can access all clients via Win Explorer after it asks for user name & password, but whenever I try RDC itself, I keep getting this.....



Using each client seperately, I tried accessing WHS via the net & I am able to rdp into each client via WHS's Remote Access which makes a mockery of the 3 failure types stated as it confirms that Remote Access is configured correctly & all machines are on & connected.

I'm wondering if Win 7's Homegroup could be interfering........