"Or Botton" <[EMAIL PROTECTED]> wrote:
> After a long sleep, i'm back on the list. Had afew things going on,
> so had no time for E-Mail... so I had to download over 490 messages,
> 1.7MB worth.
Heh. Most of those will be from the last week!
> What I want to do, is to use the P350 with its ISDN connection to be
> the connection provider for the 486 via the LAN.
Two ways come to mind:
The first assumes you can get the DOS machine speaking TCP/IP over the NIC.
Do that first. You could use a product like Sygate on Win95 to provide NAT
(Network Address Translation) from your inside LAN to the Internet. You'd
simply install Sygate (or equivalent) and set up your internal LAN. NAT
would "hide" your internal LAN addresses behind the IP address assigned to
your ISDN connection. I would urge you to seek out a product that uses NAT
versus proxy (try
http://www.uq.net.au/~zzdmacka/the-nat-page/nat_windows.html), as proxy
solutions will require your DOS apps be proxy-aware in many cases. The
overly-complicates the issue. NAT software for Windows is not free
typically, although Win98SE includes sharing capabilities through ICS.
The second takes a more forward-thinking approach. You didn't mention how
much RAM or disk you've got on the 486, but if you've got 16MB or more RAM,
and 100MB of disk to spare, and since you're planning on setting up FTP and
a web server anyhow, have you considered making the 486 the gateway machine
running Linux?
A 486 is plenty of horsepower for such a machine (actually, you can get by
with less hardware but it's more work) and you'd gain the advantages of
having FTP, Apache web server (the most widely used on the Internet) and a
wealth of NAT/proxy solutions which could all be easily used by the Windows
machine client software. And not to forget DOS: you can run the DOSemu
package that will let you run your DOS apps as the box continues to act as a
gateway for the Windows machine. DOS apps unmodified in most cases (depends
on the specific app).
Finally, there *are* some DOS-based gateway packages
(http://www.uq.net.au/~zzdmacka/the-nat-page/nat_dos.html) but I suspect the
DOS machine is pretty much dedicated when using them, and I'd be concerned
about stability under load. I'd suggest something that lets it do other
useful work as well.
Good luck! Let us know how it works out.
- Bob
PS - I simply searched for DOS NAT to find those pages. Looks like a little
treasure trove of solutions.
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
More info can be found at;
http://www.softcon.com/archives/SURVPC.html
