> Our Windows 2008 Terminal Server suffers from an NLASVC timeout error.
> The event ID is 7011.  What's important is once the error occurs, the
> server must be restarted to resume operation.  The timeout occurs once
> every 8 to 12 hours.  The actual error is below.  The server is
> running all of the latest patches, including SP2.  Can NLASVC be
> disabled?
>
> Log Name:      System
> Source:        Service Control Manager
> Date:          6/10/2009 3:24:11 PM
> Event ID:      7011
> Task Category: None
> Level:         Error
> Keywords:      Classic
> User:          N/A
> Computer:      KAVSAPP01.knopf.local
> Description:
> A timeout (30000 milliseconds) was reached while waiting for a
> transaction
> response from the NlaSvc service.
> Event Xml:
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Service Control Manager"
> Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}" EventSourceName="Service
> Control Manager" />
> <EventID Qualifiers="49152">7011</EventID>
> <Version>0</Version>
> <Level>2</Level>
> <Task>0</Task>
> <Opcode>0</Opcode>
> <Keywords>0x80000000000000</Keywords>
> <TimeCreated SystemTime="2009-06-10T19:24:11.000Z" />
> <EventRecordID>108237</EventRecordID>
> <Correlation />
> <Execution ProcessID="0" ThreadID="0" />
> <Channel>System</Channel>
> <Computer>KAVSAPP01.knopf.local</Computer>
> <Security />
> </System>
> <EventData>
> <Data Name="param1">30000</Data>
> <Data Name="param2">NlaSvc</Data>
> </EventData>
> </Event>

"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66274e38cbb8bf4b74e5e3@msnews.microsoft.com...
> Hello mark,
>
> The Network Location Awareness service which collects and stores network
> configuration information such as IP addresses, Workgroup and/or Domain
> name changes (if your PC is connected to a Windows network), as well as
> Location change information, and which notifies applications when this
> information changes so that they in turn adapt to the computer's
> connectivity changes. So you should not disable that service.
>
> Is that service started and set to automatic? Do you run TrendMicro
> AntiVirus, read about a problem with that AntiVirus software?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Our Windows 2008 Terminal Server suffers from an NLASVC timeout error.
>> The event ID is 7011.  What's important is once the error occurs, the
>> server must be restarted to resume operation.  The timeout occurs once
>> every 8 to 12 hours.  The actual error is below.  The server is
>> running all of the latest patches, including SP2.  Can NLASVC be
>> disabled?
>>
>> Log Name:      System
>> Source:        Service Control Manager
>> Date:          6/10/2009 3:24:11 PM
>> Event ID:      7011
>> Task Category: None
>> Level:         Error
>> Keywords:      Classic
>> User:          N/A
>> Computer:      KAVSAPP01.knopf.local
>> Description:
>> A timeout (30000 milliseconds) was reached while waiting for a
>> transaction
>> response from the NlaSvc service.
>> Event Xml:
>> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>> <System>
>> <Provider Name="Service Control Manager"
>> Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}" EventSourceName="Service
>> Control Manager" />
>> <EventID Qualifiers="49152">7011</EventID>
>> <Version>0</Version>
>> <Level>2</Level>
>> <Task>0</Task>
>> <Opcode>0</Opcode>
>> <Keywords>0x80000000000000</Keywords>
>> <TimeCreated SystemTime="2009-06-10T19:24:11.000Z" />
>> <EventRecordID>108237</EventRecordID>
>> <Correlation />
>> <Execution ProcessID="0" ThreadID="0" />
>> <Channel>System</Channel>
>> <Computer>KAVSAPP01.knopf.local</Computer>
>> <Security />
>> </System>
>> <EventData>
>> <Data Name="param1">30000</Data>
>> <Data Name="param2">NlaSvc</Data>
>> </EventData>
>> </Event>
>
>

