Re: Connection problem
- From: MattShell <MattShell@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 12 Mar 2007 09:41:05 -0700
I have noticed the difference myselft between 6.0 and 5.2. Currently we have
a user who is using 6.0 as an experiment and he could not connect. Turns out
the box was checked in the TS client, not to connect to the TS server without
using the higher encryption, which of course the TS server does not so all of
the 5.2 will work.
Open your TS client and go to Advanced -> Always connect even if
authentication fails.
We need our computers to allow anyone to log on with any computer. So we
cannot authenticate them at the machine, we have to do this at the server log
on screen.
Matt
"Vera Noest [MVP]" wrote:
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?
- References:
- Re: Connection problem
- From: Vera Noest [MVP]
- Re: Connection problem
- Prev by Date: RE: RDP to multiple Servers
- Next by Date: RE: logon error: error occured while an inital user program was st
- Previous by thread: Re: Connection problem
- Next by thread: Periodic RDP connection refusal by Win2003
- Index(es):
Relevant Pages
|
