Looks like you alread have some good people helping you out, so I am going
to say some things which may be more tangential to your specific situation.
So take what you like, if anything. I make some assumptions here, some of
which may be mistaken.
First, I would concur that you should upgrade to 7.1.
Second, when you said you get your ip addresses from qwest, it wasn't clear
if that meant you simply leased *static* adresses from them on a monthly
basis (for which they want an extra $35.00 per month from me), or whether
you lease a dhcp address from them on a per connection basis. These are two
different kinds of leases, hence the confusion.
Third, you must have a router, one which I don't remember you mentioning
(but I do have a tendancy to read too fast!). The router will either an
intel, cisco, linksys, or some such. Would be curious to know, as I have
qwest "service" as well.
Fourth, it seems as though you have each computer configured for a ppp
connection with qwest: that is, each computer has a direct connection to
qwest (direct, but still through your dsl router (or "modem")). And from
qwest, each computer leases a separate dhcp address. If this is correct, I
would be curious to know why you did it this way. This method is less
secure: first, for protection you are relying solely on the merits of your
router and its built-in firewall; second, each comptuer has a "routable"
(public) address, which makes it one-step easier for you to be hacked;
third, if you would have done it the way I am about to suggest, then you
would have been already up and running.
Here is a better way:
Scenario #1:
Plug your phone line into your cicso router; take the ethernet cable off of
the router and plug it into the Ethernet card of your windows server (2000
or NT). Put another ethernet card in the same server. From here, take the
cable from this second card to your hub. Then plug all remaining machines
into the hub.
Then put zone alarm firewall on windows server machine. Configure the
windows server to serve (via dhcp) private addresses (which are free).
Also, put a private ip addresses to the ethernet card of the windows server
machine that is *not* connected to the vdsl router. Also, configure the
windows server to run ICS. If you do it this way, then you two firewalls
rather than one: the vdsl router firewally, and the one on the windows
machine. This is like having two routers and two firewalls: the one you
bought from qwest, and also the windows machine running ICS. Or if you
choose not to use DHCP on your *internal* netork, just use static, private
addresses on the remaining computers (e.g., linux). Again, the private
addresses are more difficult to hack (I did not say "impossible," so none of
you actual hackers out there should flame me).
Scenario #2:
Same as above, except replace the windows server machine with the linux
machine and configure it as a firewall instead of relying on zone alarm.
This would be the way a "real man" would do it. If you would like to read a
good book on this, get *Building Linux and OpenBSD Firewalls*. It is very
good.
In conclusion, I see no need to have more than one computer leasing dhcp
addresses from qwest. Have one computer do it, and make that computer yours
so that you can have more centralized control over your network.
> -----Original Message-----
> From: plug-discuss-admin@lists.PLUG.phoenix.az.us
> [mailto:plug-discuss-admin@lists.PLUG.phoenix.az.us]On Behalf Of Tom
> Achtenberg
> Sent: Saturday, July 28, 2001 1:11 PM
> To: 'PLUG Phoenix Linux Users Group'
> Subject: RE: Networking
>
>
> No I do not have my server configured as a DHCP. as I said in my original
> post, I need to get the IP address from Qwests servers. The system found
> the NIC when I did the install so I presume it installed the
> drivers. Even
> MS will do that much. As far as the rest, I am an outright Linux
> rookie and
> do not know anything about syntax for ifconfig or Samba for that matter.
> Can you help?
>
>
> From: "Eric Van Buskirk" <yonica@qwest.net>
> To: <plug-discuss@lists.PLUG.phoenix.az.us>
> Subject: RE: Networking
> Date: Sat, 28 Jul 2001 09:40:02 -0800
> Reply-To: plug-discuss@lists.PLUG.phoenix.az.us
>
> I assume that you have configured NT as a DHCP server? Is it issuing
> private addresses, or qwest addresses, by the way? Have you installed the
> proper driver for your network card? Try "netconfig" from the
> command line
> and do it again, or you can do it with "ifconfig" if you have the proper
> syntax. Have you set a default gateway? A default gateway would not be
> necessary to obataining a dhcp address, but would be, of course, for
> internet access.
>
> When you say you cannot "see" your linuxbox, do you mean through network
> neighborhood? If so, you will not be able to do that until you install
> samba.
>
> > -----Original Message-----
> > From: plug-discuss-admin@lists.PLUG.phoenix.az.us
> > [mailto:plug-discuss-admin@lists.PLUG.phoenix.az.us]On Behalf Of Tom
> > Achtenberg
> > Sent: Saturday, July 28, 2001 8:22 AM
> > To: 'PLUG Phoenix Linux Users Group'
> > Subject: Networking
> >
> >
> > I finally got my RH Linux 7.0 box up and running. Now I need to
> > figure out
> > the network configuration. I have an NT network but get the IP
> addresses
> > from Qwest as part of my VDSL service. When I boot I get a fail
> > on the eth0
> > "Determining IP info" When I installed I selected to configure
> with DHCP.
> > I do not see this box over my network and cannot access the
> internet with
> > it. Can anyone help with this configuration?
> >
> > Tom Achtenberg
> >
>
>
>
> ________________________________________________
> See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail
> doesn't post to the list quickly and you use Netscape to write mail.
>
> PLUG-discuss mailing list - PLUG-discuss@lists.PLUG.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
(text/plain)