Getting Terminal Services to work

Tech-Archive recommends: Fix windows errors by optimizing your registry

I'm integrating my new Vista 64 bit computer into my home network with XP pro computers on it. All the computers are on a workgroup "Fred". At first my Vista computer could see the XP computers. But it did not see the XP computers as being in the same workgroup. And remote desktop from the Vista to the XP computers did not work by name only by IP address. If I pinged the XP computers from the Vista and the IP addresses were wrong. All the computers are behind my router and are in the 192.168.1.xx subnet. From the XP computers pings were right and the ping looked like this
ctravel [192.168.1.100]
from Vista it looked like this
ctravel.san.rr.com [207.69.131.9]
A helpful fellow here suggested getting rid of the DNS suffix by put a period in the "Append these DNS suffixes". Things got really strange then. Vista stopped seeing the XP computers at all. If it try browsing from Remote Desktop connection then I get the message
The FRED domain/workgroup does not contain any Terminal servers.
The thing that really seems strange to me is this new behavior persists even if I take the period out of the field. If I try pinging CTRAVEL without the period the result looks just the same as it did before. If I ping with the period in I get
C:\Users\charles>ping ctavel
Ping request could not find host ctavel. Please check the name and try again.
And (to me) even stranger is now the XP machines talking to each other give me the
The FRED domain/workgroup does not contain any Terminal servers.
When browsing to Fred from Remote Desktop
Since the period on the Vista machine although they worked fine before.
How do I get a terminal services into FRED again? Should I do it from the Vista machine or the XP machines or all machines? Why did it disappear?
Any ideas welcome thanks ,
Chas
.

Relevant Pages

  • Re: Installing drivers for networked Vista computer
    ...  She's running Vista. ... Configure firewalls on all machines to allow the Local Area Network ... With Windows Firewall, this means allowing File/Printer ... put all computers in the same Workgroup. ...
    (microsoft.public.windowsxp.general)
  • Re: allow clients to ping internet sites from behind ISA 2004
    ... The system policy rules that you mentioned only allow ping from the ISA ... machine itself or from machines that are part of the "Remote management ... computer" or "Enterprise remote management computers". ...
    (microsoft.public.isa.configuration)
  • Re: Did Microsoft break my network?
    ... It seems unlikely that a Windows update impacted all your XP and Vista PCs this way, but you could open System Restore and look at history on each computer without actually running a restore. ... What protocols and firewall settings did you change on the XP machines? ... the XP computers and access files in shared folders on the Vista machines. ... I could go to any of the computers and click on "Network" and see all five ...
    (microsoft.public.windows.vista.networking_sharing)
  • RE: Windows 2000 Pro SP4, XP Home and Vissta Business 32
    ... user accounts and passwords on all machines. ... Passwords/accounts, it gets turned off in vista, but with 2000, you require ... ON (So it can see the other computers) ...
    (microsoft.public.windows.vista.networking_sharing)
  • Authentification mystery - XP Pro SP3 + Vista Ult 64 SP1
    ... Same username and password for admin on all computers ... Private network and sharing turned on on Vista ... Explicit shares on the XP machines with complete rights for everyone ... File sharing runs fine from the XP machines to Vista; ...
    (microsoft.public.windows.vista.networking_sharing)