Scott,
What Server Operating System are you talking about? Since this is a WIN2000
Active Directory news group I would 'assume' that you are running a WIN2000
AD environment.
And, what is the client OS / are the client OSes? Clearly you are talking
about WINNT 4.0 or WIN2000 or WINXP ( or some combination thereof ).
I would start with DNS. This is most probably the issue. Open up your DNS
MMC and look at the FLZ ( forward lookup zone ). Does it have the four
subfolders ( _msdcs, _tcp, _udp and _sites )? If it does not, then try
opening up a command prompt and doing a 'net stop netlogon', followed by an
'ipconfig /flushdns' and then an 'ipconfig /registerdns' and finally a 'net
start netlogon'. Or, if you have the Support Tools installed you can run a
'netdiag /fix'.
Also, make sure that the zone that you have ( something like
'yourdomain.com' ) is spelled correctly. It can very well be that you have
domain with the DNS Name of 'yourdomain.com' while - for some reason - your
DNS Zone is 'yourdomaine.com'. This could also be a problem.
Make sure that all of your internal clients are pointing only to the
internal DNS Server that is responsible for your domain......There is only
one place for the IP Address(es) of your ISP's DNS Server(s) - in the
Forwarder's tab! Make sure that DHCP is handing out the correct
information. If your internal clients are pointing to an external DNS
Server ( such as your ISP ) then you will have a whole bunch of weird
problems....
--
Cary W. Shultz
Roanoke, VA 24012
Microsoft Active Directory MVP
http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com