> Thanks. For testing purposes, we ended up disabling the NLASVC and NIS
> services. The server runs well without them. The NLASVC errors went
> away, but the "Welcome Screen" hang is still present and the server
> becomes unresponsive and must be rebooted daily.  It has become such a
> problem, that we may have have to buildout a replacement 2003
> environment.
>
> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
> news:ff16fb66274e38cbb8bf4b74e5e3@msnews.microsoft.com...
>
>> Hello mark,
>>
>> The Network Location Awareness service which collects and stores
>> network configuration information such as IP addresses, Workgroup
>> and/or Domain name changes (if your PC is connected to a Windows
>> network), as well as Location change information, and which notifies
>> applications when this information changes so that they in turn adapt
>> to the computer's connectivity changes. So you should not disable
>> that service.
>>
>> Is that service started and set to automatic? Do you run TrendMicro
>> AntiVirus, read about a problem with that AntiVirus software?
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Our Windows 2008 Terminal Server suffers from an NLASVC timeout
>>> error. The event ID is 7011.  What's important is once the error
>>> occurs, the server must be restarted to resume operation.  The
>>> timeout occurs once every 8 to 12 hours.  The actual error is below.
>>> The server is running all of the latest patches, including SP2.  Can
>>> NLASVC be disabled?
>>>
>>> Log Name:      System
>>> Source:        Service Control Manager
>>> Date:          6/10/2009 3:24:11 PM
>>> Event ID:      7011
>>> Task Category: None
>>> Level:         Error
>>> Keywords:      Classic
>>> User:          N/A
>>> Computer:      KAVSAPP01.knopf.local
>>> Description:
>>> A timeout (30000 milliseconds) was reached while waiting for a
>>> transaction
>>> response from the NlaSvc service.
>>> Event Xml:
>>> <Event
>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>> <System>
>>> <Provider Name="Service Control Manager"
>>> Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}"
>>> EventSourceName="Service
>>> Control Manager" />
>>> <EventID Qualifiers="49152">7011</EventID>
>>> <Version>0</Version>
>>> <Level>2</Level>
>>> <Task>0</Task>
>>> <Opcode>0</Opcode>
>>> <Keywords>0x80000000000000</Keywords>
>>> <TimeCreated SystemTime="2009-06-10T19:24:11.000Z" />
>>> <EventRecordID>108237</EventRecordID>
>>> <Correlation />
>>> <Execution ProcessID="0" ThreadID="0" />
>>> <Channel>System</Channel>
>>> <Computer>KAVSAPP01.knopf.local</Computer>
>>> <Security />
>>> </System>
>>> <EventData>
>>> <Data Name="param1">30000</Data>
>>> <Data Name="param2">NlaSvc</Data>
>>> </EventData>
>>> </Event>

