asked on
Connect Active Directory domain through routers
Hello All,
we are new to active directory and are trying to set up a domain to control our users. We have set up the AD:
- when connecting a PC on the same LAN (IP and switch) as the server, we can authenticate on the domaine.
- when we connect the PC on a different LAN (different IP addresses and switch) but connected on a different interface of the same router as the server, it also works.
- when we connect on a different LAN coming from a different router, we cannot connect the AD but we can ping the server.
So my questions are:
1- Are we obliged to use netbios over TCP/IP to access a domain controller ? can we just use TCP/IP ?
2- Can we connect a domain controller through routers ?
Thanks
we are new to active directory and are trying to set up a domain to control our users. We have set up the AD:
- when connecting a PC on the same LAN (IP and switch) as the server, we can authenticate on the domaine.
- when we connect the PC on a different LAN (different IP addresses and switch) but connected on a different interface of the same router as the server, it also works.
- when we connect on a different LAN coming from a different router, we cannot connect the AD but we can ping the server.
So my questions are:
1- Are we obliged to use netbios over TCP/IP to access a domain controller ? can we just use TCP/IP ?
2- Can we connect a domain controller through routers ?
Thanks
Windows Server 2003Active Directory
Last Comment
lemaitre75
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Since he was describing connectivity issues, I assume that the OP has some blocking ACLs configured.
ASKER
Dear All,
it's pure routing on cisco routers, without ACLs or FW so that's why we are concerned why it's not working ?
Question 1 was just to confirm if we need to enable Netbios over TCP/IP in the TCP/IP settings, because when disabling that, we were not able to connect the domain.
so i guess it may be a DNS problem, but what can be the problem here ? but i don't understand why since we de not refer to the server name, or i'm wrong ?
thanks
it's pure routing on cisco routers, without ACLs or FW so that's why we are concerned why it's not working ?
Question 1 was just to confirm if we need to enable Netbios over TCP/IP in the TCP/IP settings, because when disabling that, we were not able to connect the domain.
so i guess it may be a DNS problem, but what can be the problem here ? but i don't understand why since we de not refer to the server name, or i'm wrong ?
thanks
Active Directory lives and dies by DNS; if your client computers and other domain controllers cannot resolve the FQDN and SRV records of a domain controller in question, all aspects of AD (authentication, replication, domain joins, etc.) will fail. If you have DNS issues they will cause AD failures even with no router ACLs in place.
ASKER
Dear All,
i think we need to restart our installation from the beginning and follow a good procedure.
We are using our ISP DNS server
Do you know any site that have a good documentation on how to install and maintain a windows2003 AD
Finally, when choosing the domain name, is it the server name or just the domain, for example if my domain is mydomain.com and the server is host123, when configuring the domain, are we going to enter mydomain.com or host123.mydomain.com ?
thanks
i think we need to restart our installation from the beginning and follow a good procedure.
We are using our ISP DNS server
Do you know any site that have a good documentation on how to install and maintain a windows2003 AD
Finally, when choosing the domain name, is it the server name or just the domain, for example if my domain is mydomain.com and the server is host123, when configuring the domain, are we going to enter mydomain.com or host123.mydomain.com ?
thanks
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Just to repeat what has already been said, DNS is the backbone of a Windows domain - without a proper understanding of it you would be well advised to get the advice and services of someone who does. A correct initial installation is fundamental to a stable server and network.
While everything is available as guides and howto's from Microsoft, you need to ensure that you understand both the procedures and the technology before embarking on an AD install. While it is possible to follow a guide without understanding it, in this case I would suggest it is highly inadvisable.
While everything is available as guides and howto's from Microsoft, you need to ensure that you understand both the procedures and the technology before embarking on an AD install. While it is possible to follow a guide without understanding it, in this case I would suggest it is highly inadvisable.
ASKER
i think we will go with a consultant for the initial deployment
thanks all
thanks all
ASKER
i did not get the solution but i got enough advices to success in the deployment
http://www.microsoft.com/downloadS/details.aspx?familyid=C2EF3846-43F0-4CAF-9767-A9166368434E&displaylang=en