Return to BSD News archive
Xref: sserve comp.protocols.ibm:3444 comp.unix.bsd:12989 comp.os.386bsd.development:1527 comp.protocols.tcp-ip.ibmpc:20950
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!sol.ctr.columbia.edu!news.kei.com!news.byu.edu!cwis.isu.edu!u.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Newsgroups: comp.protocols.ibm,comp.unix.bsd,comp.os.386bsd.development,comp.protocols.tcp-ip.ibmpc
Subject: Re: NETBIOS Unix Server info.... : -)
Date: 28 Nov 1993 00:21:14 GMT
Organization: Weber State University, Ogden, UT
Lines: 35
Message-ID: <2d8qtq$t4q@u.cc.utah.edu>
References: <1993Nov26.150903.1@spcvxb.spc.edu> <2d6jho$j35@u.cc.utah.edu> <1993Nov27.195216.6201@emba.uvm.edu>
NNTP-Posting-Host: cs.weber.edu
In article <1993Nov27.195216.6201@emba.uvm.edu> wollman@aix3.emba.uvm.edu (Garrett Wollman) writes:
>>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).
According to our AT&T StarServer running LMX over TCP/IP, these are
the only transport sockets supported for LANManager. I think I agree
with the sentiment, and if I were designing it instead of Microsoft,
I would have at least multiplexed nb-dgm and nb-ssn to the same port
number.
Nevertheless, the TCP based DOS LanMan client from ftp.microsoft.com
will not use ports other than 137, 138, and 139; they are hard coded
in the binaries.
The only reason I quoted the /etc/services was to show the "official"
port naming, not to indicate that these were the only ports supported...
I do realize that a port need not be in /etc/services to be bound. 8-).
Terry Lambert
terry@cs.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.