Inability to connect a Windows 7 Pro system to a Windows Server 2003 domain.
I have an existing Windows Server 2003 with several XP clients that operate quite well. I have attempted to add two new Windows 7 Pro systems to the existing domain but am having difficulty contacting the Active Directory Domain Controller (AD DC). Internet functions properly from both systems but I cannot connect to the Domain. I'm using static IPs (no conflicts) and Gateways and DNS settings match those on the XP systems. I've used the Network Connection Wizard and manual attempts at connection but to no avail. Since the errors are identical on both Workstations, must I assume that the server is the problem or am I missing something in the Windows 7 O/S?Is Windows 7 Pro compatible with Windows Server 2003?Any ideas, please?
January 16th, 2010 6:42am

AFAIK, you need Windows 7 Professional or Ultimate to connect to a domain. _________________________ If this was helpful, please vote by clicking the green triangle. If it solves the issue, click "Propose as Answer". Thanks.
Free Windows Admin Tool Kit Click here and download it now
January 16th, 2010 1:42pm

I did specify that I am trying to connect Windows 7 Professional systems to the domain, but they will not connect. I neglected to say that the systems originally came with the Home Premium edition but were successfully upgraded to the Porfessional edition with WAU Home Premium to Professional key.If anyone has an idea of what's going on or what I'm missing, I would appreciate a reply.Thanks,Tom
January 17th, 2010 8:54am

Hi Tom_the_PianoMan, Thanks for using Microsoft Answers! I'm moving your thread to the Windows 7 Networking forums in the TechNet community. They'll be able to better assist you there.Cody C Microsoft Answers Support Engineer Visit our Microsoft Answers Feedback Forum and let us know what you think.
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2010 7:58am

Yes, Win 7 Pro works fine with Server 2003. Since you did a manual config, double-check that the Win 7 machines are using the DC's IPv4 address for DNS (and no other). If that is OK, what happens if you do an nslookup of your domain's FQDN (eg mydomain.local) from a Win 7 client?Bill
January 25th, 2010 9:45am

Hi TomI'm using a single test instance of Windows 7 pro on a laptop joined to a 2003 AD server ( and lots of XP boxes ).I didn't have any issues joining the domain/active directory.Forgive me if this advice is covered by your manual joining the domain attempt, but have you tried:Right click my computer -> properties, Advanced system settings -> computer name -> change move the radio button to domain, type in the name of the domain, put in an admin username and password when prompted, and restart.Things that I've found to cause problems in the past when joining domains:VPN, you used to be able to join a domain over VPNs in the past but a good few months ago that stopped. ( I think because of a MS patch . Maybe it was considered a security vulnerability? ) I build quite a few PC for other companies and used to be able to remote login to the servers, setup user accounts and passwords, VPN in on the new PC, join the new PC to the domain and setup the users' account locally but alas no more :(Are you VPNing in to the AD or are you on a local network?Another thing that can cause issues is DNS. The behind the scenes techno stuff to do with domains - the ldap service I think, needs to be available and if the DNS isn't resolving the service to the 2003 server that can cause problems. Is the DNS service for the win7 box that can't join the domain provided by the 2003 server or something else?I've found that all sorts of things always seem to run a lot more smoothly when an AD server is running the DNS for it's desktops.Re-reading your original post I see the DNS settings are the same as the XP machines but my question still stands. Is the 2003 server providing the DNS?Actually probably not if you are running static IPs. Therein may lie your problem :) Try enabling DHCP and DNS on the server ( even if only temporary ), setup a range, serve the 2003 server as the DNS server in scope options, and get the win7 box getting its IP address and DNS from the server, that could do it for you. Don't forget to setup the DNS forwarders if you leave the DHCP/DNS turned on.
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2010 1:25pm

Hi Bill,I am using IPv4 addresses exclusively. IPv6 has been disabled on all NICs.I haven't done a nslookup yet; thanks for the heads up.I also haven't PING'ed the server from either of the two new workstations, though since I can see the server (and other systems) when I view network computers from the workstation, I don't think that will be a problem.My client -- a Dentist -- installed and started up the two workstations (as Home Premium systems) before they were physically connected to the network infrastructure. Being 'helpful' I think he tried to set them up on the domain without having all of the pieces in place. When I try to place them on the domain, the Wizard says that they are already on a domain called HygienePC1 which is the name of the workstation itself. It is possible that both systems are in the Homegroup and not able to be moved to the domain, but I'm not sure. At any rate, I think I may need to get some on-site help or a book that explains the ins and outs of Windows 7 Pro.Thaks,Tom
January 26th, 2010 2:43am

Hi Hugh,Yes, I've tried to add the systems to the domain as you described, but still get the AD DC error. The error codes point to the DNS settings being incorrect or missing but they are correct.VPN is not an issue with this network.Idap service could be a problem but I'm not sure how to resolve it right now. The DNS service is being provided by the server.I may have to enable the server's DHCP function and go to dynamic IPs but static IPs have not been a problem with XP Pro systems already on the network. Active Directory with the XP systems works fine.Thanks,Tom
Free Windows Admin Tool Kit Click here and download it now
January 26th, 2010 2:51am

Did you get this resolved, I have the same issue now.
May 1st, 2011 9:26am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics