Welcome, Guest. Please login or register.

Author Topic: "Easy"net Networking Pains!  (Read 13692 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline danbeaver

Re: "Easy"net Networking Pains!
« on: July 01, 2012, 10:18:45 AM »
I'm afraid that EastNet simplifies setting up AmiTCP v 3.0b; it does not help with the hardware all that much, in fact it took me 2 months to get online and only works on OS 3.x (they leave this out).  After more than several emails I sent went unanswered by Amigakit's support staff (over a 2 moth period) I finally got some help. The next issue for me was connecting my 2 network printers so I could print; they never answered this one. I finally got all of MiamiDX downloaded and setup so 2.5 months after I started I could surf and print via my home network.

Here are a few hints: there is a downloadable key file for MiamiDX, if you have USB support, then a USB Ethernet dongle sets up easier than any other (for wireless, get a ZuniDigital wireless bridge -- Newegg on sale for not that much, I just bought another for 25 salad leaves US).  Read through Amibay's help site for setups. If there is an area that doesn't work for you there are alot of folks out there to help.
 

Offline danbeaver

Re: "Easy"net Networking Pains!
« Reply #1 on: July 01, 2012, 12:13:52 PM »
Most commonly AmiTCP does not store the location of you driver in its db/interfaces and, if using EasyNet, in the EasyNet.cfg file. Make sure they point directly to your NIC device (xxx.device) driver. It does care about much else if the dhcp is set properly. MiamiDX will set your IP address, mask and router IP address automatically; EasyNet doesn't do dhcp as easily.
 

Offline danbeaver

Re: "Easy"net Networking Pains!
« Reply #2 on: February 13, 2013, 12:53:23 PM »
My best software buy in years is RoadShow68K.  It is dead simple to use, has a large number of supported interfaces, and is the fastest  TCP/IP stack I have ever used. I have never had it not work after 1) the one click install and 2) a simple copy of one file from Storage to DEVS. Oh, 3) a reboot.