*BSD News Article 24451


Return to BSD News archive

Xref: sserve comp.protocols.ibm:3440 comp.unix.bsd:12987 comp.os.386bsd.development:1525 comp.protocols.tcp-ip.ibmpc:20937
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!usenet.ins.cwru.edu!eff!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: 27 Nov 1993 04:03:04 GMT
Organization: Weber State University, Ogden, UT
Lines: 32
Message-ID: <2d6jho$j35@u.cc.utah.edu>
References: <2cupi2$8ba@orion.cc.andrews.edu> <1993Nov26.150903.1@spcvxb.spc.edu>
NNTP-Posting-Host: cs.weber.edu

In article <1993Nov26.150903.1@spcvxb.spc.edu> terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.) writes:
>  I set this up and I'm having a problem, as LAN Manager (or at least DEC's
>Pathworks) expects to see a directory services server listening for broad-
>casts on port 137. I suspect that this code only works if there are one or
>more "real" TCP LANman hosts on the local network. I suppose I'll have to
>write a directory services server (or enough of one to fake out Pathworks).
>If anybody else has done this already, please send me mail and let me know.

I'd also be interested in this, if it is out there... or if you write it.
8-).

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:


	#
	# LAN Manager services and sockets
	#
	nb-ns		137/tcp		netbios-ns nb-name
	nb-dgm		138/udp		netbios-dgm nb-dg
	nb-ssn		139/tcp		netbios-ssn nb-vc

It works for me with the client from ftp.microsoft.com, but I do have
other servers on the same wire.


					Terry Lambert
					terry@cs.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.