RE: Clients can't access internet using DSL Modem directly connected

From: JimC, PMP (JimCPMP_at_discussions.microsoft.com)
Date: 10/12/04


Date: Tue, 12 Oct 2004 15:07:06 -0700

I'm no network person by any measure, but I had a similar problem and this is
what I did to get around it (and I am positive there are many better ways to
do it... I just don't know them). The first thing I did was to open a window
into my dsl modem and change the configuration to keep it on at all times.
Make sure the dsl modem is set to supply the dhcp information (unless you
want to do it yourself at the system level). If the person has a fixed ip
address, your dsl modem should be configured accordingly. I purchased a
linksys switch and hooked each system into one of the ports and daisy chained
my wireless off of that.

My addresses looked something like this:

65.13.xx.xxx (for the fixed ip address)
 also be sure to add the DNS and gateway information to the modem as well.
192.168.1.254 for the dsl modem
192.168.1.100 for the first system
192.168.1.101 for the second system... etc...
For each system, the subnet was 255.255.255.0 and the gateway was
192.168.1.254

While this is not the most secure configuration, it got me up and running
until I can configure a better solution with a hard firewall and place my
server in a dmz. Please be sure to turn on the firewall for your xp systems
(since it comes on by default for server 2003).

The method I originally tried was installing two network cards in my server,
one connected to the dsl modem and the other to the switch and the other
systems. I ran into the same problems you did and suspect the firewall on my
server was blocking the incoming traffic from my local systems (or the
firewalls on my local systems were contributing to the problem). I didn't
have the time (or want to take the risk) of turning off both firewalls and
seeing what happened. I think it should have worked, but for whatever
reason, it didn't.

Any additional insight form someone that actually knows what they are doing
would be most helpful!



Relevant Pages

  • << SBS News of the week - Sept 26 >>
    ... And he points to the info you need to put the file on the server in the ... at the network perimeter. ... The Symantec Firewall/VPN and the Gateway Security ... by the firewall at risk. ...
    (microsoft.public.backoffice.smallbiz)
  • << SBS News of the week - Sept 26 >>
    ... And he points to the info you need to put the file on the server in the ... at the network perimeter. ... The Symantec Firewall/VPN and the Gateway Security ... by the firewall at risk. ...
    (microsoft.public.backoffice.smallbiz2000)
  • << SBS News of the week - Sept 26 >>
    ... And he points to the info you need to put the file on the server in the ... at the network perimeter. ... The Symantec Firewall/VPN and the Gateway Security ... by the firewall at risk. ...
    (microsoft.public.windows.server.sbs)
  • Re: need help re. office network install
    ... > and their network is a mess, the result of years of neglect. ... they have a gateway server w/ no special ... > firewall rules on it, they have a large DMZ that serves no purpose ... install anymore software on the firewall machine than is absolutely ...
    (comp.os.linux.networking)
  • Re: oops again
    ... open on the Firewall, and the default should be none. ... Since you intend to install IIS purely as a test server for your ASPX pages ... Make sure that IIS is only listening on the local network (192.168.x.y ...
    (microsoft.public.inetserver.iis)