"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66278168cbb9b7db8fee9c@msnews.microsoft.com...
> Hello mark,
>
> "Welcome screen hang"? What do you mean with that, slow logons?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Thanks. For testing purposes, we ended up disabling the NLASVC and NIS
>> services. The server runs well without them. The NLASVC errors went
>> away, but the "Welcome Screen" hang is still present and the server
>> becomes unresponsive and must be rebooted daily.  It has become such a
>> problem, that we may have have to buildout a replacement 2003
>> environment.
>>
>> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
>> news:ff16fb66274e38cbb8bf4b74e5e3@msnews.microsoft.com...
>>
>>> Hello mark,
>>>
>>> The Network Location Awareness service which collects and stores
>>> network configuration information such as IP addresses, Workgroup
>>> and/or Domain name changes (if your PC is connected to a Windows
>>> network), as well as Location change information, and which notifies
>>> applications when this information changes so that they in turn adapt
>>> to the computer's connectivity changes. So you should not disable
>>> that service.
>>>
>>> Is that service started and set to automatic? Do you run TrendMicro
>>> AntiVirus, read about a problem with that AntiVirus software?
>>>
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers no rights.
>>> ** Please do NOT email, only reply to Newsgroups
>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>> Our Windows 2008 Terminal Server suffers from an NLASVC timeout
>>>> error. The event ID is 7011.  What's important is once the error
>>>> occurs, the server must be restarted to resume operation.  The
>>>> timeout occurs once every 8 to 12 hours.  The actual error is below.
>>>> The server is running all of the latest patches, including SP2.  Can
>>>> NLASVC be disabled?
>>>>
>>>> Log Name:      System
>>>> Source:        Service Control Manager
>>>> Date:          6/10/2009 3:24:11 PM
>>>> Event ID:      7011
>>>> Task Category: None
>>>> Level:         Error
>>>> Keywords:      Classic
>>>> User:          N/A
>>>> Computer:      KAVSAPP01.knopf.local
>>>> Description:
>>>> A timeout (30000 milliseconds) was reached while waiting for a
>>>> transaction
>>>> response from the NlaSvc service.
>>>> Event Xml:
>>>> <Event
>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>> <System>
>>>> <Provider Name="Service Control Manager"
>>>> Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}"
>>>> EventSourceName="Service
>>>> Control Manager" />
>>>> <EventID Qualifiers="49152">7011</EventID>
>>>> <Version>0</Version>
>>>> <Level>2</Level>
>>>> <Task>0</Task>
>>>> <Opcode>0</Opcode>
>>>> <Keywords>0x80000000000000</Keywords>
>>>> <TimeCreated SystemTime="2009-06-10T19:24:11.000Z" />
>>>> <EventRecordID>108237</EventRecordID>
>>>> <Correlation />
>>>> <Execution ProcessID="0" ThreadID="0" />
>>>> <Channel>System</Channel>
>>>> <Computer>KAVSAPP01.knopf.local</Computer>
>>>> <Security />
>>>> </System>
>>>> <EventData>
>>>> <Data Name="param1">30000</Data>
>>>> <Data Name="param2">NlaSvc</Data>
>>>> </EventData>
>>>> </Event>
>
>

> When the RDP session starts, the user is prompted for credentials.
> Once the credentials are entered and user presses enter (or the
> arrow), the RDP session displays "Welcome" with the rotating circle
> (to the left), but the log on never gets any further.  We've waited
> over 20 minutes and nothing.
>
> Normally, a series of messages are displayed like load profile, etc.
>
> The event log is void of errors.  The console is also hung.  It has
> happened to all users and appears to the connection independent - RDP
> client version, OS version, do not matter.  This happens at least once
> a day, sometimes more.  A hard reboot is required to reactivate the
> server.
>
> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
> news:ff16fb66278168cbb9b7db8fee9c@msnews.microsoft.com...
>
>> Hello mark,
>>
>> "Welcome screen hang"? What do you mean with that, slow logons?
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Thanks. For testing purposes, we ended up disabling the NLASVC and
>>> NIS services. The server runs well without them. The NLASVC errors
>>> went away, but the "Welcome Screen" hang is still present and the
>>> server becomes unresponsive and must be rebooted daily.  It has
>>> become such a problem, that we may have have to buildout a
>>> replacement 2003 environment.
>>>
>>> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
>>> news:ff16fb66274e38cbb8bf4b74e5e3@msnews.microsoft.com...
>>>
>>>> Hello mark,
>>>>
>>>> The Network Location Awareness service which collects and stores
>>>> network configuration information such as IP addresses, Workgroup
>>>> and/or Domain name changes (if your PC is connected to a Windows
>>>> network), as well as Location change information, and which
>>>> notifies applications when this information changes so that they in
>>>> turn adapt to the computer's connectivity changes. So you should
>>>> not disable that service.
>>>>
>>>> Is that service started and set to automatic? Do you run TrendMicro
>>>> AntiVirus, read about a problem with that AntiVirus software?
>>>>
>>>> Best regards
>>>>
>>>> Meinolf Weber
>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>> and
>>>> confers no rights.
>>>> ** Please do NOT email, only reply to Newsgroups
>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>> Our Windows 2008 Terminal Server suffers from an NLASVC timeout
>>>>> error. The event ID is 7011.  What's important is once the error
>>>>> occurs, the server must be restarted to resume operation.  The
>>>>> timeout occurs once every 8 to 12 hours.  The actual error is
>>>>> below. The server is running all of the latest patches, including
>>>>> SP2.  Can NLASVC be disabled?
>>>>>
>>>>> Log Name:      System
>>>>> Source:        Service Control Manager
>>>>> Date:          6/10/2009 3:24:11 PM
>>>>> Event ID:      7011
>>>>> Task Category: None
>>>>> Level:         Error
>>>>> Keywords:      Classic
>>>>> User:          N/A
>>>>> Computer:      KAVSAPP01.knopf.local
>>>>> Description:
>>>>> A timeout (30000 milliseconds) was reached while waiting for a
>>>>> transaction
>>>>> response from the NlaSvc service.
>>>>> Event Xml:
>>>>> <Event
>>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>>> <System>
>>>>> <Provider Name="Service Control Manager"
>>>>> Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}"
>>>>> EventSourceName="Service
>>>>> Control Manager" />
>>>>> <EventID Qualifiers="49152">7011</EventID>
>>>>> <Version>0</Version>
>>>>> <Level>2</Level>
>>>>> <Task>0</Task>
>>>>> <Opcode>0</Opcode>
>>>>> <Keywords>0x80000000000000</Keywords>
>>>>> <TimeCreated SystemTime="2009-06-10T19:24:11.000Z" />
>>>>> <EventRecordID>108237</EventRecordID>
>>>>> <Correlation />
>>>>> <Execution ProcessID="0" ThreadID="0" />
>>>>> <Channel>System</Channel>
>>>>> <Computer>KAVSAPP01.knopf.local</Computer>
>>>>> <Security />
>>>>> </System>
>>>>> <EventData>
>>>>> <Data Name="param1">30000</Data>
>>>>> <Data Name="param2">NlaSvc</Data>
>>>>> </EventData>
>>>>> </Event>

