Event ID 1219 - Server 2003 (UNABLE TO ACCESS)

[Steve]

We have a Windows 2003 Server Standard edition SP1 that is displaying this
event id error in the event logs.

Event ID: 1219
Source: WinLogon
Category: None

Description
“Logon rejected for DOMAIN/USERNAME. Unable to obtain Terminal Server User
Configuration. Not enough resources are available to complete this operation”

The server hangs up and doesn’t let anyone access the share folders or even
remote desktop into it. We have been restarting the server in the past and
this is the only thing that seems to fix the problem temporarily. We have
enough memory for this server (3.75 GB Intel Xeon CPU 2.00 Ghz). Any ideas?


Thanks!

[Robert L [MVP - Networking]]

I think MS has a hotfix for that issue. This search result may help,

Event ID TroubleshootingEvent ID 1219 - Unable to obtain Terminal Server User Configuration Event ID 1311 - There are currently no logon servers available to service the logon ...
http://www.chicagotech.net/wineventid.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Steve" <Steve@discussions.microsoft.com> wrote in message news:43C421A8-03F4-4276-BBDD-D4D27C0C334E@microsoft.com...
We have a Windows 2003 Server Standard edition SP1 that is displaying this
event id error in the event logs.

Event ID: 1219
Source: WinLogon
Category: None

Description
“Logon rejected for DOMAIN/USERNAME. Unable to obtain Terminal Server User
Configuration. Not enough resources are available to complete this operation”

The server hangs up and doesn’t let anyone access the share folders or even
remote desktop into it. We have been restarting the server in the past and
this is the only thing that seems to fix the problem temporarily. We have
enough memory for this server (3.75 GB Intel Xeon CPU 2.00 Ghz). Any ideas?


Thanks!

[Steve]

Robert thanks for the quick reply. We are not running Windows 2000 server
and this is not our Terminal Server. This server is up to date with all of
its Microsoft Updates. Any other suggestions will be higly appreciated

"Robert L [MVP - Networking]" wrote:

> I think MS has a hotfix for that issue. This search result may help,
>
> Event ID TroubleshootingEvent ID 1219 - Unable to obtain Terminal Server User Configuration Event ID 1311 - There are currently no logon servers available to service the logon ...
> http://www.chicagotech.net/wineventid.htm
>
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "Steve" <Steve@discussions.microsoft.com> wrote in message news:43C421A8-03F4-4276-BBDD-D4D27C0C334E@microsoft.com...
> We have a Windows 2003 Server Standard edition SP1 that is displaying this
> event id error in the event logs.
>
> Event ID: 1219
> Source: WinLogon
> Category: None
>
> Description
> “Logon rejected for DOMAIN/USERNAME. Unable to obtain Terminal Server User
> Configuration. Not enough resources are available to complete this operation”
>
> The server hangs up and doesn’t let anyone access the share folders or even
> remote desktop into it. We have been restarting the server in the past and
> this is the only thing that seems to fix the problem temporarily. We have
> enough memory for this server (3.75 GB Intel Xeon CPU 2.00 Ghz). Any ideas?
>
>
> Thanks!
>

[Robert L [MVP - Networking]]

It could be the name resolution issue. Any errors if using nslookup and netdiag?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Steve" <Steve@discussions.microsoft.com> wrote in message news:52D00615-B9B7-4656-BD80-3708B61D3432@microsoft.com...
Robert thanks for the quick reply. We are not running Windows 2000 server
and this is not our Terminal Server. This server is up to date with all of
its Microsoft Updates. Any other suggestions will be higly appreciated

"Robert L [MVP - Networking]" wrote:

> I think MS has a hotfix for that issue. This search result may help,
>
> Event ID TroubleshootingEvent ID 1219 - Unable to obtain Terminal Server User Configuration Event ID 1311 - There are currently no logon servers available to service the logon ...
> http://www.chicagotech.net/wineventid.htm
>
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "Steve" <Steve@discussions.microsoft.com> wrote in message news:43C421A8-03F4-4276-BBDD-D4D27C0C334E@microsoft.com...
> We have a Windows 2003 Server Standard edition SP1 that is displaying this
> event id error in the event logs.
>
> Event ID: 1219
> Source: WinLogon
> Category: None
>
> Description
> “Logon rejected for DOMAIN/USERNAME. Unable to obtain Terminal Server User
> Configuration. Not enough resources are available to complete this operation”
>
> The server hangs up and doesn’t let anyone access the share folders or even
> remote desktop into it. We have been restarting the server in the past and
> this is the only thing that seems to fix the problem temporarily. We have
> enough memory for this server (3.75 GB Intel Xeon CPU 2.00 Ghz). Any ideas?
>
>
> Thanks!
>