Re: Invalid network address

sounds like it's losing it's ability to communicate with the domain
controllers. I would start troubleshooting in that direction. IP settings,
DNS, communication to the DC's, DC replication, etc.

Jeff Pitsch
http://www.sbcgatekeeper.com
Your terminal services security website

"shawner47" <ssmith@xxxxxxxxxxxxxx> wrote in message
news:6bagi1djp2kp05n01mcl4eab88eb3s8l6c@xxxxxxxxxx
> Yes to all. The event log messages are similar to the logon messages.
> "Logon rejected for DOMAIN\user. Unable to obtain Terminal Server
> User configuration. Error: The network address is invalid."
>
> The logon screen comes up, but when you enter the information and hit
> enter, it gives the error. As I said, the local administrator account
> can logon with no problems. I am quite puzzled.
>
> Thanks!
> Shawn
>
>
> On Wed, 14 Sep 2005 09:35:08 -0400, "Jeff Pitsch"
> <jeff@xxxxxxxxxxxxxxxxx> wrote:
>
>>Any errors in the event logs? Are you able to ping the server when it is
>>in
>>this state? Are you able to pull up the login screen when this happens?
>>
>>Jeff Pitsch
>>http://www.sbcgatekeeper.com
>>Your terminal services security website
>>
>>
>>"shawner47" <ssmith@xxxxxxxxxxxxxx> wrote in message
>>news:ug8gi1hh09t3b5i5ut01f1giviq4ec09a4@xxxxxxxxxx
>>> Hello all,
>>> I am hoping someone can help me out here. I am very new to
>>> Terminal Services and I am experiencing a problem that I can't seem to
>>> find an answer for. I installed Terminal Services yesterday and this
>>> problem popped up instantly. When I first boot up my Win2k3 Term
>>> Server, clients can log in with no problem. After a while (random
>>> times) however, when they try to log on again, a Logon Message pops up
>>> and says that "The system cannot log you on due to the following
>>> error: the network address is invalid" or "The system cannot log you
>>> on due to the following error: The RPC server is unavailable" This is
>>> the case for all users including administrator, except for the local
>>> administrator account on the machine. This is running on an hp BL30p
>>> blade with the NIC's teamed, if that may be of any help. Any help
>>> would be greatly appreciated! Thanks in advance!
>>>
>>> Cheers,
>>> Shawn
>>
>


.

Relevant Pages

  • Re: Users Cant Log Into Local Machine That Is Attached To A Domai
    ... Are you trying to access to a T.S server? ... Are you trying to access via RDC (Remote desktop connection) to a Windows ... Terminal Services Client Error Message: You Do Not Have Access to Logon to ... You do not have access to logon to the Session. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Users Cant Log Into Local Machine That Is Attached To A Domai
    ... Are you trying to access via RDC (Remote desktop connection) to a Windows ... Terminal Services Client Error Message: You Do Not Have Access to Logon to ... Systems Administrator ... You do not have access to logon to the Session. ...
    (microsoft.public.windows.server.active_directory)
  • Re: obscure logon events?
    ... These don't explain reason of these event entries. ... Logon even: 540 A user successfully logged on to a network. ... You can safely ignore this event log and it should ...
    (microsoft.public.windows.server.sbs)
  • Re: Preparing Network Connections... forever
    ... Windows IP Configuration ... Connection-specific DNS Suffix. ... "Replication Services" event log contained the same error as originally posted. ... The failure code from authentication protocol Kerberos was "There are currently no logon servers ...
    (microsoft.public.windows.server.active_directory)
  • Re: Failure Audit 537 in Event Log
    ... You get the event 537 in SBS event log. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... | Logon Failure: ...
    (microsoft.public.windows.server.sbs)