Name Resolution Problem

[Kevin Darcy]

If a ping makes the access work temporarily, then this is almost
certainly not a DNS problem. DNS isn't related to ping or anything at
that level of network (except as a consumer of network resources, like
everything else).

Since you say the access works "until a reboot of the access device",
then that strongly implicates the "access device" as the source of the
problem.


- Kevin

rkirby at modimes.org wrote:

> We are running an NT network and have recently experienced problem
> resolving two Intranet server pages from locations outside of the
> local net (WAN, VPN, etc.)  We have several other Intranet servers
> that are all accessable from both local and remote sites.  The local
> resident  users do not have not problems with the access to these two
> resouces in question.  We have primary and secondary WINS server.
>
> >From the remote sites (WAN, VPN) we cannot resolve the URL name using
> the IE browser.  If we ping either the IP address or the resouce name
> they both return successfully.  Once this has been done we can
> successfully access both resources via the browser until a reboot of
> the access device.
>
> Does anyone offer a suggestion to isolate where the problem is?