"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb662781c8cbb9b9b8e5a7cc@msnews.microsoft.com...
> Hello mark,
>
> Please post an unedited ipconfig /all from the TS and the DNS/DC.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> When the RDP session starts, the user is prompted for credentials.
>> Once the credentials are entered and user presses enter (or the
>> arrow), the RDP session displays "Welcome" with the rotating circle
>> (to the left), but the log on never gets any further.  We've waited
>> over 20 minutes and nothing.
>>
>> Normally, a series of messages are displayed like load profile, etc.
>>
>> The event log is void of errors.  The console is also hung.  It has
>> happened to all users and appears to the connection independent - RDP
>> client version, OS version, do not matter.  This happens at least once
>> a day, sometimes more.  A hard reboot is required to reactivate the
>> server.
>>
>> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
>> news:ff16fb66278168cbb9b7db8fee9c@msnews.microsoft.com...
>>
>>> Hello mark,
>>>
>>> "Welcome screen hang"? What do you mean with that, slow logons?
>>>
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers no rights.
>>> ** Please do NOT email, only reply to Newsgroups
>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>> Thanks. For testing purposes, we ended up disabling the NLASVC and
>>>> NIS services. The server runs well without them. The NLASVC errors
>>>> went away, but the "Welcome Screen" hang is still present and the
>>>> server becomes unresponsive and must be rebooted daily.  It has
>>>> become such a problem, that we may have have to buildout a
>>>> replacement 2003 environment.
>>>>
>>>> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
>>>> news:ff16fb66274e38cbb8bf4b74e5e3@msnews.microsoft.com...
>>>>
>>>>> Hello mark,
>>>>>
>>>>> The Network Location Awareness service which collects and stores
>>>>> network configuration information such as IP addresses, Workgroup
>>>>> and/or Domain name changes (if your PC is connected to a Windows
>>>>> network), as well as Location change information, and which
>>>>> notifies applications when this information changes so that they in
>>>>> turn adapt to the computer's connectivity changes. So you should
>>>>> not disable that service.
>>>>>
>>>>> Is that service started and set to automatic? Do you run TrendMicro
>>>>> AntiVirus, read about a problem with that AntiVirus software?
>>>>>
>>>>> Best regards
>>>>>
>>>>> Meinolf Weber
>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>>> and
>>>>> confers no rights.
>>>>> ** Please do NOT email, only reply to Newsgroups
>>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>>> Our Windows 2008 Terminal Server suffers from an NLASVC timeout
>>>>>> error. The event ID is 7011.  What's important is once the error
>>>>>> occurs, the server must be restarted to resume operation.  The
>>>>>> timeout occurs once every 8 to 12 hours.  The actual error is
>>>>>> below. The server is running all of the latest patches, including
>>>>>> SP2.  Can NLASVC be disabled?
>>>>>>
>>>>>> Log Name:      System
>>>>>> Source:        Service Control Manager
>>>>>> Date:          6/10/2009 3:24:11 PM
>>>>>> Event ID:      7011
>>>>>> Task Category: None
>>>>>> Level:         Error
>>>>>> Keywords:      Classic
>>>>>> User:          N/A
>>>>>> Computer:      KAVSAPP01.knopf.local
>>>>>> Description:
>>>>>> A timeout (30000 milliseconds) was reached while waiting for a
>>>>>> transaction
>>>>>> response from the NlaSvc service.
>>>>>> Event Xml:
>>>>>> <Event
>>>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>>>> <System>
>>>>>> <Provider Name="Service Control Manager"
>>>>>> Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}"
>>>>>> EventSourceName="Service
>>>>>> Control Manager" />
>>>>>> <EventID Qualifiers="49152">7011</EventID>
>>>>>> <Version>0</Version>
>>>>>> <Level>2</Level>
>>>>>> <Task>0</Task>
>>>>>> <Opcode>0</Opcode>
>>>>>> <Keywords>0x80000000000000</Keywords>
>>>>>> <TimeCreated SystemTime="2009-06-10T19:24:11.000Z" />
>>>>>> <EventRecordID>108237</EventRecordID>
>>>>>> <Correlation />
>>>>>> <Execution ProcessID="0" ThreadID="0" />
>>>>>> <Channel>System</Channel>
>>>>>> <Computer>KAVSAPP01.knopf.local</Computer>
>>>>>> <Security />
>>>>>> </System>
>>>>>> <EventData>
>>>>>> <Data Name="param1">30000</Data>
>>>>>> <Data Name="param2">NlaSvc</Data>
>>>>>> </EventData>
>>>>>> </Event>
>
>

