asked on

Two computers in an AD network are refusing all connections

I have a client with an small AD infrastructure. The previous IT person made amess of things. In any event, two of their computers are refusing to allow connections even thought file & printer sharing is allowed in the firewall rules and logged on as the local administrator.

The computers can connect to all over shares and computers but nothing is allowed as a connection to these two machines.

I have tried everything I could think of to fix this issue. Removed and added the computers from the domain etc.

Michael Worsham

Could possibly be an issue with the Distributed File Systems (DFS) Client functionality...

Even though the hotfix/patch is geared to RDP, it does affect other system environmentals as well:

You receive a "Remote computer has ended the connection" error message when you use the remote desktop connection tool on a Windows XP SP2-based computer
http://support.microsoft.com/kb/898713

Irwin W.

ASKER

The machines are all patched to SP3 and I don't see this registry entry under MUP as described in the article.

Well, since I backed up the registry, I am going to enter and enable it an try it out..

Any other thoughts?

Joseph Daly

Just for the heck of it have you tried stopping and disabling the windows firewall service?

Any funny group policies being applied to these computers?

ASKER CERTIFIED SOLUTION

Michael Worsham

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Joseph Daly

Good call with the winsock fix. Try this if you dont want to go trough all the ms steps.

winsock xp fix
http://www.snapfiles.com/get/winsockxpfix.html

Irwin W.

ASKER

Thought o this but ruled it out due to all the other issues like no local admin passwords. i had started scanner for sasser and other nasties ;)