Re: IISRESET needed for clients to reestablish TS-connection

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



In the meantime i have also fixed the Network Policy Event error.

I have added my TS to the group RAS & IAS Servers. Now i don't have the
problem anymore that NPS can't find a DC.

I hope this might have been the login failures on our TS through TS Gateway.
I'll keep you updated in case the problem persist.

Greetz

"deconinckg" wrote:

Dear,

Like i said it was with remote appz. And with TS i meant to connect with RDP
if we have the TS Gateway filled in. TS itself works.

The Client doesn't really see an error just that he cannot login. It doesn't
say his username or password might be incorrect. It just reopens the login
screen for retyping his username and password.

Only thing i see then on the terminal server is the following:

An account was logged off.

Subject:
Security ID: DOMAIN\user
Account Name: user
Account Domain: DOMAIN
Logon ID: 0xa1e8d4a

Logon Type: 3

This event is generated when a logon session is destroyed. It may be
positively correlated with a logon event using the Logon ID value. Logon IDs
are only unique between reboots on the same computer.

so he logs the user off directly after he hit enter to login on remote appz
or through TS Web Access

"Rob Leitman [MSFT]" wrote:


"deconinckg" <deconinckg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E12F9847-36E4-4BAC-96F6-0B5D7F39EB41@xxxxxxxxxxxxxxxx
Dear all,

We have a problem on our TS 2008. For some reason we have to do iisreset
/restart

Our clients are able to reconnect to the Terminal Server after this
action.
Sometimes we have this several times a day, and other times it could be
that
we have no problems at all during the day.

In the Eventlog the only thing that might be worrysome is the following:
Error event: 4402 (NPS = Network Policy Server)
There is no domain controller available for domain <OurDomain>.

Although when i run following command in prompt: nltest
/dsgetdc:<ourdomain>

It does return our DC. We have for now only one DC in our domain. Can
anyone
tell me what might be wrong and why we need to restart IIS so that our
users
can reconnect to TS remote apps and TS itself.

IIS has no relationship with TS. Are you sure the problem isn't with TS Web
Access or TS Gateway?

What error does the client see when this happens?

Rob



.



Relevant Pages

  • Re: Unknown Domain user - domain authentication appears limited
    ... (using cached login). ... Microsoft MVP (Windows Server System: Security) ... > due to the following error: Logon failure: the user has not been granted ...
    (microsoft.public.windows.server.security)
  • Re: Domain Administrator cannot logon to SBS 2003 LOCALLY
    ... login are involved. ... I have concern when you mentioned Veritas Backup. ... It is a SBS Server ... > 'The user has not been granted the requested logon type at this machine'! ...
    (microsoft.public.security)
  • Re: Whos guessing passwords? - source of invalid logins to inetinfo, SBS2003
    ... "Krzysztof Barski" wrote in message ... I am desperately trying to identify from where someone tries to login to our sbs2003 server. ... the first in a chain of these logon attempts also generates eventid 1706 from MSExchangeTransport in application log. ... I haven't seen these for a while, but I think it turned out to be attempts to authenticate with the SMTP server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Mapped drive wont reconnect at logon
    ... login credentials (from the same server). ... to point to the shared file, specified the login name ... and password and ticked the reconnect at logon option. ... Just to be sure, those problem computers are running XP Pro, yes? ...
    (microsoft.public.windowsxp.network_web)
  • Re: How To:Windows Integrated Security and workgroups
    ... I entered the server name and the login prompt just got represented ... furhter 2 times and then logon failure msg! ... Johnny Blair - but also tried WINXP1\Johnny Blair. ...
    (microsoft.public.dotnet.framework.aspnet.security)