Connect Windows 7 to 2003 Domain

So in school we are doing some networking, and I'm a total geek so like to go all out and test it in my own time and fiddle around. I decided to setup my network with 2 servers, 1 of which is the DC and hosts Active Directory and the local web site I set up, the other is a file server. My laptop had Windows 7 Professional on it, and every time I tried to connect to my domain, it would give me an array of error messages, on another Windows XP computer, I put in the details it asked for, and it connected to the domain instantly. I then decided to just throw Windows XP on my laptop.

Now thinking through, I don't know if I want such an out-dated OS. I've been looking around on Google for information about it, but nothing solid has been found. I questioned about what the school used, but then I realized they ran 2008 - They have XP, Vista, and 7 laptops/desktops.

Could anyone help me through this? Is this a server issue, or client issue? Should I just install 2008? It seems this is more compatible with 7.

Thanks!

 

We need much more info than what you are giving...what are the error messages? What version of Sever 2003? RTM, SP1, SP2, R2? Are the machine assign IP addresses or Static? Is the Windows 7 machine resolving DNS to the DC?

Win 7 supports joining Windows 2003 Domains...

 

It's Windows Server 2003 Enterprise SP2. There are different messages I get, one of which is that it cannot resolve the DNS. IP addresses are static. To my knowledge the client Win 7 is not resolving the DNS to the DC. I'm in the middle of reinstalling Windows 7 on my laptop, so will try again soon and give some specifics, though no doubt when I try it, it will work first shot.

 

I guess it doesn't really matter, was just curious and having a play around.

 

What method are you using to join the domain?

You should be able to do it if the w2k3 server is up to date with all the updates it needs.

If you go to "Control Panel > System", then look at the "Computer name, domain, and workgroup settings". Click on where it says "Change settings", then go to "Network ID" button. You will need to enter the information for you domain.

If that doesn't work, it can get complicated.

Remember to first install updates to the servers, both servers.

 

I tried both ways, using the Network ID, and the other way. Neither worked, unfortunately. I think I might just leave it as is and get some more laptops to play around with on the domain.

 

I have several W7 computers joined to our W2K3 server AD at work. If you cannot connect to the domain because of DNS issues, first make sure that DNS is properly configured on the W2K3 domain controller. If it is a DNS server and it should be if you are hosting AD, it will work just fine. If you setup DNS during AD installation, it should be working fine.

On the W7 client computer, statically set the DNS server address to the DNS W2K3 server hosting your AD. Then try to join the domain. If no luck, make sure you can ping the server. Still no luck? Try putting the .local extension after the domain name when you join.

 

Also, you can setup your domain controller to be a DHCP server and set your clients to DHCP as well. This will produce the same effect as setting the static DNS server address on the clients. DHCP will actually work better because it will eliminate any possible mistakes you have made in the address allocations. DHCP is real easy to setup and should fix your problem immediately.

 

I'm a little confused as to why this isn't working, as I setup DNS and DHCP when I installed AD. When I just put in the domain, joelkrause, it asks me for the credentials and I put them in and it says that it cannot resolve the DNS server. Though when I put in, joelkrause.local, it cannot find AD.

DHCP is installed and configured on the server. I just don't know why it would work first shot in Windows XP, and not Windows 7.

 

From the W7 client, can you ping the DNS name of the server? If not, make sure you can ping it via IP.

If you can only ping via IP, set the DNS server IP address in your static IP settings on the W7 client.

Make sure that the domain controller/DNS server is setup with a static IP and that the DNS server address on the server is pointing to itself. Meaning, you set the static IP address settings on the DNS server with it's own IP address in the DNS server box. This ensures that your DNS server will handle DNS requests properly.

 

Are you using a flat namespace? I saw you domain name joelkrause, did you add a domain suffix like .local, .com, etc. ? If you used a TLD such as com or net, do you own that name? I've added many Win 7 machines to a Server 03 domain without issue.

On the Win 7 machine when you run nslookup from an elevated cmd prompt does it resolve your domain?

Also is your DC resolving DNS to itself, is it self aware? Do you have a home router that is also acting as a DNS server? Most home routers do...

It would be helpful to see the IP Stacks of both the DC and the Win 7 machine...

 

You may try turning on WINS. Do you have the DHCP options set up properly in DHCP?

 

Win 7 doesn't need WINS, in fact Server 2008 added support for Flat Namespaces to kill off the need for WINS...SAMBA Hosts are really the only reason to have WINS, unless you have a SERVICE LOCATOR POINT in SCCM 2007....

 

He's using 2003. I thought maybe it would help him get it working. I already know it's going away.

 

Sorry Makeitso I wasn't trying to sound like a jerk (I should of re-read for tone). WINS is a good old technology but isn't used in a AD Query...when you do a domain lookup it Queries DNS looking for 3 SRV Records for the Domain: Kerboros, LDAP and Global Catalog...

When I teach AD I use the saying to start the class...

No DNS
No AD

Know DNS
Know AD

 

Are you a teacher? I don't really see you post a lot here, but your answer is right on the spot.

 

Oh sorry guys! Forgot about this thread :/

My server's sort of hit rock bottom and I will have to replace them. I'm thinking when I do, I won't have a domain. Just a workgroup. Much easier, IMO. The domain was just a test.

Anyway, thanks for all your help! Much appreciated.

 

Merlin,

I'm a long time IT Trainer and Consultant mainly now working on Virtualization and Private Cloud Datacenters. I spend most of my time at TabletPc Review (sister site) but I'm active here as well (Lenovo, Toshiba).

Joel,

If you are planning after college to go into IT fulltime AD is a good skill to have. I when I was learning AD I ran a full Windows Domain at home with multiple servers. Now I have one high end (for it's day) workstation running Hyper-V for my test and learning environment. I use Windows 7 Home Group for sharing....

 

Thanks for the advice! I'm hoping to go into IT full time, hopefully doing system administration. I might actually setup a domain, get to know the interface of AD, etc. It's fun to do. I'll sort it out when I get my new computers.

 

OK. Well remember for the next time you setup a domain....If you can't connect to the domain to join a client computer, verify your network connectivity and then manually set your client's DNS address to that of the domain controller server. If your network connectivity is good, it will work. Most of the problems you will find with a domain environment are DNS related.

If you are interested in a home server/client based network then check out Server 2008 Home Edition. It's better suited for home environments.

 

I see that you are IT trainer and consultant. I am in the same field as you do, but I am not a trainer. I mostly work on network side. It has been nice to know you though. I have to agree with you that AD technology is a must for IT world, but I would go with Server 2008R2 instead of Sever 2003. You make a wise choice for using Hyper-V instead of VMWare.

I use Hyper-V for my environment and it works out really well.

 

Happy to make your acquaintance Merlin My specialty is Hyper-V and System Center, I've been working with Microsoft on developing training on Private Cloud Architecture and implementation. It's a lot of fun...

AD seems to be the great unifier even VMWare uses it

 

Why do you say that? Out of curiosity.

 

I say it because from a TCO and ROI prospective Hyper-V offers better value, from an IT staffing POV I can get any Windows Admin in front of it and have them administering it in under a half hour...