Pinging name stopped working

Sorry for the vagueness.

I am trying to "ping roo" from my internal network, not from the internet.
I was able to do this yesterday, now I can not.

I am able to ping any other pc on the network (pcs and TIGGER) with no
issue, its just this one file server.

I assume its a DHCP issue but I don't know where to look.

Steve
"CJT" wrote:

> steves100.RemoveThis@hotmail.com wrote:
>
> > I have 2 servers on my network. First (TIGGER) connected to internet and
> > intranet, running DNS and DHCP
> >
> > #2 (Roo) basically a file server.
> >
> > For some reason no computer on the network can ping ROO only the IP, this
> > was working yesterday.
> >
> > I have looked in DHCP settings on both servers.
> >
> > Name resolution is working on all the other PCs.
> >
> > Any help
> >
> > Steve
>
> When you say TIGGER is "running DNS" do you mean it's configured as
> a DNS server?
>
> Then can I assume you're talking about "Roo's" external name? In that
> case you should have your DNS server set to be authoritative on it. If
> you're trying to refer to ROO by an internal name, then it probably
> belongs in the hosts file(s), and should not be exposed to the external
> world.
>
> Your post is pretty vague on just what you've got set up and what you're
> trying to do.
>
> --
> The e-mail address in our reply-to line is reversed in an attempt to
> minimize spam. Our true address is of the form che....RemoveThis@prodigy.net.
>
 >> Stay informed about: Pinging name stopped working 

steves100.TakeThisOut@hotmail.com wrote:

> Sorry for the vagueness.
>
> I am trying to "ping roo" from my internal network, not from the internet.
> I was able to do this yesterday, now I can not.
>
> I am able to ping any other pc on the network (pcs and TIGGER) with no
> issue, its just this one file server.
>
> I assume its a DHCP issue but I don't know where to look.

I don't know why you think it's a DHCP issue, unless you think it's
a coordination problem between DHCP and DNS.

How is your LAN configured to resolve local names? Are they in the
hosts file? When you ping ROO, does it resolve to an IP address?
Is that IP address the correct one?

Does ROO have the same IP address today that it did yesterday?
>
> Steve
> "CJT" wrote:
>
>
>>steves100@hotmail.com wrote:
>>
>>
>>>I have 2 servers on my network. First (TIGGER) connected to internet and
>>>intranet, running DNS and DHCP
>>>
>>>#2 (Roo) basically a file server.
>>>
>>>For some reason no computer on the network can ping ROO only the IP, this
>>>was working yesterday.
>>>
>>>I have looked in DHCP settings on both servers.
>>>
>>>Name resolution is working on all the other PCs.
>>>
>>>Any help
>>>
>>>Steve
>>
>>When you say TIGGER is "running DNS" do you mean it's configured as
>>a DNS server?
>>
>>Then can I assume you're talking about "Roo's" external name? In that
>>case you should have your DNS server set to be authoritative on it. If
>>you're trying to refer to ROO by an internal name, then it probably
>>belongs in the hosts file(s), and should not be exposed to the external
>>world.
>>
>>Your post is pretty vague on just what you've got set up and what you're
>>trying to do.
>>
>>--
>>The e-mail address in our reply-to line is reversed in an attempt to
>>minimize spam. Our true address is of the form che....TakeThisOut@prodigy.net.
>>


--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che....TakeThisOut@prodigy.net.
 >> Stay informed about: Pinging name stopped working 

Your right it is probably a DNS issue.
I am not using a HOSTS file I am using I assume DNS (sorry I really don't
know) I am not using WINS.
I can ping the IP fine, just not the name, and only this computer has the
issue.

When I do a NSLOOKUP I get the following respnse which I assume is not
good.....

*** Can't find server name for address 10.0.0.3: Non-existent domain
Default Server: UnKnown
Address: 10.0.0.3


10.0.0.3 is TIGGER my DNS server.

Is there an easy way to uninstall and reinstall DNS or becasue of AD it
impossible?

Steve



CJT <abujlehc.DeleteThis@prodigy.net> wrote in news:4315EEB8.7020606@prodigy.net:

