Re: wireless access point - WNR2000 router

how about a little white space...

"sid" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi all
> Not posted here before but there seems to be some life in this newsgroup.
> We have an internal wired network that DOESN'T use DHCP. All the client
> windoze machines have their IPs set uniquely & their gateway & DNS
> settings
> pointing at a proxy server that gives internet access. I need to add
> wireless capability to this network. So the access point has to be able to
> have a hardwired IP, gateway & DNS setting on it's wired side in the same
> way as all the existing clients and ideally it will have its own DHCP
> server
> on its wireless side. Is this possible, is there a name for this
> particular
> function & if so are there any recommendations for a box that will do
> such.

any normal wireless access point will perform these functions.

> The boss has already wasted money on a wnr2000 Netgear router that,
> presumably because it's a router doesn't seem to do the trick

all you needed was an "access point" not a router - which just confuses the
issue
http://www.netgear.com/Products/Rout...s/WNR2000.aspx
you do understand the difference between a "wireless router" and "wireless
access point" ?
If you wanted to just add a "wireless access point", why did the boss
purchase a "router" ?

> once you set
> its IP address for the internal network it just seems to disappear.

exactly how did you physically connect the "router" - which port did you use
?
what does that mean - disappear ?
you no longer see the IP address and can't ping it from the wired side ?

> I've
> tried googling for wireless access point comparisons but the only info
> that
> features in the results is speed, good looks & not obscure configuration
> abilities.
>

On Wed, 24 Feb 2010 08:57:46 -0600, "ps56k"
<(E-Mail Removed)> wrote:

>"sid" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>
>> The boss has already wasted money on a wnr2000 Netgear router that,
>> presumably because it's a router doesn't seem to do the trick
>
>all you needed was an "access point" not a router - which just confuses the
>issue
>http://www.netgear.com/Products/Rout...s/WNR2000.aspx
>you do understand the difference between a "wireless router" and "wireless
>access point" ?
>If you wanted to just add a "wireless access point", why did the boss
>purchase a "router" ?

