🚀 go-pugleaf

In article <19970506221545152478@gothic.u-net.com>,
bryce@gothic.u-net.com.nospam (^CountB^) wrote:

> Steve Firth <filter@firthcom.demon.co.uk> wrote:
> 
> > ^CountB^ <bryce@gothic.u-net.com.delete-me> wrote:
> > 
> > > I want to do a similar thing, but I want to connect 10 macs and a
> > > printer to a FreBSD server.
> > > 
> > > Do I need MacLan too?
> > 
> > Hiya Count,
> 
> Hi
> 
> > Do you still see Icey these days? 
> 
> Not any more, no.
> 
> > I assume that with FreeBSD, you are
> > running an NFS server? I don't think MacLan connect will help you, it's
> > designed for connecting PCs to AppleTalk networks. What you need is
> > MacNFS which costs big money - around �200 per Mac, I've been thinking
> > of doing the same myself, using an old(ish) PC as an NFS server.
> 
> Well, I actually don't need to share disks, but do need to do stuff such
> as POP3 logins, web serving etc. So far I can't even ping my mac, yet
> both my Mac and unix box appear to be setup okay (I think, I'm new to
> actually *doing* unix).

I have a Mac/WinNT/95/FreeBSD network (occasionally Linux appears
also).  There is a peculiarity to the Mac in that at least one TCP/IP
application (NCSA Telnet, Fetch, etc.) has to have been started up
before the Mac will actually respond to external pings.  This is so
a driver can be loaded into the system.  After this, the TCP/IP
application can be stopped, and the Mac will respond to pings still.

If you have subnet and IP address set up correctly on the Macintosh
and the FreeBSD box, the first thing I would do is try NCSA Telnet
from the Mac to FreeBSD.  After that, experiment with pinging from
FreeBSD to the Mac.

In general, the Mac is a disaster for IP.  Their latest and most
improved version networking software, OpenTransport, is vulnerable
to a "ping of death".  I have to laugh, really.