Re: Vicom Gateway (Macintosh)

Simon Hayes (
Fri, 6 Mar 1998 12:43:33 -0800

>I guess that a way to solve the problem could be TCP/IP.

No, I don't think so. MacIP already uses TCP/IP, especially when you use
something like Gateway or IP netrouter, I think that's what they do.

>Maybe a solution with the new OT 1.3... i'm trying and trying...

I don't think so here either - I'm using OT 1.3, and it didn't make any

I don't think there is a real solution yet, as somebody here suggested.
The only other app I have the same kind of problem with is ftp. I found
some details about how the problem with fetch and these products is that
fethc sends the ip address of the machine it is on to the server, as I
understand cu does also. This is why we get server errors.

Both the gateways work by using a set of internal ip numbers for each
machine and using your real ip number to be a router of some kind to send
packets in and out. Thus fetch is sending it's internal ip number instead
of the real one and the server doesn't understand it.

now in fetch the actual error I get from the server is a port error, so
I've managed to find an ftp program for the mac which allows you to specify
the port, so I'm now working on trying to figure out what on earth I need
to specify in terms of the port.

This may or may not have anything to do with the cu error. I don't think
anything can be done about that until cu is updated or by buying a $1500,00
hardware router and a set of custom IP's. Not really an option for most
home cu users, I would imagine. The problem is not with the gateways,
rather it is with the old software which is not setup for dealing with the
gateways properly. At least, that is my understanding.

Interestingly for another project I've been doing some research on the home
networking market. Intel expects 20 million home networks similar to ours
in the next year, and that the entire market will come to over 1 billion
dollars by the end of 98. wowza. That's huge growth, far more than, say,
the adoption of windows NT by the fortune 500, which you see press on
almost every day. The most common reason cited for a home network is
sharing a printer, but the second most common reason cited is shared
internet access - one modem, one account, two PC's. Thus this setup and
this problem with cu-seeme is liable to become an issue developers will
find they have to address sooner rather than later, rsn.

Any developers listening??


Simon Hayes
The HyperCard Resource Page
The HyperCard Mailing List
Never pick a fight with anyone who buys ink by the barrel. -Jeff Ackerman