Re: Domain not available

Thanks Larry,

Yes, this is a Windows 2003 Server.

Using your information I was able to get into the local machine and
repair the NIC (who would've thought?) but it still did not fix the
problem.

Here is more...

This is a DC in a remote office. This office is connected to the main DC
via router<>router VPN which is a little flakey. The DNS on this DC is
inherited from the main DC. It also appears that my DNS is hosed on the
local DC.

Replication of the AD seemed to not be happening correctly and when the
workstation was able to log in it was doing so by finding the DC over the
VPN and not the local DC.

The workstation can log in IF it is rebooted and you immediately log in.
If you wait any length of time or attempt to log in after you log off it
will throw the error "Windows cannot log you in now because the domain
XXX is not available."



Even after demoting and promoting the local DC it still did not act as a
DC. The workstation still went to the VPN to find the domain.

It's probably time to call the pros, and to find some classes. If I am
going to continue to do this I'm gonna have to learn a little more....


Thanks




"Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@xxxxxxxxxxxxxxx> wrote in
news:6F0C1F34-CE63-46EE-AE7C-FCEAC2EA4B50@xxxxxxxxxxxxx:

Hi Mark:

Is the DC you reference SBS 2003, which is the focus of this group?
If not, you may be better off in the standard Windows Server group.

I can add that if as you seem to say, you cannot logon to the errant
workstation, and it cannot be found on the network from other
computers on the network, and if you cannot determine that it is set
to receive DHCP, or indeed that the network adapter is working, you
probably need to fix those issues.

Apparently the password for any local user has been lost? If you need
to release the local admin password to gain control of the
workstation, have a look at this:

http://www.petri.co.il/forgot_administrator_password.htm

In particular

Petter Nordahl-Hagen's Offline NT Password & Registry Editor

about 2/3 down the page. I use it under similar conditions, and can
testify that it works.

Larry

"Mark" <mtaylor*@*lrim.com> wrote in message
news:1212836083_4126@xxxxxxxx
I am receiving the dreaded error "Cannot log you in now because the
domain "XXX" is not available."


Well a laptop plugged into the adjoining port works fine, but is
configured to know where to find the local DNS server.

The workstation not able to log in is a Windows XP machine and I
think the network adapter is configured to receive an IP
automatically, and no DNS information is provided. So, it is strictly
relying on windows networking to ID the machine and get an IP
address. But it doesn't seem to be working. Once booted the machine
cannot be seen on the network, not does it have an IP address.

The complication is that we cannot log into the machine locally to
fix this at the workstation level, if there is indeed anything wrong
with the workstation. I think that something in the DC is not
broadcasting something so that the workstation can receive an IP
address. Question is, what exactly is it?

I have rebooted the DC, restarted services such as WINS, DNS,
Browser, etc. Removed the machine from the AD list. The only thing I
have not done, and really do not want to do is demote and promote the
machine.

I don't really know what else to try at this point. I thought I'd run
it by you guys before I called in the $1000 per day company....


Any suggestions?
Thanks
Mark

--


----== Posted via Pronews.Com - Unlimited-Unrestricted-Secure Usenet
News==----
http://www.pronews.com The #1 Newsgroup Service in the World!
100,000 Newsgroups
---= - Total Privacy via Encryption =---





--


----== Posted via Pronews.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.pronews.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= - Total Privacy via Encryption =---
.

Relevant Pages

  • Re: Branch Office Networking
    ... Troubleshooting Windows Event ID ... BRANCH OFFICE CLIENT ... DNS SUFFIC SEARCH LIST...ATW.LOCAL ... > Everything works fine (able to access network, email, dns, etc.). ...
    (microsoft.public.windows.server.networking)
  • Printer driver-related network delays
    ... I've got a Windows XP LAN comprised of several workstations and printers. ... Every time someone on a workstation tries to print to a network printer from ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Cannot obtaion domain controller
    ... DC and DNS on same machine. ... Windows IP Configuration ... Ethernet adapter Office Network: ... Client details. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Printer driver-related network delays
    ... I've got a Windows XP LAN comprised of several workstations and printers. ... Every time someone on a workstation tries to print to a network printer ... Why does Windows XP insist on gathering information or drivers from ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Domain not available
    ... you may be better off in the standard Windows Server group. ... I can add that if as you seem to say, you cannot logon to the errant workstation, and it cannot be found on the network from other computers on the network, and if you cannot determine that it is set to receive DHCP, or indeed that the network adapter is working, you probably need to fix those issues. ...
    (microsoft.public.windows.server.sbs)