Jerblaine
asked on
DNS problems: Non existent domain
Ok here is the deal.
I have a server running windows 2003 server. This server is configged to do everything: DNS, DGCP, EMAIL etc.
I have a workgroup in the office. I am trying to put all the puters from the workgroup into the new domain that i created on the wind 2003 server computer.
I can ping the IP address of the win2003 server from another puter on the workgroup but i cannot ping it by name.
I have researched for hours. I believe my DNS server is configged correctly all the way down to the PTR in the reverse lookup zone. I am not toally sure about my forward lookup zones though. Could a problem in there be causing this?
I have done NSLOOKUP and it still says domain not found. BUT it does find the IP address. It just leaves it blank by server name........then at other times it says it cannot find server name.
It looks like my server can be found by the workgroup by IP but not be name.
Help?
I have a server running windows 2003 server. This server is configged to do everything: DNS, DGCP, EMAIL etc.
I have a workgroup in the office. I am trying to put all the puters from the workgroup into the new domain that i created on the wind 2003 server computer.
I can ping the IP address of the win2003 server from another puter on the workgroup but i cannot ping it by name.
I have researched for hours. I believe my DNS server is configged correctly all the way down to the PTR in the reverse lookup zone. I am not toally sure about my forward lookup zones though. Could a problem in there be causing this?
I have done NSLOOKUP and it still says domain not found. BUT it does find the IP address. It just leaves it blank by server name........then at other times it says it cannot find server name.
It looks like my server can be found by the workgroup by IP but not be name.
Help?
The first thing to check is DNS. Make sure that the server only points to *itself* in the TCP/IP Settings. Make sure each client only points to the server for DNS.
selected zone is Windows 2000 Operating System.....and you are saying the win2003 server installed....:)
Ok also download the netdiag.exe utility from microsoft and cehck your DNS server is working fine and as per j0rdan: said configure primary DNS address on server and workstation clients should be Local IP address of the windows server...and ISP dns adress in forwarders tab of the DNS server console.
Regards,
VIjay Kadadi
Ok also download the netdiag.exe utility from microsoft and cehck your DNS server is working fine and as per j0rdan: said configure primary DNS address on server and workstation clients should be Local IP address of the windows server...and ISP dns adress in forwarders tab of the DNS server console.
Regards,
VIjay Kadadi
ASKER
Well I downloaded netdiag.exe then when I went to run it, it tells me
the procedure entry point Dnsgetprimarydomainname_ut f8 could not be located in the dynamic link library DNSAPI.dll
so this could be related to why the other puters in the workgroup cannot see the domain.
So now I need to correct this problem so that I can run netdiag.exe right?
Also for the IP address of the ISP's DNS server, could the gateway router be acting as a dns server as well? If not then I need to get the IP address for the ISP's DNS server so that I can put it in the forwarders tab under properties in the DNS console.
How does this sound so far?
the procedure entry point Dnsgetprimarydomainname_ut
so this could be related to why the other puters in the workgroup cannot see the domain.
So now I need to correct this problem so that I can run netdiag.exe right?
Also for the IP address of the ISP's DNS server, could the gateway router be acting as a dns server as well? If not then I need to get the IP address for the ISP's DNS server so that I can put it in the forwarders tab under properties in the DNS console.
How does this sound so far?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well it ended up being the firewall. It needed to be turned off on the windows server 2003 machine in order for the xp clients to even see it and join it.