how ping command resolve name?

Hi,
just want to know how does the ping command work out the name resolution.
From DNS or WINS or hosts file or whatever? I noticed that some times DNS
can resolve a name but ping can't and some times the other way around.
Thanks in advance,

hi,
http://www.microsoft.com/technet/net..._ch07.mspx#E5C
--
Dragos CAMARA
MCSA Windows 2003 server


"tree leafs" wrote:

> Hi,
> just want to know how does the ping command work out the name resolution.
> From DNS or WINS or hosts file or whatever? I noticed that some times DNS
> can resolve a name but ping can't and some times the other way around.
> Thanks in advance,
>
>
>

If you have a primary DNS server specified, and you try to ping a host, the
DNS server will be used. What do you mean when you say "DNS can resolve a
host, but ping can't"?

Are you using nslookup to connect to the DNS server to resolve these hosts?
Also keep in mind that just because you don't get ping replies, does not mean
DNS is not working. Client side firewalls of all types can block ICMP
traffic, but DNS should always present you with the IP of that host (if it
can resolve it obviously).

"tree leafs" wrote:

> Hi,
> just want to know how does the ping command work out the name resolution.
> From DNS or WINS or hosts file or whatever? I noticed that some times DNS
> can resolve a name but ping can't and some times the other way around.
> Thanks in advance,
>
>
>

Jason,
the dns server is last in order, first is hosts file then lmhosts and the
last is the dns
--
Dragos CAMARA
MCSA Windows 2003 server


"Jason Fraioli" wrote:

> If you have a primary DNS server specified, and you try to ping a host, the
> DNS server will be used. What do you mean when you say "DNS can resolve a
> host, but ping can't"?
>
> Are you using nslookup to connect to the DNS server to resolve these hosts?
> Also keep in mind that just because you don't get ping replies, does not mean
> DNS is not working. Client side firewalls of all types can block ICMP
> traffic, but DNS should always present you with the IP of that host (if it
> can resolve it obviously).
>
> "tree leafs" wrote:
>
> > Hi,
> > just want to know how does the ping command work out the name resolution.
> > From DNS or WINS or hosts file or whatever? I noticed that some times DNS
> > can resolve a name but ping can't and some times the other way around.
> > Thanks in advance,
> >
> >
> >

Are you sure that WINS ( lmhost ) work before DNS , that was correct for NT
but fromW2K it v.v AFAIK
Arkady

"Dragos CAMARA" <(E-Mail Removed)> wrote in message
news:8B1E3BAF-38C6-4C99-B80A-(E-Mail Removed)...
> Jason,
> the dns server is last in order, first is hosts file then lmhosts and the
> last is the dns
> --
> Dragos CAMARA
> MCSA Windows 2003 server
>
>
> "Jason Fraioli" wrote:
>
>> If you have a primary DNS server specified, and you try to ping a host,
>> the
>> DNS server will be used. What do you mean when you say "DNS can resolve
>> a
>> host, but ping can't"?
>>
>> Are you using nslookup to connect to the DNS server to resolve these
>> hosts?
>> Also keep in mind that just because you don't get ping replies, does not
>> mean
>> DNS is not working. Client side firewalls of all types can block ICMP
>> traffic, but DNS should always present you with the IP of that host (if
>> it
>> can resolve it obviously).
>>
>> "tree leafs" wrote:
>>
>> > Hi,
>> > just want to know how does the ping command work out the name
>> > resolution.
>> > From DNS or WINS or hosts file or whatever? I noticed that some times
>> > DNS
>> > can resolve a name but ping can't and some times the other way around.
>> > Thanks in advance,
>> >
>> >
>> >