Here's one that has me scratching my head. One of the clients on the local
LAN can't connect to one of our terminal servers. he can connect to any
other TS in the domain, but not a specific one.
There are packets being passed between the two machines, but the server
must reject something (I'm not all that skilled in reading the packets from
Network Monitor) becuase after a dozen packets, it just fails, and he gets
the usual "Can't connect... three things" error box.
He's running Win2K Pro with the latest RDP client. The other similarly
configured machines on the network have no trouble logging on to that TS.
I've reinstalled the client a few times, and it doesn't seem to do any
good.
Anywhere else I should look?
Vera Noest [MVP] - 29 Mar 2005 22:39 GMT
Anything in the EventLog on the TS when this client fails to
connect?
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
"J. Knapp" <jknapp@nospam.nospam> wrote on 29 mar 2005 in
microsoft.public.win2000.termserv.clients:
> Here's one that has me scratching my head. One of the clients
> on the local LAN can't connect to one of our terminal servers.
[quoted text clipped - 15 lines]
>
> Anywhere else I should look?
J. Knapp - 30 Mar 2005 01:21 GMT
> Anything in the EventLog on the TS when this client fails to
> connect?
Nope. :-(
... which just makes it more mysterious...
But then today, he tried his shortcut and it worked. Go figure.
anonymous@discussions.microsoft.com - 31 Mar 2005 11:05 GMT
Check the encryption level on the server in terminal server
configuration and his rdp client make sure they are the
same level. also make sure he has access rights to the
server in terminal server config
>-----Original Message-----
>Here's one that has me scratching my head. One of the clients on the local
[quoted text clipped - 15 lines]
>
>.