Very frustrated...ongoing domain issue

[A]

I have looked high and low and still cannot figure this
one out. My gut feeling is that this issue is DNS
related....okay here's what going on. New win2k adv srv
build. Implimented AD no issues, configured DNS...no
issues until client computer start to join the domain.
Mix win2k and xp pro machines. One 2k machine logs into
the domain and everything seems okay until a reboot
occurs. This machine will lose all of its mapped drives;
event viewer gives and an eventID 1000. I looked it up
and it says to point the DNS to the internal DC, which I
already did. The XP machine does not need a reboot to
get kicked off the domain, it just happens with the same
eventID 1000. I have the ISP's DNS servers on the
servers dns forwarders. Here is the kicker; if the
client machines have the internal DNS server ip on their
stack, they cannot get pop3 email. When the ISP's dns
server is in the stack, then cannot get to the domain.

What am I overlooking with this one? Any insight is
greatly appreciated. TIA

A

 

[Enkidu]

I have looked high and low and still cannot figure this
one out. My gut feeling is that this issue is DNS
related....okay here's what going on. New win2k adv srv
build. Implimented AD no issues, configured DNS...no
issues until client computer start to join the domain.
Mix win2k and xp pro machines. One 2k machine logs into
the domain and everything seems okay until a reboot
occurs. This machine will lose all of its mapped drives;
event viewer gives and an eventID 1000. I looked it up
and it says to point the DNS to the internal DC, which I
already did. The XP machine does not need a reboot to
get kicked off the domain, it just happens with the same
eventID 1000. I have the ISP's DNS servers on the
servers dns forwarders. Here is the kicker; if the
client machines have the internal DNS server ip on their
stack, they cannot get pop3 email. When the ISP's dns
server is in the stack, then cannot get to the domain.

What am I overlooking with this one? Any insight is
greatly appreciated. TIA

The internal clients should be set to have *only* the internal DNS IPs
in their configuration. The DNS servers should have their DNS setting
set to their *own* IPs. (You don't say what they are set to). The DNS
servers should have forwarders to the ISPs DNS server IPs. That should
work.

I suggest that you do an ipconfig /all on a sample client and a sample
server and post the results here.

Cheers,

Cliff

{MVP Directory Services}

 

[Guest]

-----Original Message-----

The internal clients should be set to have *only* the internal DNS IPs
in their configuration. The DNS servers should have their DNS setting
set to their *own* IPs. (You don't say what they are set to). The DNS
servers should have forwarders to the ISPs DNS server IPs. That should
work.

I suggest that you do an ipconfig /all on a sample client and a sample
server and post the results here.

Cheers,

Cliff

{MVP Directory Services}
.

Thank you for responding
I have tried different configurations with the client IP
stack. I've put the ISP's DNS only, the internal DNS
only, etc... I understand that having only the DNS for
the internal server should work, but as I stated before,
if I configure the stack that way, POP3 email does not
come through. Very strange situation... I would post an
ipconfig /all but I'm not onsite at the moment. I'll see
if one of the users can send me one.
Any other suggestions? Could I have built AD
incorrectly? I used the wizard and reviewed the log, no
errors. Any thoughts?
A

 

[Enkidu]

Thank you for responding
I have tried different configurations with the client IP
stack. I've put the ISP's DNS only, the internal DNS
only, etc... I understand that having only the DNS for
the internal server should work, but as I stated before,
if I configure the stack that way, POP3 email does not
come through. Very strange situation... I would post an
ipconfig /all but I'm not onsite at the moment. I'll see
if one of the users can send me one.
Any other suggestions? Could I have built AD
incorrectly? I used the wizard and reviewed the log, no
errors. Any thoughts?

DNS and AD are independant, though, obviously AD is dependent on DNS.
This problem appears to definitely be a DNS problem. Can you just
clarify something? What do you mean by "they cannot get pop3 email"?
Can they access websites? What happens when they try to bring down
pop3 emails?

What I'd look for with ipconfig /all would be IP address, default
gateway and DNS servers, and also the netmask. This would be against
the NIC that they use.

On the clients I'd expect to see IP address to be unique on the
network, the DNS set to internal address, the netmask set correctly
and the gateway address set to the IP address of the gateway.

On the servers I'd expect to see the IP address to be unique, the DNS
to itself the netmask set correctly and the gateway address set
correctly.

If that is all OK, I'd check the results of a DNS lookup with the
nslookup command of firstly an internal machine and then an external
machine.

Not being able to resolve external addresses correctly seems to show
the server is not correctly resolving the IP addresses on behalf of
the client.

In the DNS do you have a "." zone? If so, delete it and see if that
helps. You say that you have configured forwarders, so this is
unlikely.

http://support.microsoft.com/default.aspx?scid=kb;en-us;298148

Cheers,

Cliff

{MVP Directory Services}