Clients can't communicate with AD once joined.

  • Thread starter Thread starter Graham Palfreyman
  • Start date Start date
G

Graham Palfreyman

Hiya,

I have a AD client which has 10 machines working happily with it. I built 4
new servers yesterday and they joined the domain fine. Problem is when i try
to logon using the domain for authentication it takes about 20 minutes to
logon and in the event log there are lots of errors about not being able to
find the domain controller, group policy won't run because it can't find the
domain controller etc etc..... When the machines are in a workgroup they
can ping and communicate using IP and FQDN. It will also join the domain
quite happily. As soon as those machines reboot and you try to login via the
domain it alls goes wrong. Eventually when you've "logged in" the machine
will not ping the DC either IP of FQDN. Very ODD

Oh just to complicate matters some more the 1st machine i put on the domain
works fine. The other 3 do what ive explained.

Does licensing cause these issues?

If anyone can spread some light on this i would be grateful as i've never
seen anything like this.

Gray
 
This is most likely a dns issue. Do you have your isp defined in your
client dns? Only your AD dns server should be defined on your clients and
the AD dns server should forward requests to your isp.

Licensing has nothing to do with it.

--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup

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



Worked out what was wrong. Default gateway was set incorrectly. Never mind
all is working now anyway.



Gray
 
Back
Top