On Wed, 2003-04-30 at 00:29, John Scott wrote:
A DNS entry for what? Itself? The PDC? Or the PDC looking for an entry for the connecting machine? I don't use DNS for internal network resolution. I use the hosts/lmhosts files so I don't understand how DNS would apply. Any theories?
Well the error message you quoted said that either the domain could not be contacted or no machine account could be found - since you have managed to add the machine to the domain that would imply that there is a machine account; it would also imply that when you did add the machine to the domain the Pc could find the domain, so have you changed the firewall setup since you added the machine to the domain? When i had the error message and looked it up on the MSFT site is said that this was caused by a missing DNS entry. I was not using DNS either. But what it shows is that there is a name resolution problem - either hosts/lmhosts or on the WINS server if you have one
Are you suggesting I try shutting down the firewall on the PDC?
Yes - it is a matter of finding out where the problem really lies - if you shut down the firewall on the PDC and you can log on to the domain then the problem is with the firewall configuration. If this does not help then the problem lies elsewhere.
Shutting Zone Alarm didn't help. That makes sense though since configured ZA to view my internal network as a trusted zone.
Fine, then the problem is not with the ZA firewall.
-- Tim <tim@pipandtim.com>