can ping by ip but not by name...

  • Thread starter Thread starter Mark
  • Start date Start date
M

Mark

Hello,

I can ping a certain computer on my network by ip address,
but not by name. I know this is a dns problem, but how
would you address it? This computer is using DHCP to
obtain it's tcp/ip information. I've ran ipconfig /all
and it is getting the right info for the dns server and
the wins server and all of that. I am not sure if this is
client side or server side. The machine can ping itself
by name. No one else can ping it by name. If this is a
server issue, how would you find what is causing it?
Thanks.

Mark
 
In
Mark said:
Hello,

I can ping a certain computer on my network by ip address,
but not by name. I know this is a dns problem, but how
would you address it? This computer is using DHCP to
obtain it's tcp/ip information. I've ran ipconfig /all
and it is getting the right info for the dns server and
the wins server and all of that. I am not sure if this is
client side or server side. The machine can ping itself
by name. No one else can ping it by name. If this is a
server issue, how would you find what is causing it?
Thanks.

Mark
Click to expand...

If this machine is part of a domain can you ping it by FQDN?
Is the machine registering in DNS?
 
I can now no longer ping by ip address, name, or fqdn, but
I can go to start, run, \\billing14 and access it fine.
That doesn't make sense. Kevin, you had asked if the
machine is registering in DNS and honestly, I don't even
know how to check that. Any ideas? Thanks

Mark
 
I can now no longer ping by ip address, name, or fqdn, but
I can go to start, run, \\billing14 and access it fine.
That doesn't make sense. Kevin, you had asked if the
machine is registering in DNS and honestly, I don't even
know how to check that. Any ideas? Thanks

Mark
 
In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:
I can now no longer ping by ip address, name, or fqdn, but
I can go to start, run, \\billing14 and access it fine.
That doesn't make sense. Kevin, you had asked if the
machine is registering in DNS and honestly, I don't even
know how to check that. Any ideas? Thanks
Click to expand...
Use:
nslookup
billing14.domain.com
 
I did the nslookup and it was able to give the name and ip
address just fine. Only strange thing is that where it
says the server name and ip first, the server name is
unknown, but the ip address is right. That's kind of
weird. Any other thoughts? Thanks again.

Mark

-----Original Message-----
In (e-mail address removed)
Click to expand...
 
In
Mark said:
I did the nslookup and it was able to give the name and ip
address just fine. Only strange thing is that where it
says the server name and ip first, the server name is
unknown, but the ip address is right. That's kind of
weird. Any other thoughts? Thanks again.
Click to expand...
That start up message by nslookup is caused from not having a PTR record
for the IP listed for DNS. You can ignore it or configure a reverse lookup
in DNS.

You can do nslookup for the name in DNS and the machine is resolved?
This is not a DNS problem then, at least for your local DNS. Would you by
any chance have your ISP's DNS in TCP/IP properties?
In TCP/IP properties on the DNS tab for this machine do you have NetBIOS
over TCP/IP enabled?
 
Ok. I just noticed something. The actual ip address of
the machine is 172.28.228.47 and when doing the nslookup
or trying to ping, it's trying to locate the machine with
an ip of 172.28.228.73, so that would be dns that's the
problem, right? Now, how does one access the dns table or
whatever to try and correct that? Thanks again.

Mark
 
In
Mark said:
Ok. I just noticed something. The actual ip address of
the machine is 172.28.228.47 and when doing the nslookup
or trying to ping, it's trying to locate the machine with
an ip of 172.28.228.73, so that would be dns that's the
problem, right? Now, how does one access the dns table or
whatever to try and correct that? Thanks again.

Mark
Click to expand...
Use the DNS snap in to open your forward lookup zone for its domain and edit
the host with the machines name. DDNS should have taken care of this make
sure you have Dynamic updates enabled on the machine and the zone.
 
I enabled dynamic updates for the zone, but didn't see
where to do this for the machine. There is only one
machine listed under the domain and that's the dc, which
is the dns server. There is no setting for enabling
dynamic updates, at least that I can see. I have tried
pinging the problem machine by name and it still tries to
ping it with the wrong ip address.

I've ran nslookup, which gives the wrong ip for that
machine. I've ran nbtstat with -a and -A and that found
the machine fine with correct ip address. I have ran net
view \\<computer name> and that came back fine, so, as far
as I can tell, this still seems to be a dns problem.
Where does this info get cached in dns, and how do you
access it, or can you? Thanks.

Mark
 
In
Mark said:
I enabled dynamic updates for the zone, but didn't see
where to do this for the machine. There is only one
machine listed under the domain and that's the dc, which
is the dns server. There is no setting for enabling
dynamic updates, at least that I can see. I have tried
pinging the problem machine by name and it still tries to
ping it with the wrong ip address.
Click to expand...

On the zone it is on the general tab.
On the machine it is on the DNS tab "Register this connection's IPs in DNS"
or something like that.

All domain members *MUST* only point to the DC for DNS.
I've ran nslookup, which gives the wrong ip for that
machine. I've ran nbtstat with -a and -A and that found
the machine fine with correct ip address. I have ran net
view \\<computer name> and that came back fine, so, as far
as I can tell, this still seems to be a dns problem.
Where does this info get cached in dns, and how do you
access it, or can you? Thanks.
Click to expand...
What is the machine using for DNS?
 
The problem machine is using dhcp and it is pointing to
the domain controller for dns as it should. I hope I
answered that right. Thanks.

Mark
 
In
Mark said:
The problem machine is using dhcp and it is pointing to
the domain controller for dns as it should. I hope I
answered that right. Thanks.
Click to expand...
I was looking back through the thread I can't find if you said what OS was
on the machine.
If it is a legacy OS such as NT4 or Win9x you need DHCP to register in DNS
for this machine. You may also need WINS.
 
It's win2k pro and is using DHCP for obtaining ip address
and for DNS. Thanks again. I do appreciate your help.
This seems to be an odd case.

Mark
 
In
Mark said:
It's win2k pro and is using DHCP for obtaining ip address
and for DNS. Thanks again. I do appreciate your help.
This seems to be an odd case.
Click to expand...
Did you make the setting on the DNS tab in TCP/IP properties, I posted
previosly?.
 
That option was already checked on the DNS tab, sorry,
forgot to tell you that in the last post. Thanks.

Mark
 
In
Mark said:
That option was already checked on the DNS tab, sorry,
forgot to tell you that in the last post. Thanks.

Mark
Click to expand...
Run ipconfig /registerdns that should register the record in DNS.
 
Hi Kevin,

First of all, I want to thank you for sticking it out with
me and continuing to help out, I really appreciate it! I
did try running ipconfig /registerdns (twice!) and it
didn't help. I even waited an hour after running it each
time to let it update, still didn't help. So, I kind of
took the easy way out and renamed the computer. Now I can
ping it just fine. I pinged billing14 (the old computer
name) just for the heck of it and it still wanted to have
the ip address of 172.28.228.73, even though there is no
billing14 anymore. I'll have to delete it from active
directory and then ping it. If it still comes up with an
ip after that, then I'll give up. Either way, think I got
it from here. Thanks again Kevin for helping out!

Take care,

Mark
 
Back
Top