Cannot resolve names

[Guest]

Hi, good morning to al

We are experiencing a very strange issue on a machine within our domain. This machine has the network correctly configured with an static IP address and, in fact, all the servers and the gateway can be "pinged" if the IP address is used, and we can enter the windows network neighborhood without problems. However, it is completely unable to resolve names, and obviously, if we let it get an address by DHCP, it fails miserably. The domain name server, a Red HAt Linux machine is performing well; in fact from any other machine there are no connectivity problems. We have also checked that there is not any physical reason to explain this abnormal behavior by plugging another computer in the place of the affected machine

Any idea of what can we do

Thanks in advance
Jaume Tomas Amella

 

[William Stacey [MVP]]

1) Can you ping the dns server from this machine.
2) Use nslookup or dig to perform directed query at dns server. What does
it say?

--
William Stacey, MVP

Hi, good morning to all

We are experiencing a very strange issue on a machine within our domain.

This machine has the network correctly configured with an static IP address
and, in fact, all the servers and the gateway can be "pinged" if the IP
address is used, and we can enter the windows network neighborhood without
problems. However, it is completely unable to resolve names, and obviously,
if we let it get an address by DHCP, it fails miserably. The domain name
server, a Red HAt Linux machine is performing well; in fact from any other
machine there are no connectivity problems. We have also checked that there
is not any physical reason to explain this abnormal behavior by plugging
another computer in the place of the affected machine.

 

[Guest]

Good morning agai

I can ping the server and all computers (the gateway, for instance) within our network without problems, but when I make a direct query using nslookup I obtain "Can't find server name for address 192.101.162.68: No response from server. Default servers are not available". However, from any other computer (with the same operating system and identical configuration of the network card), everything works fine

Thanks in advance
Jaum

 

[William Stacey [MVP]]

It looks like client can not access 192.101.162.68. Can you ping that from
the client? And is that a running dns server?

--
William Stacey, MVP

Good morning again

I can ping the server and all computers (the gateway, for instance) within

our network without problems, but when I make a direct query using nslookup
I obtain "Can't find server name for address 192.101.162.68: No response
from server. Default servers are not available". However, from any other
computer (with the same operating system and identical configuration of the
network card), everything works fine.

 

[Guest]

Yes, yes, 192.101.162.68 is our primary DNS and is running fine. I can ping it from the client, but when I try to make "nslookup" I get error. Furthermore, the offending PC can be pinged both from the DNS server and from any other machine on the network. In fact, it can do it all except name resolution, it seems..

Thanks in advance
Jaume

 

[William Stacey [MVP]]

If this is a bind server, check the acls. Also check any firewall rules
that may be blocking port 53 for this clients IP. Lets see some output of
dig. The actual output would help. Also lets see an ipconfig /all from the
client.

--
William Stacey, MVP

Yes, yes, 192.101.162.68 is our primary DNS and is running fine. I can

ping it from the client, but when I try to make "nslookup" I get error.
Furthermore, the offending PC can be pinged both from the DNS server and
from any other machine on the network. In fact, it can do it all except name
resolution, it seems...

Thanks in advance,

Jaume

 

[Ace Fekay [MVP]]

In

Ok, let's go forward:

1) We don't have any firewall within our network, so the port 53 is
not blocked for our internal computers. Nor there is a acls. As far
as I'm concerned, the client has not a personal firewall.

2) This is the output of ipconfig /all for the client (by the
way...can we use "dig" in a windows 2000 computer?)

Windows 2000 IP configuration:

Host name: ifae-w105
Primary DNS Suffix: ifae.es
Node Type: Peer-Peer
IP Routing Enabled: No
WINS Proxy Enabled: No
DNS Suffix Search List: ifae.es

Ethernet Adapter Local Area Connection:

Connection-specific DNS Suffix: ifae.es
Description: Intel 8255x-based PCI Ethernet Adapter (10/100)
Physical Address: 00-02-B3-A7-BB-CE
DHCP Enabled: No
IP Address: 192.101.162.44
Subnet Mask: 255.255.255.0
Default Gateway: 192.101.162.10
DNS Servers: 192.101.162.68
Primary WINS Server: 192.101.162.1



Many thanks, Jaume Tomas

If you get this message (not really an error):
"Can't find server name for address 192.101.162.68: No response from server.
Default servers are not available".

It usually just means that there's no reverse zone PTR entry for the DNS
server, 192.101.162.88. Are you saying that this is the ONLY client that
gets this message?

Can you ping your DNS server by it's FQDN? Try this:

ping dnsServername.ifae.es

ping -a dnsServername.ifae.es

Please post your results... Thanks!

--
Regards,
Ace

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

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

 

[William Stacey [MVP]]

Please show the nslookup output for the session. Include a test of a name
that should exist.

--
William Stacey, MVP

Ok, let's go forward:

1) We don't have any firewall within our network, so the port 53 is not

blocked for our internal computers. Nor there is a acls. As far as I'm
concerned, the client has not a personal firewall.

2) This is the output of ipconfig /all for the client (by the way...can we

use "dig" in a windows 2000 computer?)

Windows 2000 IP configuration:

Host name: ifae-w105
Primary DNS Suffix: ifae.es
Node Type: Peer-Peer
IP Routing Enabled: No
WINS Proxy Enabled: No
DNS Suffix Search List: ifae.es

Ethernet Adapter Local Area Connection:

Connection-specific DNS Suffix: ifae.es
Description: Intel 8255x-based PCI Ethernet Adapter (10/100)
Physical Address: 00-02-B3-A7-BB-CE
DHCP Enabled: No
IP Address: 192.101.162.44
Subnet Mask: 255.255.255.0
Default Gateway: 192.101.162.10
DNS Servers: 192.101.162.68
Primary WINS Server: 192.101.162.1

Many thanks,

Jaume Tomas

 

[ObiWan]

1) We don't have any firewall within our network

Ok, but please verify if the "problem machine" is
running a "personal firewall" (or even ICF) if that's
the case, maybe the "firewall" is blocking packets
and creating the problem you observed