can't logon on Terminal Server W2000

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

It is TS W2000 , App mode
Client WXP SP2 (other network without domen) can't access
Event Log on TS:
- Acces denied logon system
- Unknown name of user or incorrrect password
ID 529
Domen: WS01
Type of logon: NTLmSsp
Pack of testing: NTLM
Workstation: WS01

Domen: WS01 - here must be other name!!! - it is name of workstation
and user name use local name but not user of domain!?

Reinstalling Wendows have not help :(
 
So how is this user trying to connect to the Terminal Server?
When you start the Remote Desktop client on the workstation called
WS01 and go to "Options" - "General", what information is filled in
into the "Domain" field?
Seems to me that the user tries to logon to the Terminal Server
while using a local account on the workstation. That won't work and
produce the EventID that you report.
 
Thanks you your answer!

Field "Domain" is filled correct - domain of TS
and field "user" is filled correct - user of domain of TS
but this information don't use TS for logon :(
 
Weird! I really don't have a clue about what's happening here.
Can you connect to a shared folder on the server from this client,
using your domain username and password?

As an afterthought: have you checked the Terminal Server Connection
Configuration settings on the server? Could it be configured with
an incorrect username for Autoconnect?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
Weird is really :-)
....TS work is correctly - as other workstation from this network logon TS
good...
I can connect to shared folder on the server, I can make command ping with
this server success and etc... but I can't make terminal session with this TS
....
 
I have virtually the same issue. I can not get the Terminal Services Sevice
to start - it just times out. This is very weird indeed as this situation
lives in my IIS machine/Win2000 Server. I had two hard drives in that
machine and right after getting Windows installed, IIS running and configured
and all updates to that point, I copied one hard drive to the other (Ghost
actually). That second drive has been sitting in the machine for nearly 2
years. I set it up, started the machine and there were issues, but mostly
updates and such.

BEFORE getting anywhere near the internet, I installed Symantec Anti-Virus
server and got that set up/updated. I run a hardware firewall so I thought
that I was ready for Windows updates. Did 'em. Re-booted, all seems well.

Tried to start the TS service and that's as far as I've gotten. I had TS
running fine BEFORE this hardware switch. I don't get it!!

Tom Moore
 
Back
Top