Hi

Just wondered if you could help, I am looking to setup public access wifi in a nearby hotel, but can't work out how to integrate it in to the hotel.

The hotel has an SBS 2003 domain running on a 192.168.0.x network with a netgear router for internet access on 192.168.0.1 running dhcp (sbs not handling dhcp all done via router) ideally i'd like to add the wireless network on a 10.0.0.x address but still to go out via the same broadband router

My wireless network will consist of a couple of access points going back to a filtering pc to handle clients logging in for wireless internet then ideally connect the filtering pc to hotel router. Thus keeping it separate to the SBS domain.

Just wondered what your network configuration suggestion for this setup would be. The SBS domain is supported by a separate IT company and i'd rather leave their setup as it is.

Many Thanks

Because of the existing router you can not use any other subnet unless you are going to put in a router.

Ideally you would have a managed switch which supports vlans. Config would look like:

router<>managed vlan switch<>sbs network on vlan1 and wireless network on vlan2.

But then you mention a filtering pc. It would have to have two nics so it would be a router. Config would like like this:
router<>sbs lan
router<>filtering pc<>wirless lan

Then you could do your 10.x.x.x. [why that subnet (16million ips) who knows since most wireless aps only support 254 connects max so you should stick to a class c private ip]

Imagine the power if you knew how to internet search

Many thanks for your reply,

option 2 seems best since I want to use a filtering pc, but how do I configure the two NICS to act as a router?

Would it be best to BRIDGE them or could I use the ROUTE ADD command and point the 10.x.x.x wireless network to the 192.x.x.x network?

I dont want anyone on the public wireless side to be able to browse the private SBS side...

I agree with wanderer that most wireless aps only support 254 connects max but for communication efficiency, only 20 to 30 computers can be connected to one access point at any given time. More than that lag will set in.

i_Xp/VistaUser

ok, so if I give the filter machine and access points on the public wireless network 192.x.x.x addresses, how can I stop the wireless users being able to browse the private SBS network?

You would want to engage ICS on the filtering machine to route between 192.168.0.x and the ap side of 192.168.1.x

Be clear in your understanding. Your lan is 192.168.0.x whereas your AP wireless lan is 192.168.1.x. Two very different subnets.

Unless you ADD a route, once the AP traffic hits router1, there isn't a path back to the SBS of the lan.

Personally I prefer vlans in this situation but you can always add that down the road.

Imagine the power if you knew how to internet search

Normally I would have used ICS on the filtering pc but the main router has dhcp enabled which ICS won't work with...

can I set router2 to 192.168.5.1 then use the static route option in the router to point it to router1?

"can I set router2 to 192.168.5.1 then use the static route option in the router to point it to router1?"

No. How is your router at 192.168.0.x going to route to a different 192.168.5.x
subnet?

Routing works like this:
ipA<router>ipB1<>ipB2<router>ipC
What you are asking is:
ipA<router>ipB1 and ipC<router>

There is this really cool thing called ip reservations or static ip.
1. you can reserve a ip in the router to only be assigned to that nics mac address [also known as mac filtering]
2. static ip. You change the dhcp scope in the router to exclude the static ip you assign to ICS filtering pc.

Darn. Just realized ICS ip default is 192.168.0.1. You will want to use RRAS instead. See here
http://www.windowsnetworking.com/ar...

Imagine the power if you knew how to internet search

Hi many thanks for your comments, from the information you gave me have successfully set up the netwrok I was planning, ended up using a linksys router and adding it to the other network via its WAN port all sorted now.
Thanks again