On Nov 17, 2005, at 1:56 PM, Michael Bumbalough wrote:
John Buell <email@hidden> on Thursday, November 17, 2005 at
2:16 PM
-0500 wrote:
On 11/17/05 11:46 AM, "Phillip Burk" <email@hidden> wrote:
<snip>
I'd set a preferred DC and see how that goes. Sometimes if DNS
can't
return the DC address you'll have this issue.
By name or by IP address?
If you are going to do this, I would use the IP address. It could be
that the AD domain's DNS servers aren't returning the correct
information
to the client. Although, you probably wouldn't have been able to
bind to
AD if it wasn't working on some level. In any case, the IP address
will
eliminate the DNS server from the equation.
I'd recommend both ways. First by FQDN simply because that's how we
do it here. Then try via IP address. The reason for FQDN is that
someday your DC will be upgraded and it's IP address may change. Of
course if DNS is the issue that's something else entirely...
Any other networking issues? Duplex mismatch can cause problems but
that's admittedly a reach.
The iMac is on wireless, but we've got 20 PC laptops in a wireless
cart in
the same location, and they log into the domain.
