Cannot login to domain controller

The problem:

"Windows cannot connect to the domain, either because the domain controller
is down or otherwise unavailable, or because your computer account was not
found. Please try again later. If this message continues to appear, contact
your system administrator for assistance."

For the most part everything is working fine. Occasionally Iâ??ll get the
above message and I can fix it by leaving the domain and joining it again.
Sometimes the problem will come back in a few days, sometimes weeks later. On
other workstations after correcting it once the problem never returns.

I donâ??t see any errors generated in the workstation or domain controller
event logs. The workstation has the correct DNS for the domain controller. It
can ping the DNS controller. It can leave and join the domain with no
problems at all.

The problem seems to happen mostly to laptop users that take their PC away
from the domain for a few days, but itâ??s not isolated to these users. It has
happened to desktop users too.

The server is running Windows Server 2003 R2. Itâ??s connected to another
domain controller via a VPN using Logmein Hamachi. I have another location
with the same configuration with but it does not experience the same
problems.

Any ideas on what can be causing the problem?

Meinolf
Fri Aug 15 00:00:34 PDT 2008

Hello patrick,

Please post an unedited ipconfig /all from the DC and a problem client. How
do you logon to the DC, with Remote desktop? Or do you mean logon to the
domain, which sounds more correct from the posting? What measn you have another
location, is this also the same domain or a different? Please post your domain
names you are using.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> The problem:
>
> "Windows cannot connect to the domain, either because the domain
> controller is down or otherwise unavailable, or because your computer
> account was not found. Please try again later. If this message
> continues to appear, contact your system administrator for
> assistance."
>
> For the most part everything is working fine. Occasionally Iâ??ll get
> the above message and I can fix it by leaving the domain and joining
> it again. Sometimes the problem will come back in a few days,
> sometimes weeks later. On other workstations after correcting it once
> the problem never returns.
>
> I donâ??t see any errors generated in the workstation or domain
> controller event logs. The workstation has the correct DNS for the
> domain controller. It can ping the DNS controller. It can leave and
> join the domain with no problems at all.
>
> The problem seems to happen mostly to laptop users that take their PC
> away from the domain for a few days, but itâ??s not isolated to these
> users. It has happened to desktop users too.
>
> The server is running Windows Server 2003 R2. Itâ??s connected to
> another domain controller via a VPN using Logmein Hamachi. I have
> another location with the same configuration with but it does not
> experience the same problems.
>
> Any ideas on what can be causing the problem?
>

akvkollam
Mon Aug 18 02:16:11 PDT 2008


Hi
Do you have two domain controllers in your network...
Check the replication is taking place,it can be a problem of
that.......


--
akvkollam
------------------------------------------------------------------------
akvkollam's Profile: http://forums.techarena.in/members/akvkollam.htm
View this thread: http://forums.techarena.in/active-directory/1020800.htm

http://forums.techarena.in

Patrick
Mon Aug 18 16:57:10 PDT 2008

I do have more than one domain controller. I don't see any problems with the
replication. If it were a DC replication problem I would that it would affect
all the PC's that use that DC to authenticate. Am I wrong?

"akvkollam" wrote:

>
> Hi
> Do you have two domain controllers in your network...
> Check the replication is taking place,it can be a problem of
> that.......
>
>
> --
> akvkollam
> ------------------------------------------------------------------------
> akvkollam's Profile: http://forums.techarena.in/members/akvkollam.htm
> View this thread: http://forums.techarena.in/active-directory/1020800.htm
>
> http://forums.techarena.in
>
>

Patrick
Mon Aug 18 17:05:00 PDT 2008

You are correct that I mean I logon to to the domain, not remote desktop into
the domain controller.

Regarding the other location, it's the same domain name in a different
location. Doman is domain1.local


Here is the IP Config for the problem workstation:


Windows IP Configuration
Host Name . . . . . . . . . . . . : Admin-02-04a
Primary Dns Suffix . . . . . . . : domain1.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain1.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit
Controller
Physical Address. . . . . . . . . : 00-11-43-2E-EE-58
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.2.187
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.2.1
DHCP Server . . . . . . . . . . . : 10.0.2.1
DNS Servers . . . . . . . . . . . : 10.0.2.3
Lease Obtained. . . . . . . . . . : Monday, August 18, 2008 9:59:23 AM
Lease Expires . . . . . . . . . . : Monday, August 18, 2008 10:59:23
AM


Windows IP Configuration

Host Name . . . . . . . . . . . . : server-02
Primary Dns Suffix . . . . . . . : domain1.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain1.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE
(NDIS VBD Client)
Physical Address. . . . . . . . . : 00-1E-C9-47-81-90
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.2.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.2.1
DNS Servers . . . . . . . . . . . : 10.0.2.3
5.131.84.250
5.224.41.39
5.224.42.171
5.38.145.44

