Re: Win 95 DUN errors with PM2Er

David Davies (David@buckeyeweb.com)
Mon, 18 Aug 1997 22:35:16 -0400

>
> On Mon, 18 Aug 1997, Operacao-AmazonNet wrote:
> > >Specify DNS Servers !! I think this is the big one. We just by
default put
> > >our resolvers in and forget about it.
> >
> > I thought PM3 would send the DNS Server to DUN automatically, just
> > like the remote IP address.
> A 0x51 debug will confirm this. But the PM3 must know the primary and
> secondary DNSes (set nameserver x.y.z.a and set nameserver 2 x.y.z.b).
> AFAIK, even if DNSes are set in DUN, the PM3 will accept/reject them and
> send down the correct DNSes. If no DNS is set on the PM3, it'll
> reject anything and send down a 0.0.0.0 for DNS.

That's a big negative !! At least for us. The resolvers that we use are
off of our network. Not sure if that matters or not. But if I take the
DNS servers out of DUN. then 70-80 percent of the users can't resolve. Now
I know that it may not be LE issue, more than likely an MS issue, but the
easy fix is just to specify. I have the same DNS's set in the PM'S as I
specify in the DUN settings. MAC, Unix, etc all pull O.K. but 3.1, 95 and
NT just love to have 'em specified. It's been that way as long as I can
remember.

Granted I'm not saying it shouldn't work I'm just saying that whenever
someone asks and I tell 'em to put 'em in their and especially check the
"log onto network setting" things are peachy after that.

David Davies
Director, Internet Services
Buckeye Internet Services, Ltd.
http://www.buckeyeweb.com
"Through the modem, past the NAP, around the World, nothing but Net...."
-------EXPANSION ONLY--------BRING BERNIE BACK TO CLEVELAND--------