Remote desktop cannot connect to XP machine in Small Business Server 2008 domain

Running Small Business Server 2008 domain.  The domain consists of 3 computers running Windows 7 Pro, 1 computer running Windows XP and one ML350 server running Small Business Server 2008.

The problem: Remote desktop from the Windows 7 Pro pc's cannot connect to the XP machine.  Remote desktop from the  ML350 server cannot connect.

Things I have done:
- On the XP machine : right clicked on My Computer, left clicked on the Remote tab, left clicked on “select Remote Users” and added the administrator user and a user name.   Entered these using the domain\Username format .  The application recognized the users I entered (you know, it will uppercase the domain name).

- On the XP machine , when I start a command prompt and type in the command “ping Connect” it displays the correct ip address of the server.
 - On the xp machine, when the command “ping ml350” is entered, it displays the correct ip address of the server.

The XP machine was connected to the Small Business Server 2008 domain using the http://Connect command.  

Now for the strange item:  The name of the XP machine is W24.  When I open a command prompt on any Windows 7  Pro machine and execute the command  “ ping w24” the system does not recognize the w24 computer and will not display any ip address.  If I ping any Windows 7 pc from any pc including the XP machine, the correct ip address appears.

I checked the Windows Firewall settings on the XP machine.  Remote desktop is checked but it is greyed out.  Next to it is a column called “group policy”  In there it is set to Yes

Because this XP machine belongs to a domain, there is no way I know of to turn off the Windows firewall.

What needs to be done to enable the XP machine to be recognized?  

What dns setting needs to be changed so the XP machine is recognized?

What gpo setting needs to change?
donpickAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

NVITCommented:
> ...any Windows 7  Pro machine and execute the command  “ ping w24”
Can you ping the XP stn IP?

On one of the Windows 7 stns, have you tried clearing the dns cache via:
ipconfig /flushdns

Open in new window

0
Lee W, MVPTechnology and Business Process AdvisorCommented:
Try connectingg to the XP machine by IP address.
Try turning off the Windows Firewall
Have you EVER been able to connect to the XP machine via Remote Desktop?
Did you change the port the XP machine listens on for Remote Desktop (registry setting)
Have you checked the event logs on the XP system.
Have you installed new antivirus software that may include a firewall capability?
0
donpickAuthor Commented:
Hello NewVillageIT (NVIT):  The ip address of W24  is 192.168.0.4.  Yes, I can successfully ping this from any Windows 7 Pro pc.

Hello Lee W, MVP:  Yes, using remote desktop, I can successfully connect from a Windows 7 pc to the XP pc by entering the ip address for the XP machine.   Remember, I CANNOT turn off the firewall on the XP machine unless you know which gpo controls this.   This is what i wrote above:  >>I checked the Windows Firewall settings on the XP machine.  Remote desktop is checked but it is greyed out.  Next to it is a column called “group policy”  In there it is set to Yes<<

>>Have you EVER been able to connect to the XP machine via Remote Desktop?<<
 No, not until i used the ip address as you directed.

>>Did you change the port the XP machine listens on for Remote Desktop (registry setting)<<
 No, don't know how to do this.

>>Have you checked the event logs on the XP system<<
Yes, there are several netlogin errors .  They say:
====================
No Domain Controller is available for domain DONHOME due to the following:
The RPC server is unavailable. .
Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
=======================
I don't know why the error says there is no Domain controller.  if there were no domain controller then I would not be able to login on the XP machine to any domain account.  I am able to login to any domain account from the XP machine.  

>>Have you installed new antivirus software that may include a firewall capability? <<
No, the antivirus is installed on the domain server (TrendMicro Worry Free Advanced) It's firewall is turned off.   It would seem to me the SBS 2008 domain knows how to handle the firewalls on all the pc's connected to the domain.  But I'm not an expert so I could be wrong.

My guess is there is something wrong with DNS somewhere. I am not a computer expert so I don't know where to start troubleshooting.
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

NVITCommented:
Did you try ipconfig /flushdns on one of the win7 stations? Then try to rdc to xp?
0
Lee W, MVPTechnology and Business Process AdvisorCommented:
Yes, using remote desktop, I can successfully connect from a Windows 7 pc to the XP pc by entering the ip address for the XP machine.

If we're understanding each other, then what you're saying above is that you CAN connect via RDP when you use the IP address?

If that's the case, then you're having name resolution issues.  Confirm your DNS settings on the workstation.  Your subsequent information on the event logs suggests that the machine is either no longer able to authenticate with the domain or your DNS settings EITHER on the server or the workstation (or both) are incorrect.

To be clear, the ONLY DNS server your workstations should know about is the DC.  And the DC's network settings should only point to itself for DNS - NO ISP DNS SERVERS AT ALL!  You could be using forwarders on the SBS server's DNS server, but NOT in the network connection properties.  

I would say verify your DNS settings (post the results of IPCONFIG /ALL if you're not sure) and then remove and re-add the workstation to the domain (including deleting the computer from the server's list of workstations).  Workstations should dynamically register their names with the server when they are installed properly and if it is done properly, you shouldn't have a problem connecting.
0
donpickAuthor Commented:
I have attached screen captures of the ipconfig from the XP machine and a Windows 7 Pro machine.
How do they look to you?
ipconfig-from-Windows-7-pc.pdf
xpipconfig.doc
0
Lee W, MVPTechnology and Business Process AdvisorCommented:
DNS looks ok on the workstations... what's it look like on the server?  Have you reviewed your event logs on the servers and workstations for any errors or exclamations?  Are those IPs the same that respond when you try to ping by name?  Can you ping by name?  can you ping by IP?  It's possible you once set a hosts file entry to override DNS on the Win7 system - if you can get there by ip and not by name.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
donpickAuthor Commented:
I checked the hosts files and nothing there.  I cannot successfully ping the XP machine using
  ping w24
>>what's it look like on the server? <<
  I assume by this you mean :  will ping w24 work on the server?  Answer is no.

>>Have you reviewed your event logs on the servers and workstations for any errors or exclamations?<<
 There are lots of entries in the system event log.  What errors would be specific for this problem?  Remember, I am not a Windows expert. What errors would you be looking for?
0
Lee W, MVPTechnology and Business Process AdvisorCommented:
When reviewing the event logs, you're looking for errors and warnings.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.