We have a server here that is running Windows Server 2003 SE w/ SP1. It is
our VPN server. After it has been running for a while with no one using it
there are often issues when trying to log in. If you actually go to the
server and log into the console you will often just get a blank screen; all
you will be able to see if the cursor.
If you attempt to log in remotely using remote desktop the screen will go
blank for a few minutes and then throw up and error message stating that the
system could not log you in because the RPC server was unavailable.
Also, even when the server is rebooted you attempt to log in it may stay at
the "Applying Settings" screen for a long time (maybe 15+ minutes?).
These are some of the EventIDs we see in the event viewer:
Event ID: 1219
Logon rejected for domain\user. Unable to obtain Terminal Server User
Configuration. Error: The RPC server is unavailable.
Event ID: 1053
Windows cannot determine the user or computer name. (The RPC server is
unavailable. ). Group Policy processing aborted.
Event ID: 1030
Windows cannot query for the list of Group Policy objects. Check the event
log for possible messages previously logged by the policy engine that
describes the reason for this.
Event ID: 5719
This computer was not able to set up a secure session with a domain
controller in domain DOMAIN due to the following:
The RPC server is unavailable.
This may lead to authentication problems. Make sure that this computer is
connected to the network. If the problem persists, please contact your domain
administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up
the secure session to the primary domain controller emulator in the specified
domain. Otherwise, this computer sets up the secure session to any domain
controller in the specified domain.
(note: this server is not a DC)
Event ID: 7
The kerberos subsystem encountered a PAC verification failure. This
indicates that the PAC from the client SERVER$ in realm DOMAIN.COM had a PAC
which failed to verify or was modified. Contact your system administrator.
------------------------------------------------
Any ideas on what could be causing all of this? None of this seems to be
affecting its performance running our VPNs, but it's extremely annoying to
not be able to log in right away when we need to check something.... the
server will simply be unresponsive for 10-15 minutes and then the desktop
will finally appear.
Thanks!
our VPN server. After it has been running for a while with no one using it
there are often issues when trying to log in. If you actually go to the
server and log into the console you will often just get a blank screen; all
you will be able to see if the cursor.
If you attempt to log in remotely using remote desktop the screen will go
blank for a few minutes and then throw up and error message stating that the
system could not log you in because the RPC server was unavailable.
Also, even when the server is rebooted you attempt to log in it may stay at
the "Applying Settings" screen for a long time (maybe 15+ minutes?).
These are some of the EventIDs we see in the event viewer:
Event ID: 1219
Logon rejected for domain\user. Unable to obtain Terminal Server User
Configuration. Error: The RPC server is unavailable.
Event ID: 1053
Windows cannot determine the user or computer name. (The RPC server is
unavailable. ). Group Policy processing aborted.
Event ID: 1030
Windows cannot query for the list of Group Policy objects. Check the event
log for possible messages previously logged by the policy engine that
describes the reason for this.
Event ID: 5719
This computer was not able to set up a secure session with a domain
controller in domain DOMAIN due to the following:
The RPC server is unavailable.
This may lead to authentication problems. Make sure that this computer is
connected to the network. If the problem persists, please contact your domain
administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up
the secure session to the primary domain controller emulator in the specified
domain. Otherwise, this computer sets up the secure session to any domain
controller in the specified domain.
(note: this server is not a DC)
Event ID: 7
The kerberos subsystem encountered a PAC verification failure. This
indicates that the PAC from the client SERVER$ in realm DOMAIN.COM had a PAC
which failed to verify or was modified. Contact your system administrator.
------------------------------------------------
Any ideas on what could be causing all of this? None of this seems to be
affecting its performance running our VPNs, but it's extremely annoying to
not be able to log in right away when we need to check something.... the
server will simply be unresponsive for 10-15 minutes and then the desktop
will finally appear.
Thanks!
Facebook
Twitter