Re: how to configure SBS2003 to accept WIFI clients

Hi Roberto,

Plain old access point should work. When you configure the new wireless
router though, you will need to be on the same default subnet initially
(192.168.1.1 or whatever the default it). Then you can configure the WAN
port on router to a static IP on the 10.0.0.x subnet and hook it to your LAN.
Then you can configure it to use DHCP for whatever local subnet (which
should only be wireless clients and the 4 ports on the device itself) with
the SBS server as the DNS.

So basically, your setup for the locally connected wireless router would
look like:

Notebook physical NIC - (10.0.0.x by DHCP from SBS server)
Notebook wireless NIC - (10.0.10.x or whatever subnet you configure from
wireless router)

Wireless router LAN - (10.0.10.1 or whatever) - Needs DHCP if you want or
you can statically assign wireless clients
Wireless router WAN - (10.0.0.200) - Connected to the local network with
10.0.0.1 as the gateway -- make sure DNS servers are set to 10.0.0.1 or you
will have trouble.

Let me know if that works!

Stu



"Roberto" wrote:

> Hi Stu
> thanks for the info, yes you have a true picture of my setup the
> diferent subnets seems to be the problem.
>
> No1 would apear to be the best option all round, cost and easy of
> implementation, Linksys have the WRT54G that I could hook up to a
> spare port on the switch to do the job. Would a plain old access
> point be suficient here ? I have one on hand I could use.
>
> No2 isn't an option - for security reasons
>
> No3 not sure, but I seem to remember having problems when I tried to
> configure the router for a 10.0.0.X subnet once before.
>
> I assmue I will be able to access the WRT54G via a web interface to
> configure it to the 10.X.X.X subnet ?
>
> Some added info for you
> If I configure the Notebook with static values that reflect the LAN IP
> etc, it sees the domain but shares , web etc are unavailable
>
> rgds
> Robert
>
> "Stu" <Stu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:4734D956-70A8-461C-9EC9-770EC6C534B5@xxxxxxxxxxxxxxxx
> > Hi Roberto,
> >
> > So as I understand it, your setup is as follows:
> >
> > Server NIC 1 - 10.0.0.1 (LAN)
> > Server NIC 2 - 192.168.16.2 (WAN)
> >
> > Router - 192.168.16.1 - (LAN)
> > Router - ??? - (WAN to ISP) Don't need to know this.
> >
> >
> > Server NIC 2 is hooked up to your router and server can ping the router.
> > When the notebook is physically hooked up to the 10.0.0.1 network, it
> > works
> > fine. When you try to connect wirelessly to the router though, no good.
> > The
> > issue here is that if you connect via wireless, you'll have to be on the
> > 192.168.16.1 subnet and that subnet won't know anything about your local
> > network (since it can only see 192.168.16.xxx). You have three options
> > that
> > I can see...
> >
> > 1.) Don't use the wireless on your gateway, instead buy another wireless
> > router and hook it to the lan to broadcast that network - should cost
> > about
> > 50 bucks
> >
> > 2.) Don't use the NIC2 on your server and reconfigure your router to
> > attach
> > to NIC1...this will work and just costs time and potential security
> > concerns
> > depending on how thorough you lock down SBS
> >
> > 3.) Reconfigure your router to attach to the lan and buy a DSL or Cable
> > modem to attach to server NIC 2 directly.
> >
> > If anyone else has ideas, feel free to post. In my mind though, I don't
> > see
> > how you'll be able to have the notebook hook up to both networks without
> > having to reconfigure their mail, shares, etc each time which seems like a
> > less-than-optimal solution as the network is currently setup.
> >
> > Stu
> >
> >
> > "Roberto" wrote:
> >
> >>
> >> Stu
> >> thanks for the reply, here are some more details of my setup and
> >> results of ping
> >>
> >> DHCP is disabled in the router
> >> ping 192.168.16.1 [router] gives "destination host unreachable"
> >> ping 10.0.0.1 [server] gives "destination host unreachable"
> >> Server has 2 NICs:
> >> Security mode 10 digit WEP key [same results with no secvurity set]
> >> SSID set to broadcast
> >> Wireless network access set to : allow all
> >>
> >> LAN 10.0.0.1 /255.0.0.0
> >> Default Gateway blank
> >> DNS Servers 10.0.0.1
> >> Primary Wins Server 10.0.0.1
> >>
> >> WAN 192.168.16.2 /255.255.255.0
> >> Default Gateway 192.168.16.1
> >> DNS Servers 10.0.01
> >> Primary Wins Server 192.168.16.2
> >>
> >> rgds
> >> Robert
> >>
> >>
> >>
> >>
> >>
> >> "Stu" <Stu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:2ECFE777-52C3-483E-A29A-E9DE08BF5DF6@xxxxxxxxxxxxxxxx
> >> > Hi Roberto -
> >> >
> >> > If you're having limited connectivity - it likely isn't related to SBS
> >> > at
> >> > all but rather your connection to your wireless router or network
> >> > setup.
> >> > What type of wireless router are you using? I assume it's on the same
> >> > network segment as your SBS server so if that's correct, is your router
> >> > acting as a DHCP server or is SBS (or both!?)? When you connect via
> >> > your
> >> > wireless network, can you ping the router or are you not getting that
> >> > far?
> >> > If we can have a little more info, I'm sure we can narrow down your
> >> > problem.
> >> >
> >> > Stu
> >> >
> >> >
> >> >
> >> >
> >> > "Roberto" wrote:
> >> >
> >> >> Trying to setup a client Notebook to access a domain using WIFI
> >> >> with
> >> >> 64 bit WEP Key, the Notebook will access the Domain via Cat5
> >> >> Cable
> >> >> OK.
> >> >> I have tried using server assigned & static IP/ Def G /Prefered
> >> >> DNS.
> >> >> Using static IP etc the Notebook says it's connected for 2 or 3
> >> >> seconds then says limited connectivity,
> >> >> Need help !
> >> >>
> >> >> SBS2003 with SP1
> >> >> XP PRO Acer 4064 Notebook with SP2
> >> >> Linksys WAG54G router/AP
> >> >>
> >> >> rgds
> >> >> Robert
> >> >>
> >> >>
> >> >>
>
>
>
.

