|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
We just switched away from having the router 'rout', to having ISA
2006 route. SBS always did dhcp. The wireless broadband router is
now needing to just be a wireless access point/switch.
To accomplish this in the router, we only had to add a nic to sbs and
connect it to a lan port on the router. Wan is now to sbs's old nic.
Router's wan is now empty. The router is assigned an available static
ip.
In this config, the router is pingable from sbs but none of the
network machines can reach dhcp.
Router: Linksys wrt300n
SBS '03 updated but not R2
Here's what Linksys says:
http://forums.linksys.com/linksys/board/message?board.id=Wireless_Routers&thread.id=26177
Nick
|
|
Usually there is an option in the Router Config to turn off the Routing
functions and just use the Router in AP mode... I don't see this in a quick
flip through the manual.
It's probably cheaper ( time/money) to just go out and buy an $50 AP.
--
Henry Craven {SBS-MVP}
"Nick" <nick[ at ]mirrosoft.net> wrote in message
news:1183840703.455160.114530[ at ]o61g2000hsh.googlegroups.com...
[Quoted Text] > We just switched away from having the router 'rout', to having ISA > 2006 route. SBS always did dhcp. The wireless broadband router is > now needing to just be a wireless access point/switch. > > To accomplish this in the router, we only had to add a nic to sbs and > connect it to a lan port on the router. Wan is now to sbs's old nic. > Router's wan is now empty. The router is assigned an available static > ip. > > In this config, the router is pingable from sbs but none of the > network machines can reach dhcp. > > Router: Linksys wrt300n > SBS '03 updated but not R2 > > > Here's what Linksys says: > > http://forums.linksys.com/linksys/board/message?board.id=Wireless_Routers&thread.id=26177> > Nick >
|
|
In article <1183840703.455160.114530[ at ]o61g2000hsh.googlegroups.com>,
nick[ at ]mirrosoft.net says...
[Quoted Text] > We just switched away from having the router 'rout', to having ISA > 2006 route. SBS always did dhcp. The wireless broadband router is > now needing to just be a wireless access point/switch. > > To accomplish this in the router, we only had to add a nic to sbs and > connect it to a lan port on the router. Wan is now to sbs's old nic. > Router's wan is now empty. The router is assigned an available static > ip. > > In this config, the router is pingable from sbs but none of the > network machines can reach dhcp. > > Router: Linksys wrt300n > SBS '03 updated but not R2 > > Here's what Linksys says: > > http://forums.linksys.com/linksys/board/message?board.id=Wireless_Routers&thread.id=26177
First, since you mention "ISA 2006" I presume you are running this on
another server in the network since it's not supported on SBS 2003.
What you are trying to do is normally very simple - I reconfigure
wireless routers as APs all the time - so just to make sure I'm clear:
* Nothing is connected to the WRT300N WAN/Internet jack
* You've connected the WRT300N to the LAN-side of the SBS network via
one of the 4 numbered LAN jacks, either directly to the SBS internal NIC
or indirectly via an Ethernet switch to which the SBS internal NIC is
connected
* You've assigned the WRT300N an _available_ static IP appropriate to
your _LAN_ IP addressing plan (for example, if the LAN is using
192.168.16.??, the router is assigned 192.168.16.4, and that address is
not used anywhere else on the LAN)
* When you say "none of the network machines can reach dhcp", by
"network machines" do you mean only computers with wireless NICs or
something else (such as "all computers on the LAN")?
Given the above:
* Have you DISABLED the DHCP server on the WRT300N? You MUST do this or
you will have problems. (For the WRT300N, this is on the Setup | Basic
Setup page.)
* Have you verified the SBS DHCP Server service is started? And that it
has a reasonable configuration for your network (proper scope, etc.)?
* What wireless security features are enabled and how are they
configured?
-- Owen Williams (SBS MVP)
|
|
I'm not sure about new wireless routers but as short as a year ago, any
wireless router I've had could not be used as a WAP functionality wise.
Turning off the DHCP in the wireless router was just a means of connected
devices to use static IPs in different IP pools without any sort of
complications. WAP architecture is quite different, specifically in terms of
that it "expects" to be a relay(or bridging) system for a DHCP from a wired
interface to a wireless.
Your wireless router might be different and support this kind of
polymorphism but if it's causing your greif or taking up too much time, it's
a lot simpler to buy a WAP and clone the SSID and network security of the
wireless router. Plug the WAP into a switch that goes to the server DHCP and
the integration is seamless and simple. The WAP, by default, will just send
dynamic IP requests to the DHCP and is essentially "invisible" in the network
schema.
|
|
In article <04EDD3C2-EB7C-47BE-81A4-551454FAF8AF[ at ]microsoft.com>,
AndrewMcNab[ at ]discussions.microsoft.com says...
[Quoted Text] > I'm not sure about new wireless routers but as short as a year ago, any
> wireless router I've had could not be used as a WAP functionality wise.
> Turning off the DHCP in the wireless router was just a means of connected
> devices to use static IPs in different IP pools without any sort of
> complications. WAP architecture is quite different, specifically in terms of
> that it "expects" to be a relay(or bridging) system for a DHCP from a wired
> interface to a wireless.
>
> Your wireless router might be different and support this kind of
> polymorphism but if it's causing your greif or taking up too much time, it's
> a lot simpler to buy a WAP and clone the SSID and network security of the
> wireless router. Plug the WAP into a switch that goes to the server DHCP and
> the integration is seamless and simple. The WAP, by default, will just send
> dynamic IP requests to the DHCP and is essentially "invisible" in the network
> schema.
Definitely not my experience. I've reconfigured newer, older, business-grade,
and consumer-grade wireless routers as APs with no problem. In fact, I
normally acquire wireless routers for my very small and/or non-profit clients
because they tend to be easier to find than APs, are less costly than APs, and
include a switch which can be useful.
To convert a wireless router to a basic WAP, I've always just:
* Disable the DHCP server on the router.
* Ensure nothing is connected to the WAN/Internet jack (put a piece of
electrical tape over it if necessary).
* Assign the device a static IP suitable to the LAN addressing plan (for
example, if the LAN uses SBS-default 192.168.16.x addresses, you might
assign the router 192.168.16.4, assuming that address is available).
* Connect the router to the LAN (usually to another switch) via one of its
Ethernet switch jacks; the remaining jacks can be used as a switch on
the LAN.
That's it. Some wireless routers - for example, the (consumer-grade) Belkin
F5D7230-4 v1444, which dates to ~2004 or thereabouts - even include an option
on the admin pages to reconfigure the router as an AP. If you flash it with
the open source DD-WRT firmware, you can even reconfigure the WAN jack to be
part of the (now 5-port) switch.
-- Owen Williams [SBS MVP]
|
|
|