MSTerminalServices.org Forums

Forums Home | FAQ | Search | Profile | Private Messages | Log in/Register/Password

TS, NLB and Session Directory problem

Page 1 of 1
Next:  General Discussions: Is it possible to limit rdp/ts connection to Console only ..  
Author Message
Jeff Allred

External


Since: May 06, 2005
Posts: 2



(Msg. 1) Posted: Fri May 06, 2005 3:20 pm
Post subject: TS, NLB and Session Directory problem
Archived from groups: microsoft>public>windows>terminal_services (more info?)
I have a two node NLB/TS cluster and I am receiving the following error
when trying to add the two nodes to the "Session Directory Computers"
group on the machine I have designated as the Session Directory Server
(same domain as both NLB/TS nodes.)

Information Returned from the object picker for object "node1" was
incomplete. The object will not be processed.

FWIW, I am also receiving the following event in the System log on the
Session Directory Server:

Event ID 1020 Source: TermServSessDir

The "Session Directory Computers" group is empty, you must add the
computer accounts of Terminal Servers into this group for the Session
Directory Service to work properly.

I am also receiving the following on each node of TS cluster.

Event ID: 1007 Source: TermServJet

The server failed to join Session Directory because
RpcMgmtInqServerPrincName failed with error code 0x721.


Any insight provided will be greatly appreciated.

Thanks,

Jeff Allred
Back to top
Send e-mail Login to vote
Vera Noest [MVP]

External


Since: Sep 07, 2003
Posts: 9443



(Msg. 2) Posted: Fri May 06, 2005 4:21 pm
Post subject: Re: TS, NLB and Session Directory problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Hexadecimal error code 0x721 from Event 1007 equals to decimal
error code 1825, RPC_S_SEC_PKG_ERROR, which translates to:
"A security package specific error occurred"

Any non-standard security configuration in your domain which could
cause this?

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

Jeff Allred <6stringcowboy.RemoveThis@bellsouth.net> wrote on 06 maj 2005 in
microsoft.public.windows.terminal_services:

> I have a two node NLB/TS cluster and I am receiving the
> following error when trying to add the two nodes to the "Session
> Directory Computers" group on the machine I have designated as
> the Session Directory Server (same domain as both NLB/TS nodes.)
>
> Information Returned from the object picker for object "node1"
> was incomplete. The object will not be processed.
>
> FWIW, I am also receiving the following event in the System log
> on the Session Directory Server:
>
> Event ID 1020 Source: TermServSessDir
>
> The "Session Directory Computers" group is empty, you must add
> the computer accounts of Terminal Servers into this group for
> the Session Directory Service to work properly.
>
> I am also receiving the following on each node of TS cluster.
>
> Event ID: 1007 Source: TermServJet
>
> The server failed to join Session Directory because
> RpcMgmtInqServerPrincName failed with error code 0x721.
>
>
> Any insight provided will be greatly appreciated.
>
> Thanks,
>
> Jeff Allred
Back to top
Send e-mail Login to vote
Jeff Allred

External


Since: May 06, 2005
Posts: 2



(Msg. 3) Posted: Fri May 06, 2005 7:36 pm
Post subject: Re: TS, NLB and Session Directory problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
No, but I've tried the Session Directory Server on a couple other boxes
in the domain with the exact same results.

