<[EMAIL PROTECTED]> wrote:
> [...]
> It is like a LAN, where your neighborhood is on one node, with dynamic ip
> sent out, but you can't set sharing through your node/gateway. When
> configuring connection settings, it's done as an ethernet LAN. I think,
> actually, that your modem is a type of gateway device.
The cable modems themselves can vary quite a bit in capabilities and
features. Some are simply a bridge-type device translating between the LAN
(10Base-T) and cable system (HFC). Others are full-blown router-type
devices, capable the whole host of protocol handling functions.
In my neighborhood (Cox@Home in Phoenix AZ), we started with the LANcity
bridge-type units. Just a couple of days ago, that unit was replaced with a
General Instruments DOCSIS-compliant unit. The GI unit has a web-based
management interface, and is fully manageable from the remote end, allowing
Cox to (finally) determine that there really have been signal issues on my
link for the last few years.
Or, the good news is that in any case, the setup on the home PC tends to be
the same -- just set 'er up as a networked configuration and it should work.
There are some variations depending on your market. In some areas (mine for
instance) the IP addresses are "long-term" dynamic. They MAY change but
probably won't unless they need to renumber for some reason, or you get a
new cable modem (argh!) In other areas, you're likely to be assigned a new
address each time you start up your system. Whether or not you need to do
this is strictly dependent on your cable system operator (MSO).
If you're not using Windows9x, the level of support will probably be pretty
low. To keep life simple, I'd let the installer set it all up on a Win9x
system, then "fix" it after they leave. Win9x is a handy troubleshooting
tool anyhow. If you do need to handle dynamic addressing, you'll need to
have lined up a DHCP client for your OS of choice. Other than that, you'll
need the appropriate drivers for your 10Base-T network card and a TCP/IP
protocol stack. And of course, some apps that can use it.
I don't use TCP/IP under DOS regularly myself, but I have briefly played
with the old DR-DOS WebSpyder (think that was the name) and it worked well
enough. The Novell DOS clients and Microsoft's DOS clients also work. Again,
finding apps that use this may be hit-or-miss.
Good luck, Or!
- Bob
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
