Date: Fri, 12 Feb 1999 16:14:47 -0700 (MST) From: wildcardus freakis <wildcard@dax.belen.k12.nm.us> To: Christopher Michaels - SSG <ChrisMic@clientlogic.com> Cc: "Russell D. Murphy" <rdmurphy@vt.edu>, questions@FreeBSD.ORG Subject: RE: natd and MS Network Neighborhood Message-ID: <Pine.BSF.3.96.990212161410.5512A-100000@dax.belen.k12.nm.us> In-Reply-To: <6C37EE640B78D2118D2F00A0C90FCB441A5EE4@site2s1>
next in thread | previous in thread | raw e-mail | index | archive | help
I stand humblely corrected.... On Fri, 12 Feb 1999, Christopher Michaels - SSG wrote: > > -----Original Message----- > > From: wildcardus freakis [SMTP:wildcard@dax.belen.k12.nm.us] > > Sent: Friday, February 12, 1999 4:47 PM > > To: Russell D. Murphy > > Cc: questions@FreeBSD.ORG > > Subject: Re: natd and MS Network Neighborhood > > > > If I remember correctly MSNN uses Netbeui/Client for Microsoft protocols > > that are nonrouteable....if you have any routers in the middle including a > > routed or nat box doing routing then packets pertaining to these protocols > > are dropped...this is also the case with switches that are configured for > > TCP/IP only. To have MSNN work you must be on the same segment as the > > server that you want to connect to, be running Client for Microsoft or > > Netbeui or both and have no interfering devices > > (routers,nat,routed,switches,etc.) in the middle. > > > yes and no. MS network doesn't require NetBEUI it'll run perfectly > fine over TCP/IP and that is how my personal network is configured. MS > Networks use a proto called NETBIOS, but that runs on top of the transport > protocol. If this weren't the case samba servers wouldn't work w/o NetBEUI > support in the OS. The problem being that a standard windoze client cannot > browse across subnets, it uses a broadcast message to find and advertise > itself to the rest of the workgroup. Standard windoze 9x clients, when > there are no NT/samba servers on the network will become the browse master > but are not smart enough to concatenate a cross-subnet browse list. That's > where the NT server comes in, it can have a cross-subnet browse list. If I > remember correctly, you have an NT server/master-browser on each subnet, and > then each server shares/compares lists. This way you get a cross-subnet > browse list. Technically, samba has this same functionality and Russell can > use this to have a browse list on his laptop, but to my recollection samba > 1.19.x isn't compatible with NT servers in this respects. I honestly don't > know if the new 2.0x is compatible. > > HENCE.. the question, is he on an NT network? AND.. what version of > samba is he running? > > and after this long winded block of unreadable text, ultimately, > wildcardus is right, that the ms crap is all non-routable (as far as > browsing goes) and that's why you have your problem. The question now is, > can it be fixed. You should be able to connect to a machine on the ms > network, once MS knows the IP it's trying to connect to. (theoretically) > > (if I just put my foot in my mouth, please don't kill me) > > > When i say switches I mean ones configed for TCP networks only...I have > > several switches and I can see MSNN through them fine, but then they are > > considered Workgroup Switches so they are configured for routing everthing > > even Microsoft garbage. > > > > I might be wrong but this is to the best of my knowledge. > > > > Ta- > > Sasha > > > P.S. My coworker just looked over my shoulder and asked me if I was > writing a book here. ;^P > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990212161410.5512A-100000>