Re: Help setting up SBS 2003!!!!!

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



It's not that you can't do it. You usually can. Just eliminates a few
variables and likely sources of frustration to use something designed
as an AP, that's all.


On Feb 6, 9:37 am, Joe <j...@xxxxxxxxxxxxxx> wrote:
Candace Sparks wrote:
I did not realize that the DSL modem was a router. The client wants
wireless access for a few laptops, that is why the Linksys router. I will
try and make the router work, otherwise I will entertain your suggestion.
Thanks for your help!

I can't imagine why a wireless router couldn't be used as an access
point. My main client has two DG834s, one of which provides DSL and
wireless, the other is a backup unit which also provides more wireless
on a different channel to an area of the office where the coverage
from the first is a bit flaky.

I assume these laptops will participate in domain activity, so that
router needs to be connected to the LAN switch/hub. Talk to it first
one-to-one with a computer set to get IP information by DHCP, and
change the router's network address to suit the LAN. Ideally give it
an unused address within the SBS DHCP pool, and mark that as reserved
in the SBS DHCP manager. Turn off the router's DHCP before connecting
it to the LAN, as the SBS will shut down its own server if it sees
another one.

As to IP addresses, I'd recommend changing the 10.0.0.0 network. At
some point in the future, you may need to use a VPN, and all networks
involved need to be different. There is only one 10.0.0.0 address
space, so everyone who uses it shares that one. I'd also recommend
using the server IP address change wizard to move that one. 192.168.16.
is the default SBS LAN network, and many people won't change it from
that. I'd suggest using 'mid' 192.168. networks for both LAN and SBS
external NIC, as 192.168.0., 192.168.1., 192.168.16. and 192.168.254.
are common defaults.

The wireless clients might need to make the first logon on wires, as
some people have had trouble with DHCP over wireless the first time.
It's probably a good idea anyway, as the user profile will be copied
over the first time, and wires are generally faster, and if there are
any logon issues you have at least eliminated the wireless bit.


.



Relevant Pages

  • Re: Networking Question - VLANs on SBS 2003 Premium SP1
    ... DHCP running on the router. ... Set the DHCP on the router, to make a exclusion of IP range. ... you can set the SBS use fix IP by run the CEICW. ... all gust wireless clients will get IP address from DHCP on the ...
    (microsoft.public.windows.server.sbs)
  • Re: Networking Question - VLANs on SBS 2003 Premium SP1
    ... Finally was able to get some network downtime to make the change in routers ... wireless router, but - once connected to the SBS box and I've run CEICW, the ... I ran the ISA and SBS BPA's and didn't see anything. ... I put the old router back in service so I could work on this some more. ...
    (microsoft.public.windows.server.sbs)
  • Re: Wireless connects but only partially
    ... So the wireless access point is going to use a fixed IP address in the same range as the SBS - 192.168.1.x, and that's going to be an IP that's excluded from your DHCP scope so DHCP doesn't hand it out to a different device. ... Now, the connection is passing from the client PC through the WAP to the SBS, exactly as the wired connection passes through the Ethernet switch to the SBS. ...
    (microsoft.public.windows.server.sbs)
  • Re: Networking Question - VLANs on SBS 2003 Premium SP1
    ... DHCP running on the router. ... Set the DHCP on the router, to make a exclusion of IP range. ... you can set the SBS use fix IP by run the CEICW. ... all gust wireless clients will get IP address from DHCP on the ...
    (microsoft.public.windows.server.sbs)
  • Re: Wireless Network Issue - SBS2K3 - Configuration and / or Topol
    ... I am quietly confident that moving the SBS to ... and the SBS is the DHCP/DNS server - but everything else in my house is ... wireless and it works fine. ... cause is incorrect network configuration and / or hardware topology. ...
    (microsoft.public.windows.server.sbs)