Could the security configuration on the TS nodes cause this? I should
have also mentioned that this domain is still NT 4, could this be the
problem? (I didn't see anything that would lead me to believe that your
domain had to be AD for this to function properly?

Thank you,

Jeff Allred

Vera Noest [MVP] wrote:
> Hexadecimal error code 0x721 from Event 1007 equals to decimal
> error code 1825, RPC_S_SEC_PKG_ERROR, which translates to:
> "A security package specific error occurred"
>
> Any non-standard security configuration in your domain which could
> cause this?
>
> --
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>
> Jeff Allred <6stringcowboy.TakeThisOut@bellsouth.net> wrote on 06 maj 2005 in
> microsoft.public.windows.terminal_services:
>
>
>>I have a two node NLB/TS cluster and I am receiving the
>>following error when trying to add the two nodes to the "Session
>>Directory Computers" group on the machine I have designated as
>>the Session Directory Server (same domain as both NLB/TS nodes.)
>>
>>Information Returned from the object picker for object "node1"
>>was incomplete. The object will not be processed.
>>
>>FWIW, I am also receiving the following event in the System log
>>on the Session Directory Server:
>>
>>Event ID 1020 Source: TermServSessDir
>>
>>The "Session Directory Computers" group is empty, you must add
>>the computer accounts of Terminal Servers into this group for
>>the Session Directory Service to work properly.
>>
>>I am also receiving the following on each node of TS cluster.
>>
>>Event ID: 1007 Source: TermServJet
>>
>>The server failed to join Session Directory because
>>RpcMgmtInqServerPrincName failed with error code 0x721.
>>
>>
>>Any insight provided will be greatly appreciated.
>>
>>Thanks,
>>
>>Jeff Allred
>
>
Back to top
Send e-mail Login to vote
Vera Noest [MVP]

External


Since: Sep 07, 2003
Posts: 9443



(Msg. 4) Posted: Sat May 07, 2005 2:31 pm
Post subject: Re: TS, NLB and Session Directory problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
I'm afraid that NT4 is the problem:

814333 - Session Directory Does Not Work in a Windows NT 4.0 Domain
http://support.microsoft.com/?kbid=814333

Unfortunately, this is *not* mentioned in the Session Directory
White Paper.

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

Jeff Allred <6stringcowboy RemoveThis @bellsouth.net> wrote on 06 maj 2005 in
microsoft.public.windows.terminal_services:

> No, but I've tried the Session Directory Server on a couple
> other boxes in the domain with the exact same results.
>
> Could the security configuration on the TS nodes cause this? I
> should have also mentioned that this domain is still NT 4, could
> this be the problem? (I didn't see anything that would lead me
> to believe that your domain had to be AD for this to function
> properly?
>
> Thank you,
>
> Jeff Allred
>
> Vera Noest [MVP] wrote:
>> Hexadecimal error code 0x721 from Event 1007 equals to decimal
>> error code 1825, RPC_S_SEC_PKG_ERROR, which translates to:
>> "A security package specific error occurred"
>>
>> Any non-standard security configuration in your domain which
>> could cause this?
>>
>> --
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> http://hem.fyristorg.com/vera/IT
>> --- please respond in newsgroup, NOT by private email ---
>>
>> Jeff Allred <6stringcowboy RemoveThis @bellsouth.net> wrote on 06 maj 2005
>> in microsoft.public.windows.terminal_services:
>>
>>
>>>I have a two node NLB/TS cluster and I am receiving the
>>>following error when trying to add the two nodes to the
>>>"Session Directory Computers" group on the machine I have
>>>designated as the Session Directory Server (same domain as both
>>>NLB/TS nodes.)
>>>
>>>Information Returned from the object picker for object "node1"
>>>was incomplete. The object will not be processed.
>>>
>>>FWIW, I am also receiving the following event in the System log
>>>on the Session Directory Server:
>>>
>>>Event ID 1020 Source: TermServSessDir
>>>
>>>The "Session Directory Computers" group is empty, you must add
>>>the computer accounts of Terminal Servers into this group for
>>>the Session Directory Service to work properly.
>>>
>>>I am also receiving the following on each node of TS cluster.
>>>
>>>Event ID: 1007 Source: TermServJet
>>>
>>>The server failed to join Session Directory because
>>>RpcMgmtInqServerPrincName failed with error code 0x721.
>>>
>>>
>>>Any insight provided will be greatly appreciated.
>>>
>>>Thanks,
>>>
>>>Jeff Allred
>>
Back to top
Send e-mail Login to vote
Display posts from previous:   
    All times are: Eastern Time (US & Canada) (change) Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Looking for more Terminal Services info?

Sign up to the MSTerminalServices.org Monthly Newsletter, written by Terminal Server MVP & Citrix CTP Stefan Vermeulen, containing news, tips, interviews, links of the month and much more. Subscribe today and don't miss a thing!

Become an MSTerminalServices.org member!

Discuss your Terminal Services & Citrix issues with thousands of other SBC experts. Click here to join!

Community Area

Log in | Register