Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I have a wireless network that needs to be managed by my server 2003. The access points need to be directed to the IP address on the LANin order to find their config files. I need to know how to configure the server to point the APs back to that LAN IP address
Find their config files on the server?
No access point I have worked with does this. Their config is loaded from nvram on the device.
Or perhaps the language/terminology you are using is confusing. Do you mean to say you want the APs to get thier ip address from the server?
0 
Need a lot more information. As far as configuration files, the only devices I know of that have the ability to load config files from a server are Cisco Devices.
What kind of WAP are you using?
What kind of APP is going to access the device?
What Protocal does the APP use like SNMP?Or, is it a different problem all together? It seems that you may be asking how to rout the trafic on this device to the server? If this is the case then you can setup a static route on the Server to include the IP address of the WAP. This is done in CLI using the ROUTE ADD command.
We need some more details to help.
0
Hardware is Bountiful Wi-Fi. It is a controller that has 16 WAPs connected into a switch that is then connected back to the 2003 server. I would like the DHCP to be managed from my window 2003 server however all the APs are lightweight APs and need to get their config files from the controller. In order for the APs to get their config files they look for the LAN IP address. I need the 2003 server to be able to direct the APs back to the LAN IP in order for them to get their config files.
0
Where did the idea of using the 2003 server for this come from?
Apparently bountiful has a different idea about this. You need their wifi controller
http://www.bountifulwifi.com/Produc...
You don't mention routing so a route add would do nothing on the same subnet.
0
I have the controller and love it however the rest of my wired network is being managed by the 2003 server. I just need my wireless to get IPs from my server but still get directed to the LAN IP in order for it to get the config files On the controller they call it the next server IP address.
0
This is very confusing. Is your WAP only an Access Point or is it a Router/Switch/DHCP combo like most that you buy at a store. If it is then go into its configuration and turn off the DHCP services and then you computers will begin to get their IPs from the Server 2003.
The confusing part is that there should be conflicts if both this device and the Server 2003 are on the same subnet. That is why it is confusing. So would you tell us what the IP address is for the WAP and what the IP address is for the Server 2003? You could just give us the first 2 octets for security purposes and assuming you are using a 255.255.255.0 Subnet.
0
Nick Odom I understand what your desire but from what I read of the equipment that is not its design.
Reading the online pdf manual found here
http://www.bountifulwifi.com/BWRACW...it says under dhcp configuration
"specify the server from which clients should load the boot file. This is usually only needed with PXE booting and some VOIP phone and can usually be left empty."You would need to setup a PXE server. Only add on available from Microsoft is for Enterprise [which you are running] and is the Automated Deployment Services.
See here:
http://www.microsoft.com/windowsser...Configure the MS part and then you should be able to engage the next server ip function. There was nothing in the online manual that said how to then setup the devices to do the pxe boot but hinted it was in the full manual that came with the controller.
Though give some consideration to the complexity you are adding to your server and network. Complexity adds time to troubleshooting and increases the rate of failure.
0
I've got a similar set-up at a customers, though it's a 3Com system. There are 24 AP's connected and controlled by a layer 3 unified management switch. The advantage being roaming network and easy management and rebooting.
Just a warning... If you want to set up more than one wireless network, it involves setting up VLAN and should be attempted with caution because it's quite a large subject and could be very hard to grasp if you have no previous experience. Only use multiple networks if you need to.
The way I did it was configuring each and every one of the AP's to 'managed mode', then as long as there are a DHCP server (and free IP's) that responds to requests on your network the AP's should get dynamic IP's. They NEED TO be dynamic, that's important. If you hooked them up to the network and there was no DHCP server available, they probably have timed out and got a 169.x.x.x address or similar.
There should be a tool for finding these units on the network that lets you configure IP setup and all that too, you might wanna check that out.
If you let Win 2003 manage DHCP you should be able to see the units in the DHCP management under 'Leases'. As long as you see all of them there, they should be ready for configuration. You configure them from the controller, then when you apply settings it'll be pushed out to the AP's and they'll automatically reboot with the new settings.
Oh, and all your AP's must be connected to the controller, not necessarily directly to it, but from a hierarchy point of view the controller need to be highest. It can't control AP's that are connected to another part of the network.
0
Phatsta I think you missed the point of what Nick Odom
wants. Nick wants the control files for the AP to be pulled from the server not the AP controller.Your setup isn't using remotely loaded config file nor is there an AP controller. These are "lite" APs which from my reading don't have embedded controllers like regular APs but get their config from a central controller upon bootup.
0
Maybe I did, I just told him what kind of setup I worked with, and maybe it could be to some sort of help.
I haven't ever worked with any AP that gets it's config files from a pointed folder or anything similar, other than an AP controller so I'm throwing in the towel :)
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
