wademi
asked on
Error joining a computer to a domain “A domain controller could not be contacted”
I am trying to join my computer to a domain in my small office network. The computer is plugged into a router that is connected to a network port. All the other computers that are in the domain have a 10.10.10.1-24 address. The computer that I am connected to has a 192.168.200.39 address so I am assuming that the router is assigning the IP address to the computer. Its seems as if the Windows 2008 serevr/DHCP server cannot assign the computer connected to router an IP address. I have no other available ports at the location where I am at.
I keep getting a “A domain controller could not be contacted” error when I try to join the domain.
Is there a workaround for the above scenario?
Do I absolutely have to plug my computer in an existing network port for it to join my domain?
I keep getting a “A domain controller could not be contacted” error when I try to join the domain.
Is there a workaround for the above scenario?
Do I absolutely have to plug my computer in an existing network port for it to join my domain?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
That's how you need to turn off DHCP but you also need to plug the router into the network from one of its LAN ports so it becomes and access point instead of a router. It actually IS routing traffic if it's handing out addresses on that subnet.
ASKER
Thanks renazonse:. One last question. If i connect my network lan port to the lan port on th router How would I find out the IP address that was assigned to the router.
statically assign the address to the router when you turn off DHCP so you don't have to worry about it.
What you are trying to do is to add another switch to the existing network. Here is the issue when you have another router on the network you need to allow the router to lease an IP scheme that has your DNS servers listed. What the current issue is that the router is giving out DNS servers that are most likely not your internal DNS servers. You need to get into the router config to see what your current settings are. Usually you can go to the default gateway of the network the router is running on you can do an ipconfig /all on one of the clients to see what the default gateway is.
What I would is put the Router in Wireless AP Mode which make the router into an Access Point not a router
What I would is put the Router in Wireless AP Mode which make the router into an Access Point not a router
ASKER
The router is a simple verizon router: Model 7501(Just like a home router)
I can ping all the other workstations.
The 192.168.200 is not defined in the sites service.
renazonse: Should I just log in to then router administration and turn off DHCP.