Re: Connection problem

Could it be that the new laptop has rdp client v. 6.0, while all
other clients still run v. 5.2?

There are a couple of problems with the v. 6.0 client, notably the
way in which you enter the domain and username.

Have a look here:

Vista Remote Desktop Connection Authentication FAQ
http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-
connection-authentication-faq.aspx

Or just uninstall the rdp 6.0 client.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?YXBhcXVldHRl?= <apaquette@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 09 mar 2007 in
microsoft.public.windows.terminal_services:

I have a Windows 2003 Standard Server running Terminal Services
for a small group of users in 2 locations, and it has been
running fine for several months in a non-domain environment
(Microsoft servers are only used for specific
applications/purposes, as our LAN is primarily NetWare 6.5 file
servers (approx 25 scattered all across the country). All the
Microsoft servers have NetWare client software installed on
them.).

One uf the users received a new laptop with Windows XP (her old
laptop was also XP). When I attempt to connect to the Terminal
Services Server via a Remote Connection, I enter the IP address,
I get the NetWare login screen and I can "connect" to the remote
NetWare server in the same subnet as the Terminal Server, but
when it comes to processing the windows login screen for the
Terminal Services server, I get a message stating "A domain
controller could not be found for the specified domain." This
does not happen from any other computer. Even after
re-formatting the hard drive and re-installing XP, it still
thinks that it is attempting to connect to a domain controller.
Nothing in the configuration indicated that it is part of a
domain that I can find.

Any ideas how I can solve this?
.

Relevant Pages

  • Re: Unable to access local workstations from SBS 2003
    ... domain AT the client. ... I did focus on the DNS of the server as a possible issue. ... Relative to the "..computer name is not in Win2K3" I mean that the laptop ... >> I'm able to do just about anything from the laptop or any other workstation ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to access local workstations from SBS 2003
    ... Ensure there is no local HOSTS and LMHOSTS files on the client PCs ... Not sure why you would specify the UNC computer path - browse to the server, find a server share, right click 'Copy' ... Relative to the "..computer name is not in Win2K3" I mean that the laptop computer name, eg DCF9R51, is not part of the "Computers" in Active Directory. ... I'm able to do just about anything from the laptop or any other workstation on the domain: logon, WinExplore, delete but, evidently, not copy/move FROM the server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Offline files (CSC)
    ... I had a VERY similar issue with a Toshiba laptop and Win2000 server. ... We also found that when the client PC goess into ... However the 'You are now working offline' message began ...
    (microsoft.public.windowsxp.general)
  • Re: DHCP
    ... A reconfiguration of the TCP properties on this XP laptop seems to have ... since my Linux server isn't a NetBIOS server. ... This client setting ... > WIndows XPSP1 machine. ...
    (comp.os.linux.networking)
  • RE: Multi Office Novel Migration
    ... FPNW can replace a NetWare server. ... It will not support TCP/IP connections from clients running the ... The Novell Client can be used as long as the workstation ...
    (microsoft.public.windows.server.migration)