TS 2003 at SBS 2003 DC

[Oliver Richter]

Hi, (in particular at MCP Vera)

I has the following config:
1 x SBS of 2003 servers Std. (DNS, dhcp, AD, DC, Exchange)
1 x W2003 TS (now member in DC of the SBS 2003)
(reference: The TS was before member in a normal workgroup - all
works OK, since I changes into the SBS 2003 Domain it srikes)

The problem is:
I would like (also remotely) login to the TS.
There the following happens: (with "local" I mean TS direct at the
console)
1. Administrator can login itself locally and remotely (via RDP) on
TS
2. Every other users (domain user) can login itself locally on TS but
not however remotely (via RDP).

With remote access comes the Event-ID 1219 SOURCE: winlogon - in the
TS Eventlog. Now I have already checked event-id.net and MS-KB to
this event-ID 1219. I also read the discussion mails from Vera in this
group (in february 2004). However everything does not help.
The normal users are SBS remote one of operator, which I registered
specially again locally at the TS into the group of Remotedesktopuser.
I set the parameter "enable login to terminalserver" for this users
(group policy).
I gave the user fully right (admins-rights) on TS local drives (drive
C root and subdirs) - for testing - no change. The normal users have
also full rights to the RDP protocol (in terminalserviceconfig).
I checked (changed) also the follwing: The domain user use local
profiles on TS (not SBS 2003 server based) and no indiviual local
paths for TS servies are configured - no change

EVENT-ID Net says it could be an DNS problem - mhhh - but why the
administrator can loging via RDP? Who can I test, that the DNS server
an SBS 2003 DC works good by login?

I do sit now already since two days and become this thing are not
baked.

Seems somehow which simple to be - however with me it blocks.

Make me happy about each assistance.
Thanx Oliver Richter

 

[Guest]

In 1/2 day you could have rebuilt the server and restored data. There must be a point where you quit trying to fix your problem and resolve it another way, i.e. clean install as a member server, install terminal server, install programs, restore any data..

http://www.workthin.com/tshta.ht

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Oliver Richter wrote: ----

Hi, (in particular at MCP Vera

I has the following config
1 x SBS of 2003 servers Std. (DNS, dhcp, AD, DC, Exchange
1 x W2003 TS (now member in DC of the SBS 2003
(reference: The TS was before member in a normal workgroup - al
works OK, since I changes into the SBS 2003 Domain it srikes

The problem is
I would like (also remotely) login to the TS
There the following happens: (with "local" I mean TS direct at th
console
1. Administrator can login itself locally and remotely (via RDP) o
T
2. Every other users (domain user) can login itself locally on TS bu
not however remotely (via RDP)

With remote access comes the Event-ID 1219 SOURCE: winlogon - in th
TS Eventlog. Now I have already checked event-id.net and MS-KB t
this event-ID 1219. I also read the discussion mails from Vera in thi
group (in february 2004). However everything does not help
The normal users are SBS remote one of operator, which I registere
specially again locally at the TS into the group of Remotedesktopuser
I set the parameter "enable login to terminalserver" for this user
(group policy)
I gave the user fully right (admins-rights) on TS local drives (driv
C root and subdirs) - for testing - no change. The normal users hav
also full rights to the RDP protocol (in terminalserviceconfig)
I checked (changed) also the follwing: The domain user use loca
profiles on TS (not SBS 2003 server based) and no indiviual loca
paths for TS servies are configured - no chang

EVENT-ID Net says it could be an DNS problem - mhhh - but why th
administrator can loging via RDP? Who can I test, that the DNS serve
an SBS 2003 DC works good by login

I do sit now already since two days and become this thing are no
baked

Seems somehow which simple to be - however with me it blocks

Make me happy about each assistance.
Thanx Oliver Richte

 

[Vera Noest [MVP]]

While I agree with Patrick that a fresh install is probably the
fastest way to solve the problem, you could, as a last attempt to
solve it without re-installing, download FileMon and RegMon from
http://www.sysinternals.com/. Run them as administrator and start
a TS session as a normal user.

FileMon and RegMon will show you all "access denied" errors
that occur, so that you can give your users the necessary
permissions on a file-to file or Registry subkey basis.
Maybe this will show you where the problem lies, since it is
permission-related.

 

[Oliver Richter]

Thanx to all.

OK - First I will try the sysinteral tools (i hope that the logs
becomes not so big). But I find the Patrick way is better - work
time-effectively.

MFG Oliver Richter
http://www.alpha-soft.de