WSS wrote the following about [netconnect] Re: Networking Amiga with Mac:
> 
> Andrew Tait ([EMAIL PROTECTED]) on 19 Sep 2000 13:28:12 +0000:

> > Networking is toffee.  Set local IP addresses up on each machine
> > (192.168.0.1 and 192.168.0.2 respectively), netmask of 255.255.255.0
> > and they can see each other.  All you need is the protocols to get
> > them to talk.  
> 
> Oh!  Is that all? ;-)  That means absolutely nothing to me I'm afraid. 
> Just bear in mind that you're dealing with a me here - A relic from the
> 8 bit era.  Idiots guide please. ;-)

OK, to put it in perspective, here is the Interface chunk from
genesis.conf:  I'll annotate (gently!)

INTERFACE
IfName              Ethernet
 [Name as displayed in Genesis]
Sana2Device         DEVS:Networks/cnet.device
 [cnet.device comes from Aminet.  Controls PCMCIA card]
Sana2Unit           0
 [Duh!]
Sana2Config         ENV:Sana2/
 [Not used]
IPAddr              192.168.0.1
 [My IP address]
Gateway             192.168.0.253
 [You DON'T need this]
Netmask             255.255.255.0
 [192.168.0.x addresses are "local"]
MTU                 1500
 [Block size to transfer.  This is the default]
AutoOnline
 [Connects the LAN when Genesis is started]
UseNameServer
 [I need DNS for connecting to the 'net.  You won't]
HostName            miggy.lan
 [Just a name(MIGGY) and a domain (LAN)]
NameServer          193.38.113.3
 [My DNS entry #1]
NameServer          194.117.157.4
 [My DNS entry #2]

That's it!!  Because you only want to talk on the LAN, you don't need
the NameServer entries, the UseNameServer entry or the Gateway.  In
fact, you only need the device name, the IP address and the netmask :)

> Maybe it will all become clearer when all the equipment is in place.  Fingers
> crossed.

If you have any problems at the Amiga or Mac end give me a shout. 
I've got ShapeShifter happily co-existing with my LAN, and at work
I've got 18 Macs on a LAN/WAN, setup basically the same way.

> Neil's already pointed out some solutions for that.  (Thanks Neil BTW)  Now if I
> could just figure out what this "protocols" thingy means... :)

A protocol is just a defined way of communicating.  HTTP, FTP, IRC,
NFS, AFS, SMB quite a few others.  They are standardised (pretty much)
so that an NFS server on a Linux box and an NFS client on an Amiga can
talk.

> > The Power one is what I've got.  Genius ME3000II SE.  Great wee card. 
> > Works with the Aminet drivers, so you can shop around and see if you
> > can shave a few ��� off Power's solution.
> 
> Who else is there for Miggy?  All there are is Power & Eyetech making that sort
> of stuff, and Analogic (spit) selling some of it.  Who else is there?

Nearly all PCMCIA cards conform well to the NE2000 standard, so you
plug in the card, install the cnet.device driver into Devs:Networks/
and that's it!!  Check your local PC dealers for the cheapest PCMCIA
card they do.

> > Oh, we've just bought 2 G4s and 3 iMacs at work.  Fun, ain't they?
> 
> I don't know yet.  I'll let you know when I've got one... real soon now. :-)  

You won't be disappointed.  Especially the new keyboard and mouse.

> Have to use a whole truckload of Compaqs at my workplace.  For some reason,
> they refuse to move over to am Amiga network just to apease me. ;-)

I'm IT manager, so I only buy PCs for controlling hardware.  Our
academic network is primarily Mac.  Much easier for networking
printers, sharing files, network backups etc.

If you do need any help, just drop me an email and I'll do my very
best to sort things out.

Cheers,

Totty  <8^)

-- 
Totty has an Amiga A1200, with 68060/50 and 603e/200 PPC.
32Mb RAM.  8x ATAPI CD.  1.7Gb HD.  ShapeShifter V3.10 + OS 7.5.5
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>

Reply via email to