Some senseless babbling from Dan Egli to All
on 09-25-99  21:40 about TCP/IP Questions...

 DE> Ok all.

 DE> You got my OS/2 and Win98 box talking to each other. I thank you
 DE> immensely for that.

 DE> NOW, I need more help. I will be attaching to a Cablemodem soon, using
 DE> a Hub to broadcast the Signal to both boxes (only got 1 nic, so hub is
 DE> only answer till I get another nic. then I can use one machine as the
 DE> gateway for the other) and I want to have RemoteAccess to the cpu. So I
 DE> need the following (If they are in the Warp 4 distribution, just say so
 DE> and tell how to install/configure them please):

 DE> Telnet Daemon/Server
 DE> FTP Daemon/Server (Both need user access)

OS/2 has these, but they're rudimentary.  There are other FTP daemons 
available, including a Washington University port that's unfortunately 
limited with anonymous access (and a bear to set up at all).

I use Hethmon Brother's FTPD, which is simple to set up and use, though it 
has not yet been updated to support resume (not that it's important right 
now, with only a modem connection to the Internet).

It should also be noted that your cable provider will frown on setting up 
server software.  Though they will probably only check for a web server, if 
anything.

 DE> Domain Name Server Program (so that I can maintain my own DNS entries,
 DE> and not have to rely
 DE> on my Cable Provider's DNS which is slow).

You will have to use your provider's DNS anyway.  If you set it up in 
caching mode, then you're often-used addresses will be resolved without 
going to the provider's name server.

What you'll want to use is BIND, available at Hobbes.  Setting it up is a 
bit of a pain, of course.

 DE> News Spooler (Must spool Usenet news on my HDD, must allow for config
 DE> of WHICH groups to spool, and must allow NNTP support).

Changi is probably the best bet there.  I haven't taken a good look at it, 
since I just used Vsoup and GIGO to gate news into the BBS.

 DE> I know I could get all this for Linux easy, but no boxes left to put
 DE> Linux on. It's on the machine w/ a dead HDD and I got no $$ to replace
 DE> the HDD. So it's out of the picture.

Something else you need to consider is the fact that if you're going to 
plug the cable modem into the hub, you'll need two separate valid IP 
addresses for each connected computer.  

Unless, of course, you use a firewall product (such as InJoy's) which will 
do NAT (IP masquerading) on the configuration you're using.  One box will 
have the cable modem's IP address, and the other will have a RFC1918 
address (e.g. 172.16.0.1).  Keep in mind that the cable company may use a 
few such addresses themselves.  I had my network based on 172.16.0.x, then 
the friggin cable company starting using my addresses (and you'll see them, 
because the cable modem is a local LAN), so I moved to 172.20.0.x.

The performance of InJoy Firewall's IP masquerading is quite good, 
incidentally.  It's fast, and doesn't muck up the server machine (if you 
use this program, make sure to set the priority to the highest).

Mike Ruskai
thannymeister@yahoo.com


... FBI: Federal Bureau of Intimidation

___ Blue Wave/QWK v2.20
--- Platinum Xpress/Win/Wildcat5! v3.0pr2
801
805/4
3613/666