Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

BT Business Hub 2700G with Windows Server 2003 DHCP - wireless?

apfitch
Member

on ‎02-07-2011 11:33 AM

Hi, we're a small charity with a computer network using Windows Server 2003 and a BT 2700 Business Hub. We've had problems with name resolution on our private network, so recently I re-organised as follows:

 

Disabled DHCP on the business hub

Enabled and set up DHCP on Windows Server 2003.

Set the Windows Server to use the hub as the gateway.

 

This works in our wired network.

 

What I don't understand is the wireless access. The BT Hub gives out wireless addresses in 192.178 subnet, which is different from our private network (which is on 169.254 for historical reasons!).

 

In the original setup, the wireless access point have access to the internet. Now wireless devices can't connect, presumably because the 2700 is no longer in charge of DHCP. I'm not sure what I should do to get things to work again, short of reverting to using router for DHCP.

 

I might be able to set up another DHCP zone on the Windows server.

 

I also don't understand where the address range (192.178) for wireless routing is set in the 2700.

Any ideas?

 

regards

Alan

 

Southampton Hospital Broadcasting Association

0 Kudos
2 REPLIES 2

helpinghands
Power User

on ‎02-07-2011 01:21 PM

It sounds like you are connecting to the fusion network instead of the wireless network. In view avaliable networks you should have a wireless connection that  is called BT Business hub xxx. The xxx will be the last 3 digits of the serial number of the business hub. This is the one you should be connecting too.

0 Kudos

apfitch
Member
In response to helpinghands

on ‎03-07-2011 11:26 AM

Hi Helpinghands,

  no, it doesn't matter whether you use "fusion" or "wireless". In fact I got the subnet wrong in my original post, it's 192.168.178. But that's still different from the subnet we allocated on the wired lan side.

 

I guess when the 2700 is running dhcp itself, it somehow creates a route from one subnet to the other.

 

If you look in "static routes" on the 2700, there are lines like this:

 

169.254.61,1         255.255.255.255    169.254.61.1          bridge0

192.168.178.254   255.255.255.255    192.168.178.254    bridge4

169.254.61,0         255.255.255.255    169.254.61.1          bridge0

192.168.178.0       255.255.255.255    192.168.178.254    bridge4

 

which I guess is how the two subnets get linked. So I guess if I set up a new zone in the Windows 2003 server for 192.168.178, and assuming dhcp requests get routed to the server, it may work?

 

regards

Alan

 

0 Kudos