Session Directory and TS issue - Please help

  • Thread starter Thread starter Jeff
  • Start date Start date
J

Jeff

Guest
I have a NLB terminal farm of only 2 servers. I added a third server and it
shows as healthy in nlbmgr. All security is correct and it is taking
sessions correctly as it should.

Issue is that after adding the third node users are sporadically being
kicked off. Another issue is that the farm alias name will sometimes not
respond even though it can be pinged (farm name). No errors on any nodes,
which leads me to believe it is somehow related to the session directory
since it doesn't seem to ever "reach" the dedicated NIC on any node, thus no
errors in events for the terminal session. Session Directory can handle 3
nodes can't it? All are server 2003 Enterprise, same apps, sp's, printers,
all are identical in everyway. No errors on session directory server either.
Any ideas? It only started happening after adding third node. All servers
are dual NIC's. LAN and TSF.
 
RE: Session Directory and TS issue - Please help

Also, we are only using 56 licenses out of our 250 licenses. So licenses are
not an issue on this particular farm.

"Jeff" wrote:

> I have a NLB terminal farm of only 2 servers. I added a third server and it
> shows as healthy in nlbmgr. All security is correct and it is taking
> sessions correctly as it should.
>
> Issue is that after adding the third node users are sporadically being
> kicked off. Another issue is that the farm alias name will sometimes not
> respond even though it can be pinged (farm name). No errors on any nodes,
> which leads me to believe it is somehow related to the session directory
> since it doesn't seem to ever "reach" the dedicated NIC on any node, thus no
> errors in events for the terminal session. Session Directory can handle 3
> nodes can't it? All are server 2003 Enterprise, same apps, sp's, printers,
> all are identical in everyway. No errors on session directory server either.
> Any ideas? It only started happening after adding third node. All servers
> are dual NIC's. LAN and TSF.
 
Re: Session Directory and TS issue - Please help

Jeff,

Are the TS servers you are using dual NIC? If so, can you verify that the
NLB IP address is the same one that is registered with Session Directory?
You can do this by using tsconfig and selecting the proper IP when joining
the SD.

Thanks,
Roman

"Jeff" <Jeff@discussions.microsoft.com> wrote in message
news:20A23174-BDCB-403B-B325-139358AC26D9@microsoft.com...
> Also, we are only using 56 licenses out of our 250 licenses. So licenses
> are
> not an issue on this particular farm.
>
> "Jeff" wrote:
>
>> I have a NLB terminal farm of only 2 servers. I added a third server and
>> it
>> shows as healthy in nlbmgr. All security is correct and it is taking
>> sessions correctly as it should.
>>
>> Issue is that after adding the third node users are sporadically being
>> kicked off. Another issue is that the farm alias name will sometimes not
>> respond even though it can be pinged (farm name). No errors on any
>> nodes,
>> which leads me to believe it is somehow related to the session directory
>> since it doesn't seem to ever "reach" the dedicated NIC on any node, thus
>> no
>> errors in events for the terminal session. Session Directory can handle
>> 3
>> nodes can't it? All are server 2003 Enterprise, same apps, sp's,
>> printers,
>> all are identical in everyway. No errors on session directory server
>> either.
>> Any ideas? It only started happening after adding third node. All
>> servers
>> are dual NIC's. LAN and TSF.
 
Re: Session Directory and TS issue - Please help

Yes they are all dual NIC. The Session Directory (farm) NIC does have the
correct IP address. Network Load Balancing settings for the farm NIC also
shows correctly with the farm address, farm name, and farm virtual MAC.

All three servers are also showing correctly with 1. Multicast 2. Single
Affinity

DNS and WINS is also showing correctly for the farm and for all three nodes.

"Roman Porter [MSFT]" wrote:

