Re: (ASCEND) pipeline 50 unexpected dial-out

["Keith G. Murphy" <keithmur@mindspring.com>]

Code Chang wrote:
> 
> hi, All
> 
>     When our customer used Pipeline 50 with ISDN.  But the pipeline 50 always has unexpected dial-out problem.
>     And there are NT server on their ethernet segment.  I guess maybe caused the NT broadcast ?
> 
>     Does anyone have the same problem ?  Or can we use filter to solve the problem ?
> 
>     Thanks !!
> 
If you have control over their network, you could try to address it
there:

I believe what happens is that Windows machines try to resolve their
workgroup and host names through DNS.  I think Microsoft has a registry
setting or patch to get them to stop doing this.  You'd have to go to
Microsoft's site (or maybe DejaNews) to find out more...

Or:

They may simply have a client with a misconfigured domain name and/or
workgroup.
The time I saw it was when I had a local DNS server and my Win95 client
was configured to a different domain than the local DNS server was
authoritative for, causing the local DNS server to generate outgoing
packets, trying to resolve both hostname.domain and workgroup.domain. 
Correcting the domain name on the Win95 client fixed the problem. 
Funnily enough, if the client doesn't know about any DNS server on the
local network, it seems to be smart enough not to generate outgoing
packets on its own.  (Another brain-dead MS'ism: apparently the client
has no *need* to resolve the damn names through DNS...)
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>