> This is from 1 of the 2 servers.  Both crash, but this server has more
> issues than the other.
>
> Microsoft Windows [Version 6.0.6002]
> Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
> C:\Users\administrator.KNOPF>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : KAVSAPP01
> Primary Dns Suffix  . . . . . . . : knopf.local
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : knopf.local
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix  . : knopf.local
> Description . . . . . . . . . . . : VMware PCI Ethernet Adapter
> Physical Address. . . . . . . . . : 00-50-56-BD-77-4A
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> IPv4 Address. . . . . . . . . . . : 10.100.32.50(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 10.100.32.1
> DNS Servers . . . . . . . . . . . : 10.100.32.20
> 10.100.32.30
> Primary WINS Server . . . . . . . : 10.100.32.20
> Secondary WINS Server . . . . . . : 10.100.32.30
> NetBIOS over Tcpip. . . . . . . . : Enabled
> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
> news:ff16fb662781c8cbb9b9b8e5a7cc@msnews.microsoft.com...
>
>> Hello mark,
>>
>> Please post an unedited ipconfig /all from the TS and the DNS/DC.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> When the RDP session starts, the user is prompted for credentials.
>>> Once the credentials are entered and user presses enter (or the
>>> arrow), the RDP session displays "Welcome" with the rotating circle
>>> (to the left), but the log on never gets any further.  We've waited
>>> over 20 minutes and nothing.
>>>
>>> Normally, a series of messages are displayed like load profile, etc.
>>>
>>> The event log is void of errors.  The console is also hung.  It has
>>> happened to all users and appears to the connection independent -
>>> RDP client version, OS version, do not matter.  This happens at
>>> least once a day, sometimes more.  A hard reboot is required to
>>> reactivate the server.
>>>
>>> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
>>> news:ff16fb66278168cbb9b7db8fee9c@msnews.microsoft.com...
>>>
>>>> Hello mark,
>>>>
>>>> "Welcome screen hang"? What do you mean with that, slow logons?
>>>>
>>>> Best regards
>>>>
>>>> Meinolf Weber
>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>> and
>>>> confers no rights.
>>>> ** Please do NOT email, only reply to Newsgroups
>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>> Thanks. For testing purposes, we ended up disabling the NLASVC and
>>>>> NIS services. The server runs well without them. The NLASVC errors
>>>>> went away, but the "Welcome Screen" hang is still present and the
>>>>> server becomes unresponsive and must be rebooted daily.  It has
>>>>> become such a problem, that we may have have to buildout a
>>>>> replacement 2003 environment.
>>>>>
>>>>> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
>>>>> news:ff16fb66274e38cbb8bf4b74e5e3@msnews.microsoft.com...
>>>>>
>>>>>> Hello mark,
>>>>>>
>>>>>> The Network Location Awareness service which collects and stores
>>>>>> network configuration information such as IP addresses, Workgroup
>>>>>> and/or Domain name changes (if your PC is connected to a Windows
>>>>>> network), as well as Location change information, and which
>>>>>> notifies applications when this information changes so that they
>>>>>> in turn adapt to the computer's connectivity changes. So you
>>>>>> should not disable that service.
>>>>>>
>>>>>> Is that service started and set to automatic? Do you run
>>>>>> TrendMicro AntiVirus, read about a problem with that AntiVirus
>>>>>> software?
>>>>>>
>>>>>> Best regards
>>>>>>
>>>>>> Meinolf Weber
>>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>>>> and
>>>>>> confers no rights.
>>>>>> ** Please do NOT email, only reply to Newsgroups
>>>>>> ** HELP us help YOU!!!
>>>>>> http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>>>> Our Windows 2008 Terminal Server suffers from an NLASVC timeout
>>>>>>> error. The event ID is 7011.  What's important is once the error
>>>>>>> occurs, the server must be restarted to resume operation.  The
>>>>>>> timeout occurs once every 8 to 12 hours.  The actual error is
>>>>>>> below. The server is running all of the latest patches,
>>>>>>> including SP2.  Can NLASVC be disabled?
>>>>>>>
>>>>>>> Log Name:      System
>>>>>>> Source:        Service Control Manager
>>>>>>> Date:          6/10/2009 3:24:11 PM
>>>>>>> Event ID:      7011
>>>>>>> Task Category: None
>>>>>>> Level:         Error
>>>>>>> Keywords:      Classic
>>>>>>> User:          N/A
>>>>>>> Computer:      KAVSAPP01.knopf.local
>>>>>>> Description:
>>>>>>> A timeout (30000 milliseconds) was reached while waiting for a
>>>>>>> transaction
>>>>>>> response from the NlaSvc service.
>>>>>>> Event Xml:
>>>>>>> <Event
>>>>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>>>>> <System>
>>>>>>> <Provider Name="Service Control Manager"
>>>>>>> Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}"
>>>>>>> EventSourceName="Service
>>>>>>> Control Manager" />
>>>>>>> <EventID Qualifiers="49152">7011</EventID>
>>>>>>> <Version>0</Version>
>>>>>>> <Level>2</Level>
>>>>>>> <Task>0</Task>
>>>>>>> <Opcode>0</Opcode>
>>>>>>> <Keywords>0x80000000000000</Keywords>
>>>>>>> <TimeCreated SystemTime="2009-06-10T19:24:11.000Z" />
>>>>>>> <EventRecordID>108237</EventRecordID>
>>>>>>> <Correlation />
>>>>>>> <Execution ProcessID="0" ThreadID="0" />
>>>>>>> <Channel>System</Channel>
>>>>>>> <Computer>KAVSAPP01.knopf.local</Computer>
>>>>>>> <Security />
>>>>>>> </System>
>>>>>>> <EventData>
>>>>>>> <Data Name="param1">30000</Data>
>>>>>>> <Data Name="param2">NlaSvc</Data>
>>>>>>> </EventData>
>>>>>>> </Event>

