Re: "domain does not exist" via RDP

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

Didn't read correctly, sorry.

This can be related to dns if it is only happening on one the machine or
more widespread issues if this same thing is happening on multiple machines.
Can you provide additional details as to how widespread and check the Event
Logs of the Dc and the workstation.

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Reentrant" <nospam@xxxxxxxxxx> wrote in message
news:6l3qeoFafi4sU1@xxxxxxxxxxxxxxxxxxxxx
Paul Bergson [MVP-DS] wrote:
Make sure the TS service is running on the DC. Also can you remote
to the DC from itself? Did you check to make sure remote console was
checked to enabled?


"Reentrant" <nospam@xxxxxxxxxx> wrote in message
news:6l3b2bFa8ddlU1@xxxxxxxxxxxxxxxxxxxxx
A UPS fault led to corrupt SYSVOLs on both our DCs (fixed now by a D4
authoritative restore). But before it was fixed, trying to log onto
any of our servers or DCs via Remote Desktop gave a "domain does not
exist" error. But I could log on via the KVM console (fortunately!).
I'm just curious why this would be.

--
Reentrant

As I said in my original post, a D4 authoritative restore of SYSVOL using
http://support.microsoft.com/kb/315457 completely fixed the problem - not
a single error or warning in any of the event logs since and everything is
now fine (apart from one dead UPS). I haven't touched DNS.

My question was: why could I log onto the DCs via their console - using a
domain logon, obviously, as there are no local accounts - but trying to
logon via Remote Desktop gave the "domain does not exist" error after the
logon screen (ie after entering username & password).

Maybe cached credentialsare different for console and RDP logons?

--
Reentrant



.

Relevant Pages

  • Re: Domain name at logon differs from the name of the domain
    ... In DNS manager right click on the zone, and look at "Allow Dynamic Updates" ... > but attempting to logon to it brings the error "no domain ... >>NetBIOS domain name, as this is part of SAM logon name. ... >>Microsoft MVP Windows Server - Active Directory ...
    (microsoft.public.win2000.active_directory)
  • Re: 2min or more delay longing on to domain with XP Pro SP2
    ... When you say that things changed with the fast logon optimization disabled, ... Certainly not DNS, ... >> As for logging, do you simply mean EVENT Viewer logging or ...
    (microsoft.public.win2000.active_directory)
  • Re: Please wait while the domain list is created
    ... Delayed logons are often a dns issue in that the computer is having a ... that W2K/XP Pro domain computers point ONLY to domain controllers running ... netdiag and dcdiag should be helpful to you. ... policy that can cause very long logon times and/or logon failures. ...
    (microsoft.public.windows.server.networking)
  • Re: Event 5774 /DNS errors/Latest updates
    ... it too is handling DNS as well as all ... Upon a reboot, the FIRST ... Subsequent logon by other workstations are all doomed. ... the commands you ...
    (microsoft.public.win2000.dns)
  • Re: active directory replication
    ... >> record in the dns console from the local dc. ... so I connected to maindc. ... >> server was listed as frostburg, which is a dc at another remote site. ...
    (microsoft.public.windows.server.active_directory)