Re: (ASCEND) www.ascend.com technotes

[Dean Frye <dfrye@ascend.com.au>]

Jon, here is the note.

Regards,

dean




           Question:

           Are there any Win'95/Win NT filters that won't bring up and keep
up my line in
           an IP routed environment?  I am not doing any bridging.

           Answer:

           If you have NETBIOS running on your Windows NT or Windows '95
PC, then you might
           be suffering a problem where the PC makes NETBIOS name queries
and DNS queries
           to attempt to resolve NETBIOS names.  On Windows '95, this
typically happens
           when you have "Client for Microsoft Networks" installed as one
of the network
           protocols in "Control Panel"-->"Network".

           Because of these queries, the Ascend appears to dial out for no
reason and the
           line never seems to timeout and hang up thereafter.  These
queries are not
           "broadcasts", but actual IP routed requests.  To counter this,
we can filter
           out based on the NETBIOS source ports of 137, 138, and 139.
These call filters
           will work for most applications, but are not guaranteed for all
due to the many
           different possible PC configurations for Windows.

           Use these filters when you are routing IP (not bridging) and you
have Windows
           NT or Windows '95 computers on your network:

           Implement these as CALL FILTERS (output filters placed on a
connection profile):

           Go into Ethernet-->Filters-->IP Call...
                   and modify them to look just like this:

           Input filter 01...
           Valid=YES
           Type=GENERIC
                   Forward=No
                   Offset=0
                   Length=0
                   Mask=0000000000000000
                   Value=0000000000000000
                   Compare=Equals
                   More=No

           Make sure all other Input filters are "Valid=No".


           Output filter 01...
           Valid=Yes
           Type=IP
                   Forward=No
                   Src Mask=0.0.0.0
                   Src Adrs=0.0.0.0
                   Dst Mask=0.0.0.0
                   Dst Adrs=0.0.0.0
                   Protocol=17
                   Src Port Cmp=Equals
                   Src Port #=137
                   Dst Port Cmp=None
                   Dst Port #=N/A
                   TCP Estab=N/A

           Output filter 02...
           Valid=Yes
           Type=IP
                   Forward=No
                   Src Mask=0.0.0.0
                   Src Adrs=0.0.0.0
                   Dst Mask=0.0.0.0
                   Dst Adrs=0.0.0.0
                   Protocol=17
                   Src Port Cmp=Equals
                   Src Port #=138
                   Dst Port Cmp=None
                   Dst Port #=N/A
                   TCP Estab=N/A

           Output filter 03...
           Valid=Yes
           Type=IP
                   Forward=No
                   Src Mask=0.0.0.0
                   Src Adrs=0.0.0.0
                   Dst Mask=0.0.0.0
                   Dst Adrs=0.0.0.0
                   Protocol=17
                   Src Port Cmp=Equals
                   Src Port #=139
                   Dst Port Cmp=None
                   Dst Port #=N/A
                   TCP Estab=N/A

           Output filter 04...
           Valid=YES
           Type=GENERIC
                   Forward=Yes
                   Offset=0
                   Length=0
                   Mask=0000000000000000
                   Value=0000000000000000
                   Compare=Equals
                   More=No

           Make sure all other Output filters are "Valid=No".

           To implement, go to:

           Ethernet-->Connections-->(go into profile)-->Session Options...
                   make Call Filter=1

           This won't take effect until you bring down any existing call on
this profile.

           Additionally, in Windows NT 4.0:

           Control Panels-->Network-->Protocols-->TCP/IP Protocol-->WINS
Address...

           There is a check box for "Enable DNS for Windows Resolution".
If checked,
           Windows will query DNS to resolve NETBIOS names and it would
appear like the
           Ascend is dialing out by itself every 5-10 minutes.  Make sure
it is unchecked.





At 03:29 PM 3/3/99 -0500, ##Jon Duren wrote:
>Ascend previously had several technotes on their website that told how to
>filter netbios over ip in pipelines.  This was a very useful technote, but
>I have been unable to find it on the new site.  Does anyone have an old
>mirror of these pages, or know where they are online now.  I've even
>checked the "login" on Aos.ascend.com and could not find it.
>
>Thanks,
>Jon Duren
>
>++ Ascend Users Mailing List ++
>To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
>To get FAQ'd:	<http://www.nealis.net/ascend/faq>
> 
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>