"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66278448cbb9cc43505bac@msnews.microsoft.com...
> Hello mark,
>
> DNS looks ok for this server. Because you said both problem machines are
> Terminal servers, maybe you should think about posting to:
> microsoft.public.windows.terminal_services
>
> Are the servers VM's, according to the NIC description VMWare? Are the
> latest VMWare tools installed?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> This is from 1 of the 2 servers.  Both crash, but this server has more
>> issues than the other.
>>
>> Microsoft Windows [Version 6.0.6002]
>> Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
>> C:\Users\administrator.KNOPF>ipconfig /all
>>
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : KAVSAPP01
>> Primary Dns Suffix  . . . . . . . : knopf.local
>> Node Type . . . . . . . . . . . . : Hybrid
>> IP Routing Enabled. . . . . . . . : No
>> WINS Proxy Enabled. . . . . . . . : No
>> DNS Suffix Search List. . . . . . : knopf.local
>> Ethernet adapter Local Area Connection:
>>
>> Connection-specific DNS Suffix  . : knopf.local
>> Description . . . . . . . . . . . : VMware PCI Ethernet Adapter
>> Physical Address. . . . . . . . . : 00-50-56-BD-77-4A
>> DHCP Enabled. . . . . . . . . . . : No
>> Autoconfiguration Enabled . . . . : Yes
>> IPv4 Address. . . . . . . . . . . : 10.100.32.50(Preferred)
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 10.100.32.1
>> DNS Servers . . . . . . . . . . . : 10.100.32.20
>> 10.100.32.30
>> Primary WINS Server . . . . . . . : 10.100.32.20
>> Secondary WINS Server . . . . . . : 10.100.32.30
>> NetBIOS over Tcpip. . . . . . . . : Enabled
>> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
>> news:ff16fb662781c8cbb9b9b8e5a7cc@msnews.microsoft.com...
>>
>>> Hello mark,
>>>
>>> Please post an unedited ipconfig /all from the TS and the DNS/DC.
>>>
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers no rights.
>>> ** Please do NOT email, only reply to Newsgroups
>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>> When the RDP session starts, the user is prompted for credentials.
>>>> Once the credentials are entered and user presses enter (or the
>>>> arrow), the RDP session displays "Welcome" with the rotating circle
>>>> (to the left), but the log on never gets any further.  We've waited
>>>> over 20 minutes and nothing.
>>>>
>>>> Normally, a series of messages are displayed like load profile, etc.
>>>>
>>>> The event log is void of errors.  The console is also hung.  It has
>>>> happened to all users and appears to the connection independent -
>>>> RDP client version, OS version, do not matter.  This happens at
>>>> least once a day, sometimes more.  A hard reboot is required to
>>>> reactivate the server.
>>>>
>>>> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
>>>> news:ff16fb66278168cbb9b7db8fee9c@msnews.microsoft.com...
>>>>
>>>>> Hello mark,
>>>>>
>>>>> "Welcome screen hang"? What do you mean with that, slow logons?
>>>>>
>>>>> Best regards
>>>>>
>>>>> Meinolf Weber
>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>>> and
>>>>> confers no rights.
>>>>> ** Please do NOT email, only reply to Newsgroups
>>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>>> Thanks. For testing purposes, we ended up disabling the NLASVC and
>>>>>> NIS services. The server runs well without them. The NLASVC errors
>>>>>> went away, but the "Welcome Screen" hang is still present and the
>>>>>> server becomes unresponsive and must be rebooted daily.  It has
>>>>>> become such a problem, that we may have have to buildout a
>>>>>> replacement 2003 environment.
>>>>>>
>>>>>> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
>>>>>> news:ff16fb66274e38cbb8bf4b74e5e3@msnews.microsoft.com...
>>>>>>
>>>>>>> Hello mark,
>>>>>>>
>>>>>>> The Network Location Awareness service which collects and stores
>>>>>>> network configuration information such as IP addresses, Workgroup
>>>>>>> and/or Domain name changes (if your PC is connected to a Windows
>>>>>>> network), as well as Location change information, and which
>>>>>>> notifies applications when this information changes so that they
>>>>>>> in turn adapt to the computer's connectivity changes. So you
>>>>>>> should not disable that service.
>>>>>>>
>>>>>>> Is that service started and set to automatic? Do you run
>>>>>>> TrendMicro AntiVirus, read about a problem with that AntiVirus
>>>>>>> software?
>>>>>>>
>>>>>>> Best regards
>>>>>>>
>>>>>>> Meinolf Weber
>>>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>>>>> and
>>>>>>> confers no rights.
>>>>>>> ** Please do NOT email, only reply to Newsgroups
>>>>>>> ** HELP us help YOU!!!
>>>>>>> http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>>>>> Our Windows 2008 Terminal Server suffers from an NLASVC timeout
>>>>>>>> error. The event ID is 7011.  What's important is once the error
>>>>>>>> occurs, the server must be restarted to resume operation.  The
>>>>>>>> timeout occurs once every 8 to 12 hours.  The actual error is
>>>>>>>> below. The server is running all of the latest patches,
>>>>>>>> including SP2.  Can NLASVC be disabled?
>>>>>>>>
>>>>>>>> Log Name:      System
>>>>>>>> Source:        Service Control Manager
>>>>>>>> Date:          6/10/2009 3:24:11 PM
>>>>>>>> Event ID:      7011
>>>>>>>> Task Category: None
>>>>>>>> Level:         Error
>>>>>>>> Keywords:      Classic
>>>>>>>> User:          N/A
>>>>>>>> Computer:      KAVSAPP01.knopf.local
>>>>>>>> Description:
>>>>>>>> A timeout (30000 milliseconds) was reached while waiting for a
>>>>>>>> transaction
>>>>>>>> response from the NlaSvc service.
>>>>>>>> Event Xml:
>>>>>>>> <Event
>>>>>>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>>>>>>>> <System>
>>>>>>>> <Provider Name="Service Control Manager"
>>>>>>>> Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}"
>>>>>>>> EventSourceName="Service
>>>>>>>> Control Manager" />
>>>>>>>> <EventID Qualifiers="49152">7011</EventID>
>>>>>>>> <Version>0</Version>
>>>>>>>> <Level>2</Level>
>>>>>>>> <Task>0</Task>
>>>>>>>> <Opcode>0</Opcode>
>>>>>>>> <Keywords>0x80000000000000</Keywords>
>>>>>>>> <TimeCreated SystemTime="2009-06-10T19:24:11.000Z" />
>>>>>>>> <EventRecordID>108237</EventRecordID>
>>>>>>>> <Correlation />
>>>>>>>> <Execution ProcessID="0" ThreadID="0" />
>>>>>>>> <Channel>System</Channel>
>>>>>>>> <Computer>KAVSAPP01.knopf.local</Computer>
>>>>>>>> <Security />
>>>>>>>> </System>
>>>>>>>> <EventData>
>>>>>>>> <Data Name="param1">30000</Data>
>>>>>>>> <Data Name="param2">NlaSvc</Data>
>>>>>>>> </EventData>
>>>>>>>> </Event>
>
>