Archived from groups: microsoft.public.win2000.dns (
More info?)
"Gerhard Fiedler" <lists@connectionbrazil.com> wrote in message
news:1wot9qdp1oy82$.pscu3zqa532k$.dlg@40tude.net...
> First off, thank you all very much for your help. That's a not so common
> experience in newsgroups these days...
You are very welcome.
I do appreciate the thanks and you will probably find that
your experience with news groups in general is not the same
as these Microsoft newsgroups.
Generally, any well-formed question will get some response
and more often than not a LOT of help.
Part of the reason may be the MVP system Microsoft uses to
recognize and reward those of us who help a lot.
> It seems I created some confusion not describing the complete situation.
> Here it is:
I think you have explained it pretty well.
(In the other part of the thread, you seem to have it
focused on the problem if not completely resolved
so I am not going to address the items below unless
you reply and indicate otherwise.)
> - I am off-site, using my own ISP to connect through pcAnywhere to one
> computer on a client's internal network.
> - This one computer is an FTP server. All other computers on that network
> are normal office PCs.
> - The client's internal network is connected to the Internet through the
> client's ISP.
> - The ISP has some firewall running, but opened the ports I need to
connect
> to that one computer (and some others we need for that machine).
> - The two DNS servers that don't work are the ones that my client has
> received from their ISP.
> - They are also the ones they see in the ipconfig output of their office
> PCs (which work fine).
> - But I haven't yet seen an actual copy of ipconfig or nslookup output. So
> far they just confirmed that the numbers were the ones. This is what I'm
> waiting for now.
> - In the meantime, I have set up that one machine to use the DNS servers
of
> my own ISP (which is different from my client's ISP). It works fine with
> these DNS servers. I think that's ok, as long as it is a temporary
> solution. After all, they only get used very rarely (that machine is not
> typically used for browsing, only when I download updates etc.)
>
> Hope this clarifies some of the confusion I created.
>
> At this point, I'm waiting for the copies of the outputs of a few commands
> run on their normal PCs to see what exactly these PCs do, and whether they
> in fact are using these two DNS servers that don't work -- not from that
> machine, not from here, and not from a few other places (as you were nice
> enough to check also).
>
> I guess if in fact the other office PCs use these two DNS servers and they
> work there, we have some kind of firewall problem with my client's ISP.
>
> If the office PCs use other DNS servers, then the whole thing was a
> miscommunication from my client's ISP to my client and from my client to
> me.
>
> See also some inline comments below.
--
Herb Martin
>
> Thanks,
> Gerhard
>
>
> Herb Martin wrote:
>
> > You need a reliable DNS server (set) even if you have to install one
> > yourself.
>
> I know. And I intend to get one from my client's ISP
I think it's
their
> responsibility to provide that.
>
>
> >> I know... no offense taken
But when I use the DNS servers of my own
ISP
> >> (for example 200.174.144.14), it all works -- the nslookup works, and
> >> normal Internet access and DNS resolution too if I add it to the DNS
> >> servers in the connection configuration. So I guess the firewall is not
a
> >> problem.
> >
> > What do you mean "of your own ISP"?
>
> I hope that the above has cleared that up. I am off-site and using a
> different ISP than my client, where the one computer with the DNS server
> problem is located.
>
> > Why aren't you using YOUR ISP DNS?
>
> I think I wrote that I'm using my ISP's DNS server
And the whole
> problem is that the client's DNS servers (or what I currently have reason
> to believe what they are) don't work from that one computer. So I added
> temporarily the DNS servers of my own ISP to the list of DNS servers on
> that problematic machine, just to get it working for now.
>
> >> It looks like something's wrong with the DNS server addresses they got
> >> from their ISP.
>
> > Or the DNS servers are firewall -- or set so the clients are
> > considered "foreign" and therefore not serviced.
>
> Yes. I'm waiting for some feedback about other machines on the network to
> see what their exact setup is.
>
> > nslookup is a pretty funky tool (e.g., it gives bogus errors if their is
> > no reverse-PTR record for the DNS server) but it has the advantage
> > of being available on all NT-class machines that have IP.
>
> Thanks for that info. I've always thought that networking is some kind of
a
> black art...
Facebook
Twitter
Instagram