Return to BSD News archive
Xref: sserve comp.protocols.ibm:3445 comp.unix.bsd:12991 comp.os.386bsd.development:1528 comp.protocols.tcp-ip.ibmpc:20951 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!sgiblab!spool.mu.edu!howland.reston.ans.net!newsserver.jvnc.net!newsserver.technet.sg!news.np.ac.sg!news.np.ac.sg!news From: ngps@nova.np.ac.sg (Ng Pheng Siong) 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 08:56:25 +0800 Organization: Ngee Ann Polytechnic, Singapore Lines: 29 Message-ID: <2d8svp$2l6@nova.np.ac.sg> References: <2cupi2$8ba@orion.cc.andrews.edu> <1993Nov26.150903.1@spcvxb.spc.edu> <2d6jho$j35@u.cc.utah.edu> NNTP-Posting-Host: nova.np.ac.sg 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: From RFC100[12]: NetBios name service listens on both TCP & UDP port 137. UDP port 138 is for NetBios datagram service, and TCP port 139 for session service. I have _just_ begun work on an RFC NetBios implementation for *BSD - I'm using FreeBSD now - and am working on the name service. My eventual aim is to implement an SMB client. Unfortunately my FreeBSD machine just went belly-up from a massive IDE drive failure. (No, shouldn't be the software - the drive was having problems prior to FreeBSD's installation. ;) If anyone else is working on this, I'm interested in hearing from you. NetBios-over-TCP/IP is in RFC 1001/1002. SMB specs can be found in lanman.gatech.edu:~/lanman. (When you ftp in, you're landed at "incoming." Do a "cd ../lanman".) Cheers. - PS -- Ng Pheng Siong * ngps@np.ac.sg * npngps@solomon.technet.sg Computer Centre, Ngee Ann Polytechnic, Singapore