Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 650
  • Last Modified:

Windows 7 Pro Client Cannot Join Windows 2003 Domain

I have a small domain with a Windows 2003 DC and 4 XP clients.  Now, I am trying to add a Windows 7 Pro client and am receiving the attached error.  I also have attached the TCPIP properties of the client and the DC.  Please assist.  Thank You
Error---TCPIP-Properties.doc
0
btmtech
Asked:
btmtech
  • 8
  • 6
  • 3
  • +4
2 Solutions
 
Mike ThomasConsultantCommented:
The subnet masks on the client and server differ essentially putting them on diferent networks, change the mask on the win7 machine to match the servers.


0
 
tonyperthCommented:
the subnet on the windows 7 is wrong, it should be 255.255.0.0 not 255.255.255.0
0
 
Mike ThomasConsultantCommented:
So just change the subnet mask on the windows 7 machine to 255.255.0.0 (it is currently on 255.255.255.0)
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
Lytron55Commented:
I am not totally versed in Subnets, but shouldn't the subnet masks for both the client and the Domain Controller be the same?
0
 
acstecheeCommented:
Yes change the subnet to 255.255.0.0 and it will work fine.
0
 
GruedataIT managerCommented:
Check that the rewerse DNS is sett correct on the DC
0
 
tonyperthCommented:
LOL, all together now...
0
 
btmtechAuthor Commented:
The difference in subnet masks is to establish a connection to another domain.  All of the other XP clients have a subnet of 255.255.255.0 and they have no problem in establishing a connection to the domain.  I have tried changing the subnet on the W7 client and it makes no difference.
0
 
btmtechAuthor Commented:
Can you please be more specific on the proper reverse DNS settings on the DC?
0
 
GruedataIT managerCommented:
Go to Administrative tools - dns.
Check that your net is added under rewerse lookup zones.
If not add it.

Wrong configured DNS gives different errormessages. Many of them only on Win7 and vista
0
 
Lytron55Commented:
A couple of things that have gotten me before.  Make sure the domain name is set properly in the client to point to the domain name of DC 192.168.0.10.  
Also if this client had been previously configured to a different domain, you may need to run SYSPREP to release the security information.
0
 
acstecheeCommented:
Try pinging your fully qualified domain name.

E.g. ping sa2.local

This should reply with the ip address of your domain controller.
0
 
btmtechAuthor Commented:
I am using the correct domain name and it has never been with another domain.
0
 
btmtechAuthor Commented:
Pinging the FQDN does not work.  I can ping the DC and gateway.
0
 
Lytron55Commented:
Have you done an ipconfig /flushdns  on the client?
0
 
acstecheeCommented:
sounds like you've got an issue with your dns server to me.

Can you ping the domain name from the server or from other windows clients?

Would be worth running dnsdiag on the server
0
 
acstecheeCommented:
Also try a netdiag /fix
0
 
btmtechAuthor Commented:
Cannot ping the domain from the server.  Trying dnsdiag...
0
 
btmtechAuthor Commented:
How do I run dnsdiag?
0
 
btmtechAuthor Commented:
Run netdiag /fix from the DC or the client?
0
 
acstecheeCommented:
Sorry from the DC.
Dnsdiag and netdiag are windows support tools and you may need to install them from the CD.

Netdiag may be your best bet.

Is DNS running on the server? You should have an A record in there which points (same as parent folder) to the server IP address
0
 
DanMarCommented:
Your AD Integrated DNS zone may be damaged - run netdiag /fix, dcdiag /fix & restart the netlogon service.  If you have errors coming up on either netdiag or dcdiag please post.
0
 
btmtechAuthor Commented:
Can someone please look at our DC's DNS settings and let me know if everything looks ok?
Doc1.doc
0
 
acstecheeCommented:
Hi

These settings look basically right to me but there is something amiss. You don't appear to have a fully qualified domain name?

It looks like your domain name is "SA2.", whereas i'd expect a .local or .com or similar scheme to be used.

can you ping sai-b.sa2 from the clients?

I would definitely run a netdiag /fix with settings like these

0
 
DanMarCommented:
Hi btmtech,
As I thought your AD Integrated zone is missing/damaged.  You need to go through steps as I mentioned previously i.e. netdiag /fix, dcdiag /fix, restart netlogon (on the server).
You can get more info here: http://support.microsoft.com/kb/241505
SRV records need to exist as per this page:
http://support.microsoft.com/kb/816587
BTW, the client machines are still within the subnet of your server as the server encompasses their range.  Ideally the subnet masks should match.
more DNS info here:
816101  (http://support.microsoft.com/kb/816101/ ) HOWTO: Convert DNS Primary Server to Active Directory Integrated
323418  (http://support.microsoft.com/kb/323418/ ) HOW TO: Integrate DNS with an Existing DNS Infrastructure If Active Directory Is Enabled in Windows Server 2003
 324753  (http://support.microsoft.com/kb/324753/ ) HOW TO: Create an Active Directory Server in Windows Server 2003  
0

Featured Post

Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

  • 8
  • 6
  • 3
  • +4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now