IE Dns problem?

  • Thread starter Thread starter Russell DeMarco
  • Start date Start date
R

Russell DeMarco

We have a Win2000 network (using AD) with a DSL connection thru a Netgear
router and 8 Win XP workstations. When we go to get on the internet it
times out and you get the IE Microsoft screen about DNS or something (as if
there's no connection available). But when you exit IE & try again it works
fine or hit refresh once or twice. Being a non-tech I don't know how to fix
this but everyone is getting annoyed, any ideas?

Thanks.
 
What does each workstation's DNS point to? Your internal one or your ISP's?
Try changing it to the ISP DNS servers.
 
May I jump into this conversation since it looks like I'm having the same
problem? If you think I should get out of this thread, let me know I'll post
in a new thread.

When I put my ISP dns first, the Internet access works fine. However, my
Windows XP client doesn't see AD resources. For instance, when I share a
folder and want to assign security, I can't select the AD domain to get the
list of users/groups.
On the other hand, when I put my dns first, the Internet access doesn't
work. However, my Windows XP client can see the AD ressources. For instance,
when I share a folder and want to assign security, I can select the AD
domain to get the list of users/groups.

Any idea?

Thanks,
David.
 
In
David Gagné said:
May I jump into this conversation since it looks like I'm having the
same problem? If you think I should get out of this thread, let me
know I'll post in a new thread.

When I put my ISP dns first, the Internet access works fine. However,
my Windows XP client doesn't see AD resources. For instance, when I
share a folder and want to assign security, I can't select the AD
domain to get the list of users/groups.
On the other hand, when I put my dns first, the Internet access
doesn't work. However, my Windows XP client can see the AD
ressources. For instance, when I share a folder and want to assign
security, I can select the AD domain to get the list of users/groups.

Any idea?

David, you probably have a root zone in DNS.
In the DNS console Expand Forward Lookup zones, if you have a zone named
".", delete the zone. After you refresh the console or close and reopen the
console it will enable the Root Hints, after this is done you can enable a
Forwarder to your ISP's DNS.
Read step 3: 300202 - HOW TO: Configure DNS for Internet Access in Windows
2000
http://support.microsoft.com/?id=300202

Oh, and one more thing, you should never use your ISP's DNS in any position,
on any member of an Active Directory domain. This will cause errors and poor
network performance.
 
Thanks Kevin,
you were right, I had a root zone. I deleted it and created the forwarders
for my isp.

Why do you say adding my isp dns after my own dns on an AD member will cause
errors and poor network performance?
Since this is my network at home, my server is not always running. So it
happens regularly that I use a client computer and need my Internet
connection while my server is closed. So when I add my isp dns after my own
dns on the client computer, my internet connection still works fine with my
server closed. Of course, I agree that this is causing a timeout to happen
for my dns before using my isp dns. However, I don't see any difference in
the speed of my internet connection...

Thanks,
David.
 
In
David Gagné said:
Thanks Kevin,
you were right, I had a root zone. I deleted it and created the
forwarders for my isp.

Why do you say adding my isp dns after my own dns on an AD member
will cause errors and poor network performance?
Since this is my network at home, my server is not always running. So
it happens regularly that I use a client computer and need my Internet
connection while my server is closed. So when I add my isp dns after
my own dns on the client computer, my internet connection still works
fine with my server closed. Of course, I agree that this is causing a
timeout to happen for my dns before using my isp dns. However, I
don't see any difference in the speed of my internet connection...

This does not affect the speed of your internet connection, it affects the
accessing of domain resources authenticated by the domain controller.
I took this from your original post:
When I put my ISP dns first, the Internet access works fine. However,
my Windows XP client doesn't see AD resources. For instance, when I
share a folder and want to assign security, I can't select the AD
domain to get the list of users/groups.
Your ISP does not have the records necessaary for your AD domain Win2k XP
and Win2k3 look in DNS for the DCs SRV records, and they won't find these
records in the ISP's DNS.
 
Back
Top