Forum Home
Press F1
Thread ID: 64153	2005-12-05 06:41:00	Windows 2003 Primary Domain Controller	dameek (8235)	Press F1

Post ID	Timestamp	Content	User
410397	2005-12-05 06:41:00	I am having an issue connecting my winxp pro clients to my domain . Current set up is: Cable conneciton to router with static wan connection and router providing dhcp to my server and clients . This is where my first question arises . As far as I am aware, my server requires a static ip address . Now does this mean that I need to have my outside ip address (the one provided by my ISP) configured as the address of my server or can this be a private ip address set by my router (although set as static, ie . It doesn't change)? So far I have tried both scenarios and even took the router out of the equation and used a standard switch . The only problem with this is that both the clients are laptops and require the wireless connection provided by the router . My second question is do I need to have my server configured as a DNS server or can I just use the ones provided by my ISP . The reasons for these questions are because I have tried configuring the primary domain controller as advised previously and I have installed Active Directory and all appears ok on the server but when trying to connect client laptops to the domain I get an error that the domain controller cannot be located . I have also tried setting the wan ip address on the server and connecting the wan to the lan port on the router and disabling all services on the router and this seemed to work as far as internet access goes on the server but then I could not seem to configure the dhcp server on the server . It said that the service was running but none of the clients seemed to be able to pick up an ip address . I have played round with this for the past year or so and have had no luck and just had the network running on a workgroup which was fine for most things but as it the network has grown and more servers/services had been added, including ms exchange server this is becoming a necessity . I would be extremely greatful if anyone could offer any assistance could be offered . Cheers	dameek (8235)
410398	2005-12-05 20:39:00	I am having an issue connecting my winxp pro clients to my domain . Current set up is: Cable conneciton to router with static wan connection and router providing dhcp to my server and clients . This is where my first question arises . As far as I am aware, my server requires a static ip address . Now does this mean that I need to have my outside ip address (the one provided by my ISP) configured as the address of my server or can this be a private ip address set by my router (although set as static, ie . It doesn't change)? Best way would be to disable DHCP on router and use server for DHCP . Give the server a static IP address that is in the range that the router is using . (NOT the one provided by your ISP! Use private one) Set appropriate subnet mask . Set the default gateway as the IP of the router . Set primary DNS server as the same IP you gave the server . Now setup the server as DHCP server as normal but once that is done goto DHCP under Administrative Tools and drill down to Scope Options . In here you should see a few items listed on the right like DNS server and DNS Domain name (if you have setup DNS on the server) . Right-click on Scope Options and select Configure Options . Select Router from the list and put in the IP of your router . Now configure workstations for DHCP and check that they are getting an IP address, DNS server and Default gateway from the server . If they are then they should be able to connect to the domain . So far I have tried both scenarios and even took the router out of the equation and used a standard switch . The only problem with this is that both the clients are laptops and require the wireless connection provided by the router . My second question is do I need to have my server configured as a DNS server or can I just use the ones provided by my ISP . Yes, pretty sure a Domain Controller has to be a DNS server . Once you have set up the server as a DNS server go into DNS under Administrative tools . Right-click on your server name under DNS on the left side of the screen and goto Properties - Forwarders tab . In the box half way down that tab put in the routers IP address and click add . This will make the server look to the internet for anything that is not found on the local network .	CYaBro (73)
410399	2005-12-06 04:50:00	Thanks heaps for your help . You helped answer two of the questions I have been trying to find answers for . I have now managed to sucessfully set up dhcp and dns servers which appear to be working for both my clients now . Unfortunately though they still don't appear to be able to contact the primary domain controller when trying to log them onto the domain . I have valid user and computer accounts in AD both added to admin groups but for some reason still do not want to log on . Any thoughts would be extremely appreciated . Thanks again	dameek (8235)
410400	2005-12-06 05:25:00	Below is the error received when trying to put client on the domain: Note: This information is intended for a network administrator . If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag . txt . The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain MeekNet . local: The error was: "This operation returned because the timeout period expired . " (error code 0x000005B4 ERROR_TIMEOUT) The DNS servers used by this computer for name resolution are not responding . This computer is configured to use DNS servers with the following IP addresses:	dameek (8235)
410401	2005-12-06 08:28:00	The error seems to be that it is looking for "_ldap._tcp.dc._msdcs.<domain name>" I can't seem to locate this file anywhere although not entirely sure where I should be looking. I managed to find _ldap file in dns under the tcp folders under each site but that was it. Any thoughts would be appreciated. Thanks	dameek (8235)
410402	2005-12-06 19:47:00	Sounds like the DNS is not working properly on the server. If the clients DHCP info is correct (can check by running ipconfig /all from a command prompt), try pinging the server name and also a website and see what happens. You should get a response from each with an IP address. That will tell you of DNS is working on the server or not. Also try pinging a workstation name and a website on the server.	CYaBro (73)
410403	2005-12-06 22:26:00	Hello again, You are correct . I can ping client pc's and urls from server and I can ping the server from clients but not external urls . I did not actually think to check this as I would have thought if I could type the url in my browser on the client and it resolves the dns name to the correct ip address then it would mean that the dns server is doing its job but obviously not . If I run ipconfig/all on the client pc is does show my server ip address as being the dns server and dhcp server . DHCP seems to be running perfectly . All clients have picked up the correct ip addresses specified on the server . Your help is very much appreciated .	dameek (8235)
410404	2005-12-06 22:46:00	One more thought about this . Could the reason that I can't ping external websites from my clients be because they go through a proxy server?	dameek (8235)
410405	2005-12-07 00:01:00	Don't think a proxy server matters. The clients have the server IP address as the DNS server so all DNS queries go to it and then the server will translate into an IP address if it knows what it is otherwise it will forward it onto the router. Try changing the Forwarder IP address, that I told you to set in DNS settings on the server, to the DNS servers of your ISP.	CYaBro (73)
410406	2005-12-07 06:25:00	Sorry to be a pain but that doesn't seem to have made any difference. Still unable to ping external urls from clients.	dameek (8235)
1 2