Re: Getting Terminal Services to work



I know you said workgroup but the problem sounds like an Active Directory problem. Are you using Active Directory? If you are you have a DNS problem. In an AD domain all of the workstations need to be using an AD DNS server and no other DNS servers. It sounds like you are using your ISP DNS servers or your router. This will allow XP to sort of work with Active Directory but Vista will fail miserably. If you have an AD domain please post the results of IPCONFIG /all from a domain controller and a workstation.

If you're not using AD can you describe the network in a little more detail? What supplies DHCP services? What OS are the Terminal Servers running? Do you have a WINS server? Do you have a DNS server?

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/
http://vistahelpca.blogspot.com/


"chas" <no@xxxxxxxxxxxxxxxxx> wrote in message news:PJydnSaXmNKaGXvVnZ2dnUVZ_s_inZ2d@xxxxxxxxxxxxxxxx
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: GPO problems
    ... It was the ISA 2004 firewall client. ... DNS settings and network properties on the server and client computers. ... > Service of SBS is configured to be the DNS server on the problematic ...
    (microsoft.public.windows.server.sbs)
  • Re: Home to Pro upgrade issues with AD domain
    ... >> computers that when purchased were running XP home. ... >This usually indicates a DNS misconfiguration problem. ... > They should NOT be pointing an an ISP's DNS server. ... and 'Root Hints' ...
    (microsoft.public.windowsxp.network_web)
  • RE: DNS and 2k3 to 2k3 migration
    ... "The problems that I see so far DHCP server on old domain as most users are ... I manually fix this by setting my DNS to new domain This would cause ... the DNS Server IP address obtained from DHCP Server is pointed to ... you couldn't initial VPN connection from computers ...
    (microsoft.public.windows.server.migration)
  • Re: AD, DHCP or maybe DNS problem?
    ... gateway machine can you get to the internet? ... Does dns on the clients point ... Does the AD DNS server forward DNS requests it ... I have a 2003 Server Running as DHCP and DNS, I have 3 cleint computers. ...
    (microsoft.public.windows.server.active_directory)
  • VISTA DNS ISSUES
    ... I am having issues with some faculty's personal Vista laptops not ... being able to surf the internet. ... We are a 2003 Domain running internal DHCP and DNS (which forwards to ... manually set the DNS server to our ISP's DNS (which we use as ...
    (microsoft.public.windows.server.general)