Windows 7 won't connect to domain

[seema75]

Hi there,

I have been using Windows 7 with domain "domain1" and connected to Windows Server 2003. The owners decided to change the domain of the network from "domain1" to "domain2". Someone was hired to do the job for the company. Since I was on work tour my PC was left without any change. Now the gentleman is gone and I can not connect the domain on Windows 2003 Server. I was told to remove previous domain and switch to WORKGROUP and then switch back to "domain2".

I followed the steps till I get to username and password window. I enter my username and password and after few minutes I get the following error:

"An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the terget domain"

Please help.

 

[ryo]

hello and welcome
when you change the domain name with "domain2"
make sure that's the DNS on the windows server 2003 already configuration. because before Windows server 2003 is read the first domain ( domain1), that's why you can't to login.


Edit : http://www.sevenforums.com/network-sharing/47447-joining-domain.html
you can try this..i think that's same issue..

Cheers ~

 

[aem]

Make sure the machine is back to WORKGROUP ie you left the D1.

Restart the machine, and make sure you are on the network of D2. Join the new domain using the wizard (ie click the Network ID icon)

 

[seema75]

Make sure the machine is back to WORKGROUP ie you left the D1.

Restart the machine, and make sure you are on the network of D2. Join the new domain using the wizard (ie click the Network ID icon)

hello and welcome
when you change the domain name with "domain2"
make sure that's the DNS on the windows server 2003 already configuration. because before Windows server 2003 is read the first domain ( domain1), that's why you can't to login.


Edit : http://www.sevenforums.com/network-sharing/47447-joining-domain.html
you can try this..i think that's same issue..

Cheers ~

I have already confirmed what you have advised. Thanks for the tip though.

 

[aem]

And you have already made sure you have entered in the correct spelling of the domain name?

I had this issue just the other day, and the wizard method works.

 

[seema75]

And you have already made sure you have entered in the correct spelling of the domain name?

I had this issue just the other day, and the wizard method works.

Yes.

I'm able to use internet. I'm able to see and use shared content on the server too. (using my login and password)

 

[aem]

Do you mind screenshooting thru the steps of the wizard, and show us your ipconfig /all details?

Other than posible issue with AD not replicating, i'm not sure what to think.

 

[chev65]

Usually, just entering the Domain DNS servers manually in the network connection properties of the problem machine will get you access to the Domain server. The routers firewalls tends to block this info from being obtained otherwise.

 

[aem]

I'm sure there is no need to enter the DNS details, the machine is set to auto detect ip, so at the most i would think there is a DNS cache issue.

ipconfig /flushdns

Log on with administrator account/priv.
Use the wizard making sure there is no typo into the network name and that should do it.

 

[chev65]

I'm sure there is no need to enter the DNS details, the machine is set to auto detech ip, so at the most i would think there is a DNS cache issue.

ipconfig /flushdns

Log on with administrator account/priv.
Use the wizard making sure there is no typo into the network name and that should do it.

Could be cache or it's being blocked, not sure really but it's come up before so I figured it was worth mentioning.

For what ever reason the DNS info isn't being picked up because the Domains router firewall blocks it and causes this problem.

Point in case> http://www.sevenforums.com/network-...use-domain-network-location-2.html#post655005

 

[aem]

I'm not 100% either but he is on the new domain/LAN and can surf the net??, so based on that it shouldn't be a router/firewall issue. It's a work environment also and i'll be surprised if they need to change the router/firewall setting just by renaming a domain in AD.

With AD, replication is vital, maybe the DNS service needs a restart...etc.

Worth a try with the DNS though, anything goes.

 

[ryo]

Make sure the machine is back to WORKGROUP ie you left the D1.

Restart the machine, and make sure you are on the network of D2. Join the new domain using the wizard (ie click the Network ID icon)

hello and welcome
when you change the domain name with "domain2"
make sure that's the DNS on the windows server 2003 already configuration. because before Windows server 2003 is read the first domain ( domain1), that's why you can't to login.


Edit : http://www.sevenforums.com/network-sharing/47447-joining-domain.html
you can try this..i think that's same issue..

Cheers ~

I have already confirmed what you have advised. Thanks for the tip though.

that's solved your problem??