Relevant Pages

  • Re: 2 NIC SBS2003R2 LAN/WAN Firewall Router Connection Failure
    ... I have to admit to a preference for VMWare Server which can only be ... I've asked the other SBS MVP's to comment on the current status of SBS ... I connected directly to the router and changed its LAN side subnet ...
    (microsoft.public.windows.server.sbs)
  • Re: Running out of IP addresses
    ... In fact it is pretty hard to find a hardware LAN router these days. ... I think it worth planning a second subnet at this stage as I can see the existing scope running out, even with a 'full range' on the current subnet. ... I understand that I will need to introduce a DHCP server on the second subnet. ...
    (microsoft.public.windows.server.networking)
  • Re: Using DHCP to separate activity?
    ... Server 2003 even if they are on the HCL for ... You could then connect the current router to the second NIC ... internal wireless devices. ... Cascading a Linksys Router to Another Linksys Router ...
    (microsoft.public.windows.server.sbs)
  • Re: route trafic from external to internal adapter
    ... I am remoting into networks through PPTP and RDP and am on a subnet not ... behind o f SBS Server. ... gateway and proxy server for 192.168.30.x client computers. ... If the default gateway for 192.168.30.11 is to the RRAS router and the ...
    (microsoft.public.windows.server.networking)
  • Re: How do I create/configure a secure wireless network for my office AND allow customers to connect
    ... I have one laptop that is wireless, ... and load it into the router, the first time they use your network. ... wireless subnet, ...
    (comp.sys.mac.comm)
Quantcast