A company might intentionally go out of their way for such late 1980's
state of the art engineering in order to acheive greater integration with
operating systems build around products such as LAN manager (I'm told that
much of the archaic stuff in NT is for the sake of backwards compability
with projects initiated in conjunction with IBM). It's probably worth
investigating to what extent the app is configurable, since even on the
same subnet it would be desirable to use unicast traffic. In order to more
precisely define the nature of the traffic in the absence of documentation,
the version of network monitor that ships with NT 4 should be sufficient to
narrow down the layer 4 ports involved. I'd say use the document search
engine at support.baynetworks.com, but, as usual, the carrier/voice-side
products would appear to be lacking in publicly available PDFs.
John Neiberger <[EMAIL PROTECTED]>@groupstudy.com on 12/31/2000 06:59:51 AM
Please respond to John Neiberger <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (bcc: Kevin Cullimore)
Subject: RE: NetBios forwarding (Addendum)
> In your config below, I think it might work, but only 1 access-list
would
do
> the trick because the server should not do any broadcasting once it is
> contacted by the client. Of course, that depends on the application
> software. What is it called anyway ?
This is Optivity Telephony Manager from Nortel. The OTM server is on a
different subnet from the client. We installed the client on a laptop and
put it on the same subnet as the server and everything worked correctly.
If
we run the software from a different subnet, there are two tabs that are
unavailable. One of our LAN guys said that it was trying to use netbios to
communicate to the server. Personally, I don't understand why it only uses
it for such a small part of the program. Heck, why use it at all?
>
> Access-Lists are a necessary evil which should be avoided whenever
possible.
> Personally, I think that less resources would be used to decide whether
to
> drop or foward a broadcast than to compare it to an access list.
>
> Winston.
>
> -----Original Message-----
> From: John Neiberger [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, December 31, 2000 2:01 AM
> To: [EMAIL PROTECTED]
> Subject: Re: NetBios forwarding (Addendum)
>
>
> Okay, after a tad more research, I've come up with the following config,
> which corrects some mistakes and misunderstandings in my previous
config.
>
> interface Serial0
> ip address 10.1.1.254 255.255.255.0
> ip directed-broadcast 101
> !
> interface Serial1
> ip address 10.2.2.254 255.255.255.0
> ip directed-broadcast 102
> !
> access-list 101 permit udp host 10.1.1.1 any eq netbios-ns
> access-list 101 permit udp host 10.1.1.1 any eq netbios-dgm
> access-list 102 permit udp host 10.2.2.2 any eq netbios-ns
> access-list 102 permit udp host 10.2.2.2 any eq netbios-dgm
>
> Now, from what I can tell, this will do what I'm attempting, but I'd
still
> love to have your opinions because I have *zero* experience with netbios
or
> broadcast forwarding. I'd hate to break one thing while trying to fix
> another. (gee, I've never done that before!)
>
> Thanks again,
> John
>
> > We have some new software running on a single workstation that is
trying
> to
> > use netbios to communicate with a server on a different subnet. We
do
> not
> > currently allow this type of forwarding, and I've never configured it
> > before. We'd like to limit netbios forwarding to just these two
> machines.
> > Here is my idea, let me know if this would be the way to do it.
> >
> > access-list 1 permit 10.1.1.1 (workstation)
> > access-list 2 permit 10.2.2.2 (server)
> >
> > ip forward-protocol udp 137
> > ip forward-protocol udp 138
> > ip forward-protocol udp 139
> >
> > int fastethernet1/0
> > ip add 10.1.1.254 255.255.255.0
> > ip directed-broadcast 1
> > ip helper-address 10.2.2.2
> >
> > int fastethernet2/0
> > ip add 10.2.2.254 255.255.255.0
> > ip directed-broadcast 2
> > ip helper-address 10.1.1.1
> >
> > Would this do what I'm trying to accomplish? If not, please let me
know,
> or
> > if anyone has any tips for this sort of thing, I'd love to hear them.
> >
> > Thanks a million, as usual!
> >
> > John
> >
> >
> >
> >
> >
> > _______________________________________________________
> > Send a cool gift with your E-Card
> > http://www.bluemountain.com/giftcenter/
> >
> >
> > _________________________________
> > FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to
[EMAIL PROTECTED]
>
>
>
>
>
> _______________________________________________________
> Send a cool gift with your E-Card
> http://www.bluemountain.com/giftcenter/
>
>
> _________________________________
> FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_______________________________________________________
Send a cool gift with your E-Card
http://www.bluemountain.com/giftcenter/
_________________________________
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
+-------------------------------------------------------------+
| This message may contain confidential and/or privileged |
| information. If you are not the addressee or authorized to |
| receive this for the addressee, you must not use, copy, |
| disclose or take any action based on this message or any |
| information herein. If you have received this message in |
| error, please advise the sender immediately by reply e-mail |
| and delete this message. Thank you for your cooperation. |
+-------------------------------------------------------------+
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
