Return to BSD News archive
Xref: sserve comp.protocols.ibm:3443 comp.unix.bsd:12988 comp.os.386bsd.development:1526 comp.protocols.tcp-ip.ibmpc:20949
Newsgroups: comp.protocols.ibm,comp.unix.bsd,comp.os.386bsd.development,comp.protocols.tcp-ip.ibmpc
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!emba-news.uvm.edu!aix3.emba.uvm.edu!wollman
From: wollman@aix3.emba.uvm.edu (Garrett Wollman)
Subject: Re: NETBIOS Unix Server info.... : -)
Message-ID: <1993Nov27.195216.6201@emba.uvm.edu>
Sender: news@emba.uvm.edu
Organization: University of Vermont, EMBA Computer Facility
References: <2cupi2$8ba@orion.cc.andrews.edu> <1993Nov26.150903.1@spcvxb.spc.edu> <2d6jho$j35@u.cc.utah.edu>
Date: Sat, 27 Nov 1993 19:52:16 GMT
Lines: 26
In article <2d6jho$j35@u.cc.utah.edu>,
A Wizard of Earth C <terry@cs.weber.edu> wrote:
>The port 137 isn't a broadcaster, as far as I can tell -- it's TCP. Port
>138 is supposed to be a UDP port, but it's for datagram rather than
>virtual circuit use of the server... from my /etc/services:
> nb-ns 137/tcp netbios-ns nb-name
> nb-dgm 138/udp netbios-dgm nb-dg
> nb-ssn 139/tcp netbios-ssn nb-vc
I'd just like to point out that this doesn't really prove anything,
since the exact same ports are assigned for the other transport. IANA
like to assign the same port for both TCP and UDP to the same service,
whenever possible, to avoid confusion and reduce the demand on the
port space (if you suddenly find you need a
connection{-oriented,-less} transport for your protocol, just use it
and keep the same port number).
-GAWollman
--
Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ...
wollman@emba.uvm.edu | Shashish is the bonding of hearts in spite of distance.
uvm-gen!wollman | It is a bond more powerful than absence. We like people
UVM disagrees. | who like Shashish. - Claude McKenzie + Florent Vollant