Ethernet adapter Hamachi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hamachi Network Interface
Physical Address. . . . . . . . . : 7A-79-05-E0-2A-AB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : No
IP Address. . . . . . . . . . . . : 5.224.42.171
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 5.0.0.1
Lease Obtained. . . . . . . . . . : Wednesday, August 13, 2008 3:14:03 AM
Lease Expires . . . . . . . . . . : Thursday, August 13, 2009 3:14:03 AM


"Meinolf Weber" wrote:

> Hello patrick,
>
> Please post an unedited ipconfig /all from the DC and a problem client. How
> do you logon to the DC, with Remote desktop? Or do you mean logon to the
> domain, which sounds more correct from the posting? What measn you have another
> location, is this also the same domain or a different? Please post your domain
> names you are using.
>
> Best regards
>
>

Patrick
Tue Aug 19 06:57:01 PDT 2008

The problem client and the domain controller are in the same location
connected to the same switch.

The domain controller is also connected to a VPN using LogMeIn Hamachi. The
VPN is used to sync the domain controllers.

The OS is Windows 2003 R2 x64 Standard Edition.

The reason for the second IP address on the DC is for the VPN.

If multihomed DC is a bad idea, what else can I do to sync the two DC?




"Meinolf Weber" wrote:

> Hello Patrick,
>
> Please describe a bit more your network configuration, switches routers etc.
> Because you said the client is on a different location and use the same ip
> configuration as it will be in the same location like the server. Also you
> choose a really bad option with multihoming a Domain controller, or is the
> OS a SBS version from windows? What's the reason for the second ip address
> on the DC?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > You are correct that I mean I logon to to the domain, not remote
> > desktop into the domain controller.
> >
> > Regarding the other location, it's the same domain name in a different
> > location. Doman is domain1.local
> >
> > Here is the IP Config for the problem workstation:
> >
> > Windows IP Configuration
> > Host Name . . . . . . . . . . . . : Admin-02-04a
> > Primary Dns Suffix . . . . . . . : domain1.local
> > Node Type . . . . . . . . . . . . : Unknown
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : domain1.local
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Broadcom NetXtreme 57xx
> > Gigabit
> > Controller
> > Physical Address. . . . . . . . . : 00-11-43-2E-EE-58
> > Dhcp Enabled. . . . . . . . . . . : Yes
> > Autoconfiguration Enabled . . . . : Yes
> > IP Address. . . . . . . . . . . . : 10.0.2.187
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 10.0.2.1
> > DHCP Server . . . . . . . . . . . : 10.0.2.1
> > DNS Servers . . . . . . . . . . . : 10.0.2.3
> > Lease Obtained. . . . . . . . . . : Monday, August 18, 2008
> > 9:59:23 AM
> > Lease Expires . . . . . . . . . . : Monday, August 18, 2008
> > 10:59:23
> > AM
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . . . . : server-02
> > Primary Dns Suffix . . . . . . . : domain1.local
> > Node Type . . . . . . . . . . . . : Unknown
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : domain1.local
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II
> > GigE
> > (NDIS VBD Client)
> > Physical Address. . . . . . . . . : 00-1E-C9-47-81-90
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 10.0.2.3
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 10.0.2.1
> > DNS Servers . . . . . . . . . . . : 10.0.2.3
> > 5.131.84.250
> > 5.224.41.39
> > 5.224.42.171
> > 5.38.145.44
> > Ethernet adapter Hamachi:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Hamachi Network Interface
> > Physical Address. . . . . . . . . : 7A-79-05-E0-2A-AB
> > DHCP Enabled. . . . . . . . . . . : Yes
> > Autoconfiguration Enabled . . . . : No
> > IP Address. . . . . . . . . . . . : 5.224.42.171
> > Subnet Mask . . . . . . . . . . . : 255.0.0.0
> > Default Gateway . . . . . . . . . :
> > DHCP Server . . . . . . . . . . . : 5.0.0.1
> > Lease Obtained. . . . . . . . . . : Wednesday, August 13, 2008
> > 3:14:03 AM
> > Lease Expires . . . . . . . . . . : Thursday, August 13, 2009
> > 3:14:03 AM
> > "Meinolf Weber" wrote:
> >
> >> Hello patrick,
> >>
> >> Please post an unedited ipconfig /all from the DC and a problem
> >> client. How do you logon to the DC, with Remote desktop? Or do you
> >> mean logon to the domain, which sounds more correct from the posting?
> >> What measn you have another location, is this also the same domain or
> >> a different? Please post your domain names you are using.
> >>
> >> Best regards
> >>
>
>
>

Patrick
Thu Aug 21 07:08:00 PDT 2008

Thank you. Your answer has been helpful in identifiying the potential cause
of my problem.

Using a member server for VPN is not an option for me because I do not have
a second server at that location. I'll switch to router based VPN.

"Meinolf Weber" wrote:

> Hello Patrick,
>
>
> For VPN's use a member server with RAS installed, so that this machine handles
> the VPN connections.
>