Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 9 May 1999 10:34:55 -0700 (PDT)
From:      rick hamell <hamellr@dsinw.com>
To:        John K <john@volvo.se>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   RE: Not able to see freebsd machines on NT machine
Message-ID:  <Pine.BSF.3.91.990509102718.9185D-100000@dsinw.com>
In-Reply-To: <Pine.BSD/.3.91.990509144407.7037C-100000@nike.volvo.se>

next in thread | previous in thread | raw e-mail | index | archive | help

> On a side note:
> I heard somewhere that the Mircosoft IP stack includes NetBios informatio=
n
> in it=B4s TCP/IP headers ( //Computernames and so on) and that this is wh=
y
> you can "browse the network" even if there=B4s no NetBeui on your=20
> windows box.

=09If there is, I don't think it's terribly reliable. :) I unluckily=20
still end up putting NetBIOS on if I need to share resources between=20
Windows machines. I tried to share with just TCP/IP but when you go to=20
network neighborhood it's hit or miss if it'll see anything. Once you've=20
actually got things connected it seems a little more reliable.=20
=09Now, what I'd like to know is there any was I can kill=20
Windows95's keep alive packets. I.e. when I have a dial-up connection=20
(ppp with the -auto and -alias options,) with a time set up, Windows 9X=20
seems to ping the network and keeps it alive. :(

=09=09=09=09=09Rick


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.91.990509102718.9185D-100000>