RDC to a Win2k server on NT4 domain

[Pete]

We have a Win2K member server on an NT4 domain with
administrative terminal services installed.

Adding the Win2K server to the NT4 domain works fine and
logging on for the 1st time works without a hitch and the
new profile is created.

Any subsequent connections to the domain profile on the
server be it via RDC or at the console results in either
the terminal session being disconnected or the server
rebooting if done at the console.

What incompatibilites between the two would cause the
Win2k server to reboot. Apparently this is occuring
during the authentication process to the domain but I'm
unable to determine how to resolve this issue.

Our only means around the matter is to log on to the local
profile.

 

[Pete]

more info..

Event ID 3097

The application, winlogon.exe, generated an application
error The error occurred on 05/12/2004 @ 13:27:44.428 The
exception generated was c0000005 at address 68A850E1
(RegSAMUserConfig)

 

[Pete]

Event ID 4097...not 3097

The server is recently patched and has no known viruses,
as well.

 

[Vera Noest [MVP]]

What ServicePack are you running? This problem is supposed to be
fixed in SP3:

311804 - Computer Hangs When You Log On to a Terminal Services
Session (client) or STOP error C000021A at console
http://support.microsoft.com/?kbid=311804

 

[Pete]

SP4.

I'm thinking I should've posted this elsewhere since at
the console the server simply reboots when trying to
authenticate to the NT4 domain. I posted it here mostly
because I try terminaling to the server and encounter the
disconnect which is much more desirable than logging in at
the console and having the server reboot. The workaround
is to simply log on to the local profile which bypasses
the domain authentication.

Thank you for the reply, though.

-Pete

 

[Greg Lirette [MS]]

I'm the author of Q311804 and know that your current issue is not related
to it. The reason you are getting disconnected in because winlogon.exe is
terminating. In non session 0 instances of a CSRSS.exe or winlogon.exe
crash we don't bugcheck so we the symptom appears to be just a disconnect.
The same failure at the console (session 0) causes a bugcheck in this case
because winlogon.exe no longer exist. It is the STOP 21a bugcheck if
either winlogon,.exe or csrss.exe terminte. In the case of Q311804 it was
CSRSS.


On to the issue at hand.


Have you checked the properties of the user account to see what the
settings are in there?
How long is the username you are logging on with, or are you using the UPN
name perhaps? If so can you see if this happens with a shorter logon name?
It is possible that deleting the values in the user account like homedrive,
profile, logon hours, and so forth may fix this. Basiclly reset all values
to default then set them up again as you want them.

Really it is hard to say without a debug dump file to look at, perhaps you
may consider opening a PSS case on this. I would be interested to see your
dump.

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Greg Lirette [MS]]

The UPN logon question I asked wouldn't make much sense in an NT 4
envirement so please disregard that comment.

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Pete]

Greg,

It was a pleasant surprise to come back to the newsgroup
and find your post. Thank you.

We are only using the 'administrator' account. I will
take your suggestions on clearing out any unnecessary
profile information for that account and re-test.

It's an annoyingly elusive problem as my co-worker who set
up another server in tandem to my Win2K server setup and
the results are not consistent. He is able to terminal to
his server and log onto the domain whereas I am only able
to logon to the local admin account using terminal
services. One thing I have not tried is to use an account
other than the one mentioned.

I'll work with the scenarios you suggested (resetting the
admin account values and using another account) and post
my findings.

Thank you, again.

-Pete

 

[Vera Noest [MVP]]

OK, thanks for explaining this, Greg!

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

(e-mail address removed) ("Greg Lirette [MS]") wrote in

 

[Greg Lirette [MS]]

No problem it is my pleasure. I would really like to see a user.dmp file
of this so I can see it in the debugger. Is one created on your system
when this occurs? Even if you can resolve this by resetting the values, I
would still be interested in seeing this in the debugger if at all
possible.

Thanks,
Greg Lirette

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Pete]

Greg,

I emailed a response to you regarding the user.dmp
information. Let me know if you received it. If not,
I'll repost.

Regards,

Pete Beebe