DNS resolution only with administrator

  • Thread starter Thread starter Manfred Ehrhart
  • Start date Start date
M

Manfred Ehrhart

Hello,

I'm a developer without special skills about administration, but with PME, I
must deal with daily problem.
A computer running Win2000 pro stopped DNS resolution suddenly. Only the
administrator rights(local or domain acount) allow the user to connect to
the internet. The rest seems to operate normally (if I set the IP adress,
all is ok, but for the standard user ....).
What can I do or check up in order to activate again the DNS resolution.
Thanks you very much

Manfred
 
Manfred Ehrhart said:
Hello,

I'm a developer without special skills about administration, but with PME, I
must deal with daily problem.
A computer running Win2000 pro stopped DNS resolution suddenly. Only the
administrator rights(local or domain acount) allow the user to connect to
the internet. The rest seems to operate normally (if I set the IP adress,
all is ok, but for the standard user ....).
What can I do or check up in order to activate again the DNS resolution.
Click to expand...

Well, first of all is determining that this is actually the case -- it is
unlikely
unless the station or DNS servers are misconfigured. If either is
misconfigured
then we first repair that problem.

How do you know?

Use NSLookup from the affected workstation to determine if DNS
resolution is working. Compare this with the "IPConfig /all" to ensure
that the workstation is configured to use ONLY internal DNS servers.

Make sure those servers are "up" and correctly configured.

Ensure that they can either resolve Internet addresses directly OR have
(usually better) a border or external DNS server that can resolve the
public names of the Internet.

Do NOT try to "mix internal and external" DNS servers on the NIC
configuration of a client workstation -- use internal only if you have them.
 
Thanks for your quick reply

Nslookup reports the same as ipconfig, and it's the same as with a machine
where all is ok
server: ns3.wanadoo.fr
adress 193.252.19.3

I set this DNS on all my clients across the LAN (in TCP/IP properties).
There are only two DNS (your ISP wandoo) primary (193.252.19.3) and
alternate (193.252.19.4) . I don't know why this machine exposes this
trouble , because all the others machine (NT4 and 2000) are set with the
same manner.

Manfred
 
In
Manfred Ehrhart said:
Hello,

I'm a developer without special skills about administration, but with
PME, I must deal with daily problem.
A computer running Win2000 pro stopped DNS resolution suddenly. Only
the administrator rights(local or domain acount) allow the user to
connect to the internet. The rest seems to operate normally (if I set
the IP adress, all is ok, but for the standard user ....).
What can I do or check up in order to activate again the DNS
resolution. Thanks you very much
Click to expand...

What Service Pack level is the Win2k?
DNS Name Resolution Does Not Work for Users Who Are Not Administrators
http://support.microsoft.com/default.aspx?scid=kb;en-us;329405&Product=win2000
 
In
Manfred Ehrhart said:
Thanks for your quick reply

Nslookup reports the same as ipconfig, and it's the same as with a
machine where all is ok
server: ns3.wanadoo.fr
adress 193.252.19.3

I set this DNS on all my clients across the LAN (in TCP/IP
properties). There are only two DNS (your ISP wandoo) primary
(193.252.19.3) and alternate (193.252.19.4) . I don't know why this
machine exposes this trouble , because all the others machine (NT4
and 2000) are set with the same manner.

Manfred
Click to expand...

Do you have AD running? If so, you cannot use your ISP's DNS addresses in
any AD members' IP properties, without causing major concerns. Should only
the internal DNS.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Nslookup reports the same as ipconfig, and it's the same as with a machine
where all is ok
server: ns3.wanadoo.fr
adress 193.252.19.3
Click to expand...

The above just indicates the DNS server.

It's the info LATER on the screen that indicates whether that server
answers (correctly or incorrectly), or fails on a timeout.

If it doesn't answer or times out, my first choice is

NSLookup -time=10 some.addr.es.s
 
In
Herb Martin said:
http://support.microsoft.com/default.aspx?scid=kb;en-us;329405&Product=win2000

I had to go read that -- that was virtually incredible.

I never saw this behavior on any SP3 machines (to my knowledge.)
Click to expand...

I saw it once and was amazed that a user account couldn't resolve anything.
It's been around at least over a year as far as I can remember.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Thanks you very much for all your replies.
The computer runs SP3. But today the DNS name resolution works (and I don't
change anything ...). I will not install Sp4. I go back to my C++
programming. It's easier for me and my spirit. Thanks
Manfred
 
In
Manfred Ehrhart said:
Thanks you very much for all your replies.
The computer runs SP3. But today the DNS name resolution works (and I
don't change anything ...). I will not install Sp4. I go back to my
C++ programming. It's easier for me and my spirit. Thanks
Manfred
Click to expand...

No prob... if C++ is easier, go for it!
:-)

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top