My guess is that it is related to the domain's password policy...
On Fri, Mar 14, 2014 at 8:43 PM, Mike Tobias < [email protected]> wrote: > I'll file that one away in the back of my brain in case I ever run into > it. Glad you figured it out and took the time to confirm that was the issue! > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *J- P > *Sent:* Friday, March 14, 2014 8:21 PM > *To:* [email protected] > *Subject:* RE: Re[2]: [NTSysADM] unable to join domain-solved > > > > so tested again today on a win7 pc that had a blank password for a local > admin account, and the same result- > unable to join domain- i applied a password to the account and it worked- > > > > Jean-Paul Natola > > > ------------------------------ > > From: [email protected] > To: [email protected] > Subject: RE: Re[2]: [NTSysADM] unable to join domain > Date: Fri, 14 Mar 2014 18:31:07 +0000 > > I have receive that error before because I had to use the fully qualified > domain name "contoso.acme.com" (without the quotes of course). > > > > Dave Landry > > Site Support Administrator > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Hank Arnold > *Sent:* Friday, March 14, 2014 1:59 PM > *To:* [email protected] > *Subject:* Re[2]: [NTSysADM] unable to join domain > > > > It's usually the wrong time zone for me. > > > > *Regards,* > Hank Arnold > > > > > > Twitter: @Hank_PCDoc > > Facebook: https://www.facebook.com/hank.arnold.96 > > My Blog: > *http://it.toolbox.com/blogs/personal-pc-assistant/*<http://it.toolbox.com/blogs/personal-pc-assistant/> > > > > > > > > ------ Original Message ------ > > From: "Melvin Backus" <[email protected]> > > To: "[email protected]" <[email protected]> > > Sent: 3/13/2014 1:31:39 PM > > Subject: RE: [NTSysADM] unable to join domain > > > > Good point. I've run across problems in the past where everything looked > correct. Turned out the year was wrong. L > > > > -- > There are 10 kinds of people in the world... > those who understand binary and those who don't. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Mark Gottschalk > *Sent:* Thursday, March 13, 2014 1:25 PM > *To:* [email protected] > *Subject:* Re: [NTSysADM] unable to join domain > > > > Extreme time skew between PC and domain controller? Does the time zone, > time, etc match? > > -- Mark > > > [email protected] wrote on 03/11/2014 04:31:30 PM: > > > From: J- P <[email protected]> > > To: "[email protected]" <[email protected]>, > > Date: 03/11/2014 04:31 PM > > Subject: [NTSysADM] unable to join domain > > Sent by: [email protected] > > > > Have a new pc (vostro 270) delivered to our field office, they did a > > win 7 pro downgrade, > > I spent the better part of the day (off and on) trying to join the > > domain, continuously got the "could not contact a domain > > controller...." it's not in English I'm not going to copy paste the > error. > > > > > > remote office has a 2008r2 DC/DNS/GC; > > 1. can ping by name and ip (both ways)server to workstation and vice > versa; > > 2. we are VPNd to HQ and the can ping the FSMO over VPN; > > 3. can remote desktop both ways. > > 4.did a manual config of IP and DNS servers > > 5. turned off firewall bot server and workstation > > 6. tried manually applying DNS of HQ Domain Controllers > > 7. Can browse network and connect to the servers share (with > > alternate credentials of course) > > > > is there any possibility, that there is an issue with the OS > installation? > > > > I have joined PC's remotely before to this and all field offices and > > have never had this issue > > > > I'm going to try netmon when I get home later > > > > but getting a bit frustrated > >
<<inline: image001.png>>