Many wireless routers are less expensive than access points, so maybe
there were budget considerations in addition to some general
confusion. As we know, wireless routers can easily be configured as
access points, (but the reverse isn't true.)

"Char Jackson" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Wed, 24 Feb 2010 08:57:46 -0600, "ps56k"
> <(E-Mail Removed)> wrote:
>
>>"sid" <(E-Mail Removed)> wrote in message
>>news:(E-Mail Removed). ..
>>
>>> The boss has already wasted money on a wnr2000 Netgear router that,
>>> presumably because it's a router doesn't seem to do the trick
>>
>>all you needed was an "access point" not a router - which just confuses
>>the
>>issue
>>http://www.netgear.com/Products/Rout...s/WNR2000.aspx
>>you do understand the difference between a "wireless router" and "wireless
>>access point" ?
>>If you wanted to just add a "wireless access point", why did the boss
>>purchase a "router" ?
>
> Many wireless routers are less expensive than access points, so maybe
> there were budget considerations in addition to some general
> confusion. As we know, wireless routers can easily be configured as
> access points, (but the reverse isn't true.)

less expensive - yeah... just noticed that in comparing this Netgear router
to a WAP54G
BTW - on the Netgear site, they don't even have/list just WAP's -


>

"Bob" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On 24/02/2010 21:29, ps56k wrote:
>
>> BTW - on the Netgear site, they don't even have/list just WAP's -
>
> Did you just look at the "Home Networking" page?
>
> <http://www.netgear.com/Products/APsWirelessControllers/AccessPoints.aspx?for=Business+Networking>
> <http://www.netgear.co.uk/office_wireless_access_points.php>
>

oops - missed it for some reason -
it was over on the far right side below the Storage section -
http://www.netgear.com/Products.aspx

"Bob" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On 26/02/2010 11:08, sid wrote:
>> Sorry to have been offline for a day and thanks for your interest.
>>
>> "ps56k"<(E-Mail Removed)> wrote in message
>> news:hm3epg$vpc$(E-Mail Removed)...
>>> how about a little white space...
>>>
>>> "sid"<(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> Hi all
>>>> Not posted here before but there seems to be some life in this
>> newsgroup.
>>>> We have an internal wired network that DOESN'T use DHCP. All the client
>>>> windoze machines have their IPs set uniquely& their gateway& DNS
>>>> settings
>>>> pointing at a proxy server that gives internet access. I need to add
>>>> wireless capability to this network. So the access point has to be able
>> to
>>>> have a hardwired IP, gateway& DNS setting on it's wired side in the
>> same
>>>> way as all the existing clients and ideally it will have its own DHCP
>>>> server
>>>> on its wireless side. Is this possible, is there a name for this
>>>> particular
>>>> function& if so are there any recommendations for a box that will do
>>>> such.
>>>
>>> any normal wireless access point will perform these functions.
>>>
>>>> The boss has already wasted money on a wnr2000 Netgear router that,
>>>> presumably because it's a router doesn't seem to do the trick
>>>
>>> all you needed was an "access point" not a router - which just confuses
>> the
>>> issue
>>>
>> http://www.netgear.com/Products/Rout...utersandGatewa
>> ys/WNR2000.aspx
>>> you do understand the difference between a "wireless router" and
>>> "wireless
>>> access point" ?
>>
>> My networking skills are such that I wouldn't be certain of the
>> dictionary
>> definitions but realise that a router is probably overkill for this
>> situation.
>>
>>> If you wanted to just add a "wireless access point", why did the boss
>>> purchase a "router" ?
>>
>> Cos he's the boss ;-)
>> This happened before he involved me to try& sort things out.
>>
>>>
>>>> once you set
>>>> its IP address for the internal network it just seems to disappear.
>>>
>>> exactly how did you physically connect the "router" - which port did you
>> use
>>> ?
>>
>> One of its LAN PORTS linked into the internal network.
>>
>>> what does that mean - disappear ?
>>> you no longer see the IP address and can't ping it from the wired side ?
>>
>> Yes just that. Only way to get it back is to press the reset button&
>> lose
>> all the settings. One thing I am a little confused by with this box is
>> that
>> there is an IP addr under basic settings& then there's another one under
>> LAN settings& I'm not really sure what should go where.
>>
>> Thanks
>>
>>
> The IP address under basic settings will be the WAN port address. You will
> need to go to the LAN configuration settings to set the LAN IP address to
> one that corresponds to your network.
> What OS are the laptops going to use?
> If they are using Windows there is no need to use DHCP in the router or
> trying to get DNS to work there. If the laptops are also used elsewhere
> you can set them up to use DHCP for outside use but for your own network
> you could use the alternate config settings in TCP/IP to specify IP
> Address, gateway and DNS settings.
> see bottom of page:-
> <http://www.home-network-help.com/set-ip.html>

grabbing the manual -
ftp://downloads.netgear.com/files/WN...UM_24FEB09.pdf

yup -
the Basic Settings on section 1-4 - is for the WAN connection to an ISP

the Customize Network Settings on section 4-1 is the local LAN side.
(defaults to 192.168.1.1)

BTW - what IP address scheme are you using for the rest of your wired
network ?
ie - like 192.168.1.xxx ?

Since you have a small network -
just make sure that any DHCP address ranges are reset for just a couple of
devices,
are NOT being used by your wired static IP devices...

On Fri, 26 Feb 2010 11:08:51 +0000, sid wrote:

> "ps56k" <(E-Mail Removed)> wrote in message
> news:hm3epg$vpc$(E-Mail Removed)...

>> you do understand the difference between a "wireless router" and
>> "wireless access point" ?
>
> My networking skills are such that I wouldn't be certain of the
> dictionary definitions but realise that a router is probably overkill
> for this situation.

At this level, the difference between the two is very little. The router
will have it's LAN switch and wireless bridged together, an AP will have
it's single LAN port and wireless bridged togther. The router will have a
port labelled WAN and if you ignore it and turn off DHCP you will have
yourself an AP.

>> If you wanted to just add a "wireless access point", why did the boss
>> purchase a "router" ?

The economics of it mean that things labelled 'router' are cheaper than
things labelled 'AP', even though the chips inside and OS are virtually
identical.

> Cos he's the boss ;-)
> This happened before he involved me to try & sort things out.

'twas ever thus!

--
<http://ale.cx/> (AIM:troffasky) ((E-Mail Removed))
16:13:29 up 22 days, 8:35, 4 users, load average: 0.03, 0.16, 0.14
DIMENSION-CONTROLLING FORT DOH HAS NOW BEEN DEMOLISHED,
AND TIME STARTED FLOWING REVERSELY

>>
>> grabbing the manual -
>> ftp://downloads.netgear.com/files/WN...UM_24FEB09.pdf
>>
>> yup -
>> the Basic Settings on section 1-4 - is for the WAN connection to an ISP
>>
>> the Customize Network Settings on section 4-1 is the local LAN side.
>> (defaults to 192.168.1.1)
>>
>> BTW - what IP address scheme are you using for the rest of your wired
>> network ?
>> ie - like 192.168.1.xxx ?
>
> Yes that exactly ^
>
>>
>> Since you have a small network -
>> just make sure that any DHCP address ranges are reset for just a couple
>> of
>> devices,
>> are NOT being used by your wired static IP devices...
>>
>
> I assume that a DHCP server never blindly allocates an addr without
> sniffing
> to see if it's being used by a static device first? In any case, I see the
> Netgear box can be set to only allocate addrs between certain ranges if
> the
> above is a problem.
>
> I can only access the premises where this gear is at odd times so my next
> chance to attack it won't be until Monday.
>

DHCP just assigns - it has no idea what else you are doing -

that's why I said to reset the rangle....
it's kinda dumb for the Netgear default
to assign the entire IP range to DHCP

Also - don't overlap DHCP servers
by having more than 1 server assigning in the same IP range.

On 2/26/2010 12:43 PM, DanS wrote:
>> I assume that a DHCP server never blindly allocates an addr without
>> sniffing to see if it's being used by a static device first?
>
> Your assumption is most likely wrong.
>


Depends, some (many?) can be set to do conflict detection.

> (I am not fully aware how all DHCP servers in all devices work, maybe some
> do check, but I've never seen it.)