> steves100.DeleteThis@hotmail.com wrote:
>
>> Sorry for the vagueness.
>>
>> I am trying to "ping roo" from my internal network, not from the
>> internet. I was able to do this yesterday, now I can not.
>>
>> I am able to ping any other pc on the network (pcs and TIGGER) with
>> no issue, its just this one file server.
>>
>> I assume its a DHCP issue but I don't know where to look.
>
> I don't know why you think it's a DHCP issue, unless you think it's
> a coordination problem between DHCP and DNS.
>
> How is your LAN configured to resolve local names? Are they in the
> hosts file? When you ping ROO, does it resolve to an IP address?
> Is that IP address the correct one?
>
> Does ROO have the same IP address today that it did yesterday?
>>
>> Steve
>> "CJT" wrote:
>>
>>
>>>steves100@hotmail.com wrote:
>>>
>>>
>>>>I have 2 servers on my network. First (TIGGER) connected to
>>>>internet and intranet, running DNS and DHCP
>>>>
>>>>#2 (Roo) basically a file server.
>>>>
>>>>For some reason no computer on the network can ping ROO only the IP,
>>>>this was working yesterday.
>>>>
>>>>I have looked in DHCP settings on both servers.
>>>>
>>>>Name resolution is working on all the other PCs.
>>>>
>>>>Any help
>>>>
>>>>Steve
>>>
>>>When you say TIGGER is "running DNS" do you mean it's configured as
>>>a DNS server?
>>>
>>>Then can I assume you're talking about "Roo's" external name? In
>>>that case you should have your DNS server set to be authoritative on
>>>it. If you're trying to refer to ROO by an internal name, then it
>>>probably belongs in the hosts file(s), and should not be exposed to
>>>the external world.
>>>
>>>Your post is pretty vague on just what you've got set up and what
>>>you're trying to do.
>>>
>>>--
>>>The e-mail address in our reply-to line is reversed in an attempt to
>>>minimize spam. Our true address is of the form che....DeleteThis@prodigy.net.
>>>
>
>
 >> Stay informed about: Pinging name stopped working 

OK, I did a little more troubleshooting, and its a DDNS issue. It seems
for some reason DNS isn't being dynamic anymore. I tried an
ipconfig /registerdns and that didn't work. I was able to get it to
work by manually adding a HOST A record.

I have tried to clear the cache, didnt help




CJT <abujlehc.DeleteThis@prodigy.net> wrote in news:4315EEB8.7020606@prodigy.net:

> steves100.DeleteThis@hotmail.com wrote:
>
>> Sorry for the vagueness.
>>
>> I am trying to "ping roo" from my internal network, not from the
>> internet. I was able to do this yesterday, now I can not.
>>
>> I am able to ping any other pc on the network (pcs and TIGGER) with
>> no issue, its just this one file server.
>>
>> I assume its a DHCP issue but I don't know where to look.
>
> I don't know why you think it's a DHCP issue, unless you think it's
> a coordination problem between DHCP and DNS.
>
> How is your LAN configured to resolve local names? Are they in the
> hosts file? When you ping ROO, does it resolve to an IP address?
> Is that IP address the correct one?
>
> Does ROO have the same IP address today that it did yesterday?
>>
>> Steve
>> "CJT" wrote:
>>
>>
>>>steves100@hotmail.com wrote:
>>>
>>>
>>>>I have 2 servers on my network. First (TIGGER) connected to
>>>>internet and intranet, running DNS and DHCP
>>>>
>>>>#2 (Roo) basically a file server.
>>>>
>>>>For some reason no computer on the network can ping ROO only the IP,
>>>>this was working yesterday.
>>>>
>>>>I have looked in DHCP settings on both servers.
>>>>
>>>>Name resolution is working on all the other PCs.
>>>>
>>>>Any help
>>>>
>>>>Steve
>>>
>>>When you say TIGGER is "running DNS" do you mean it's configured as
>>>a DNS server?
>>>
>>>Then can I assume you're talking about "Roo's" external name? In
>>>that case you should have your DNS server set to be authoritative on
>>>it. If you're trying to refer to ROO by an internal name, then it
>>>probably belongs in the hosts file(s), and should not be exposed to
>>>the external world.
>>>
>>>Your post is pretty vague on just what you've got set up and what
>>>you're trying to do.
>>>
>>>--
>>>The e-mail address in our reply-to line is reversed in an attempt to
>>>minimize spam. Our true address is of the form che....DeleteThis@prodigy.net.
>>>
>
>
 >> Stay informed about: Pinging name stopped working