> Jeff,
>
> Are the TS servers you are using dual NIC? If so, can you verify that the
> NLB IP address is the same one that is registered with Session Directory?
> You can do this by using tsconfig and selecting the proper IP when joining
> the SD.
>
> Thanks,
> Roman
>
> "Jeff" <Jeff@discussions.microsoft.com> wrote in message
> news:20A23174-BDCB-403B-B325-139358AC26D9@microsoft.com...
> > Also, we are only using 56 licenses out of our 250 licenses. So licenses
> > are
> > not an issue on this particular farm.
> >
> > "Jeff" wrote:
> >
> >> I have a NLB terminal farm of only 2 servers. I added a third server and
> >> it
> >> shows as healthy in nlbmgr. All security is correct and it is taking
> >> sessions correctly as it should.
> >>
> >> Issue is that after adding the third node users are sporadically being
> >> kicked off. Another issue is that the farm alias name will sometimes not
> >> respond even though it can be pinged (farm name). No errors on any
> >> nodes,
> >> which leads me to believe it is somehow related to the session directory
> >> since it doesn't seem to ever "reach" the dedicated NIC on any node, thus
> >> no
> >> errors in events for the terminal session. Session Directory can handle
> >> 3
> >> nodes can't it? All are server 2003 Enterprise, same apps, sp's,
> >> printers,
> >> all are identical in everyway. No errors on session directory server
> >> either.
> >> Any ideas? It only started happening after adding third node. All
> >> servers
> >> are dual NIC's. LAN and TSF.
>
>
 
Re: Session Directory and TS issue - Please help

Oh yes forgot to say, each nodes configuration is redirecting to the correct
dedicated NIC (non-farm NIC).

"Roman Porter [MSFT]" wrote:

> Jeff,
>
> Are the TS servers you are using dual NIC? If so, can you verify that the
> NLB IP address is the same one that is registered with Session Directory?
> You can do this by using tsconfig and selecting the proper IP when joining
> the SD.
>
> Thanks,
> Roman
>
> "Jeff" <Jeff@discussions.microsoft.com> wrote in message
> news:20A23174-BDCB-403B-B325-139358AC26D9@microsoft.com...
> > Also, we are only using 56 licenses out of our 250 licenses. So licenses
> > are
> > not an issue on this particular farm.
> >
> > "Jeff" wrote:
> >
> >> I have a NLB terminal farm of only 2 servers. I added a third server and
> >> it
> >> shows as healthy in nlbmgr. All security is correct and it is taking
> >> sessions correctly as it should.
> >>
> >> Issue is that after adding the third node users are sporadically being
> >> kicked off. Another issue is that the farm alias name will sometimes not
> >> respond even though it can be pinged (farm name). No errors on any
> >> nodes,
> >> which leads me to believe it is somehow related to the session directory
> >> since it doesn't seem to ever "reach" the dedicated NIC on any node, thus
> >> no
> >> errors in events for the terminal session. Session Directory can handle
> >> 3
> >> nodes can't it? All are server 2003 Enterprise, same apps, sp's,
> >> printers,
> >> all are identical in everyway. No errors on session directory server
> >> either.
> >> Any ideas? It only started happening after adding third node. All
> >> servers
> >> are dual NIC's. LAN and TSF.
>
>
 
Re: Session Directory and TS issue - Please help

Found problem with this. Microsoft documentation was vague on a required
item on this. Found problem.

"Jeff" wrote:

> Oh yes forgot to say, each nodes configuration is redirecting to the correct
> dedicated NIC (non-farm NIC).
>
> "Roman Porter [MSFT]" wrote:
>
> > Jeff,
> >
> > Are the TS servers you are using dual NIC? If so, can you verify that the
> > NLB IP address is the same one that is registered with Session Directory?
> > You can do this by using tsconfig and selecting the proper IP when joining
> > the SD.
> >
> > Thanks,
> > Roman
> >
> > "Jeff" <Jeff@discussions.microsoft.com> wrote in message
> > news:20A23174-BDCB-403B-B325-139358AC26D9@microsoft.com...
> > > Also, we are only using 56 licenses out of our 250 licenses. So licenses
> > > are
> > > not an issue on this particular farm.
> > >
> > > "Jeff" wrote:
> > >
> > >> I have a NLB terminal farm of only 2 servers. I added a third server and
> > >> it
> > >> shows as healthy in nlbmgr. All security is correct and it is taking
> > >> sessions correctly as it should.
> > >>
> > >> Issue is that after adding the third node users are sporadically being
> > >> kicked off. Another issue is that the farm alias name will sometimes not
> > >> respond even though it can be pinged (farm name). No errors on any
> > >> nodes,
> > >> which leads me to believe it is somehow related to the session directory
> > >> since it doesn't seem to ever "reach" the dedicated NIC on any node, thus
> > >> no
> > >> errors in events for the terminal session. Session Directory can handle
> > >> 3
> > >> nodes can't it? All are server 2003 Enterprise, same apps, sp's,
> > >> printers,
> > >> all are identical in everyway. No errors on session directory server
> > >> either.
> > >> Any ideas? It only started happening after adding third node. All
> > >> servers
> > >> are dual NIC's. LAN and TSF.
> >
> >
 
Back
Top