Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Ok, here is the problem that I am having. I just got a new dell and as with every new machine I get, format and reload. Now I am trying to add it to my domain and it's not happening. Here are the details:
NOT running a DNS server.
DHCP server IS leasing an address to client machine.
I've changed CAT5 cables thinking I had a bad one.
I've tried configuring LMHOSTS with no success.
I've visited Microsoft about this problem with no help since I'm not running a DNS server.
The kicker is that I've had this problem with one other machine. When I reloaded that machine, the NIC was recognized during setup. When this happened the machine joined the domain with no problem. This new computer has an onboard NIC that wasn't recognized during setup. I tried Windows XP Pro on it and reluctantly it joined the domain, but took 10 minutes to logon. (That was with the bad CAT5 cable).
If anyone can shed light on this, I would much appreciate it.
Ok, found out the problem. My firewall software. I'm running ZoneAlarm. I read on Microsoft, that may happen due to port 389 not being open. Anyone know how to fix this?
0 
I figured it out. I had not put my local network in the trusted zone of my firewall. I didn't think that I needed DNS if I wasn't hosting my own web domain.
0
Well, if you have domain set up as you mentioned earlier then you must have Active Directory installed on one of your server computer. In order to use AD you must have DNS installed on the same machine.
0
You do not have to have DNS set up to have a domain running. If you do not want to set it up. don't. If you click the checkbox in Zonealarm to show all warnings and so forth, you can see when it is blocking your local network addresses. then you can just click to allow access and your fine.
0
Luvchild_143, I totally disagree with you.
DNS is absolutely vital for Active Directory operation. Without a correctly configured DNS, active directory won't be able to locate its resources (domain controllers, global catalog serves and the like).PhArAoH
0
Pharaoh is correct, luvchild is wrong. DNS is absolutely required for a Windows 2000 domain.
0
Yes. That's what I said! DNS is absolutely required for a Windows 2000 domain. You don't have AD without a domain. You don't have a domain without AD. This is not something that you have an opinion on - it is a fact. Period. DNS IS REQUIRED FOR A WINDOWS 2000 ACTIVE DIRECTORY DOMAIN. Got it?
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
