Re: Use BEFSR41 to join existing network infrastructure as DHCP server...help!
- From: "Jack \(MVP-Networking\)." <jack@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 26 Nov 2008 11:55:51 -0500
Hi
If you are accessing computers from remote you want the computers to have the same IP all the time.
One way to do so is static IP, or you can use DHCP server provided that the Router has IP reservation (AKA Static DHCP).
Static DHCP means that from the computer point of view it is a regular DHCP, however in the Router the DHCP server always assigns the same IP to the same computer (the MAC address is the key).
As far as I remember the BEFSR41 can Not do it (It is one of the first Cable/DSL Routers that got to market years ago).
I think that some of the Netgear Entry Level Cable/DSL Routers have IP reservation.
Or any current Routers that can be flashed with DD_WRT can do it too.
Jack (MS, MVP-Networking)
<lgerhardx@xxxxxxxxxxx> wrote in message news:907843f6-ef56-4bd5-a535-ec97fad17d3d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(Not sure if this is the right group to post this to, so I am sorry if
this belongs elsewhere. Please let me know!)
First off, what I am trying to do may not be possible...and I know
that. But, this is the equipment I have been given, so I want to make
sure that I am doing whatever I can get done with it.
I am at a main company office with a DHCP server here. I have a
remote office that has no DHCP server. They are on a different
network than our main office. Main is 192.168.8.x, 192.168.12.x,
192.168.10.x, and they are on 192.168.1.x.
They connect to our network with a Cisco PIX 501e firewall acting as a
gateway at 192.168.1.253.
Because we have no DHCP server at this remote location, we always have
had to physically set up a static address on every machine. Now we
are wanting to get away from that and put a DHCP server there to
autoconfigure any new systems that hook up.
Because cost is the absolute most important thing to our company I
purchased a Linksys BEFSR41 router from WalMart. I spent hours trying
to configure it to assign me a DHCP lease, which it did. After adding
a route for 192.168.0.0 to 192.168.1.253, I was able to reach my main
office network. BUT, Internet does not work at all. When I view the
routing table, it shows 0.0.0.0/0.0.0.0 heading out the WAN port...but
I am not able to use the WAN port for this kind of network connection,
and there seems to be no way for me to change this behavior. :(
When I looked at the DHCP lease information on my laptop when at the
remote location, it had assigned my default gateway to the router's
address. In the router, I set its default gateway to 192.168.1.253,
but again that was shown going to the WAN port. :(
The only solution I could reach is to manually set the default gateway
on the laptop to 192.168.1.253. This worked perfectly as far as me
being able to access everything I wanted...but totally defeats the
purpose of my DHCP server!
My question is, how can I make this work? How can I get this little
router to assign DHCP leases that correctly set the 'real' gateway for
our network, or if that's not possible, how can I set this router to
properly pass stuff to the 'real' gateway. :(
I have set the DNS entries for 192.168.1.253, then our main office DNS
server, then 4.2.2.1.
I realize this is a long explanation, but I really appreciate any
guidance you might have!! Thanks in advance!
.
- Follow-Ups:
- References:
- Prev by Date: Use BEFSR41 to join existing network infrastructure as DHCP server...help!
- Next by Date: Re: Use BEFSR41 to join existing network infrastructure as DHCP server...help!
- Previous by thread: Use BEFSR41 to join existing network infrastructure as DHCP server...help!
- Next by thread: Re: Use BEFSR41 to join existing network infrastructure as DHCP server...help!
- Index(es):
Relevant Pages
|
