2000 server DNS problem?

[bill s]

I set up my first network with server 2k after taking courses in 2003.
Everything seemed fine until I upgraded to "native mode". This done because I
have 32 clients all running XP.
I cannot get anymore computers on the domain. I keep gettting "cannot find
domain name".
I can ping the server by IP
I can ping the server by name
However NSlookup returns the server IP but says it cannot find server name.
You probably need way more info but can you direct me in some way from here?

 

[Paul Bergson]

Are your xp clients and your dc all pointing to the same dns server?

++++++++++++++++++++

From your dc

Try running netdiag and dcdiag. Look for fail, error and warning errors.

If you don't have the tools installed load them from your install disk.

d:\i386\adminpak.msi (Server tools for remote management of servers)
d:\support\tools\setup.exe (Server Utilities)

Copy the following to a cmd file and run look for error, fail and warn
within the reports. Post any errors you can't figure out. make sure you
modify DC_Name to the name of a dc in your domain.

@echo off

c:
cd \
cd "program files\support tools"

del c:\dcdiag.log
dcdiag /e /c /v /sC_Name /f:c:\dcdiag.log
start c:\dcdiag.log

netdiag.exe /v > c:\netdiag.log
start c:\netdiag.log


--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[bill s]

Are your xp clients and your dc all pointing to the same dns server?

++++++++++++++++++++

From your dc

Try running netdiag and dcdiag. Look for fail, error and warning errors.

If you don't have the tools installed load them from your install disk.

d:\i386\adminpak.msi (Server tools for remote management of servers)
d:\support\tools\setup.exe (Server Utilities)

Copy the following to a cmd file and run look for error, fail and warn
within the reports. Post any errors you can't figure out. make sure you
modify DC_Name to the name of a dc in your domain.

@echo off

c:
cd \
cd "program files\support tools"

del c:\dcdiag.log
dcdiag /e /c /v /sC_Name /f:c:\dcdiag.log
start c:\dcdiag.log

netdiag.exe /v > c:\netdiag.log
start c:\netdiag.log

I set up my first network with server 2k after taking courses in 2003.
Everything seemed fine until I upgraded to "native mode". This done

[quoted text clipped - 8 lines]

You probably need way more info but can you direct me in some way from
here?

 

[bill s]

Are your xp clients and your dc all pointing to the same dns server?

++++++++++++++++++++

From your dc

Try running netdiag and dcdiag. Look for fail, error and warning errors.

If you don't have the tools installed load them from your install disk.

d:\i386\adminpak.msi (Server tools for remote management of servers)
d:\support\tools\setup.exe (Server Utilities)

Copy the following to a cmd file and run look for error, fail and warn
within the reports. Post any errors you can't figure out. make sure you
modify DC_Name to the name of a dc in your domain.

@echo off

c:
cd \
cd "program files\support tools"

del c:\dcdiag.log
dcdiag /e /c /v /sC_Name /f:c:\dcdiag.log
start c:\dcdiag.log

netdiag.exe /v > c:\netdiag.log
start c:\netdiag.log

I set up my first network with server 2k after taking courses in 2003.
Everything seemed fine until I upgraded to "native mode". This done

[quoted text clipped - 8 lines]

You probably need way more info but can you direct me in some way from
here?

 

[bill s]

Are your xp clients and your dc all pointing to the same dns server?

[quoted text clipped - 31 lines]

Paul
yes..all the workstations point to the IP of the server.
I will try your cmd line syntax..
Found out that the place use to sponser their own website but farmed it out
before I came in.
The IP domain name and the internal domain are the same name, would this
matter?
I have not implemented IIS.

 

[bill s]

Are your xp clients and your dc all pointing to the same dns server?

[quoted text clipped - 31 lines]

You probably need way more info but can you direct me in some way from
here?

Paul
yes..all the workstations point to the IP of the server.
I will try your cmd line syntax..
Found out that the place use to sponser their own website but farmed it out
before I came in.
The IP domain name and the internal domain are the same name, would this
matter?
I have not implemented IIS.

Oh yeah...................the DC is the only server on the network

 

[Paul Bergson]

We use the same name internally and externally we just forward external
requests to our isp.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

Are your xp clients and your dc all pointing to the same dns server?

[quoted text clipped - 31 lines]

You probably need way more info but can you direct me in some way from
here?

Paul
yes..all the workstations point to the IP of the server.
I will try your cmd line syntax..
Found out that the place use to sponser their own website but farmed it
out
before I came in.
The IP domain name and the internal domain are the same name, would this
matter?
I have not implemented IIS.

 

[Steven Platt]

Once upon a time I had a problem with DNS. Lots of problems, actually. I
was having problems joining computers to the domain, also. I followed some
KB articles and got some great help from Paul Williams on these newsgroups
and got it solved. The problem I ended up having was that I didn't have the
4 special folders _msdcs, _sites, _tcp, _udp. These two links ended up
fixing it.

http://support.microsoft.com/?kbid=260371
http://www.microsoft.com/windows2000/dns/tshoot/

I hope you get it worked out. I know how DNS problems can be. It was very
frustrating to not be able to add a computer to the domain. Good luck.

-Steven-