D-Link DIR-600 :: No Devices Listed On Number Of Dynamic DHCP Clients
Jul 27, 2012
I recently noticed my 'Number of Dynamic DHCP Clients' on Network Settings is always empty. Before, it always registered a list since there are several devices that are connected to our wireless network (laptops, mobile phones, desktops).
I'm having some issues trying to reserv an IP from my D-link DIR-825 router.I have set up a static IP on my computer: 192.167.0.10. But if i view the clients on my network that ip doesn't show up!
I have a few sites using the RV042 with wireless access points and some of them have over 50 devices.In reviewing the documentation (specifically,[URL]), I came across this:Enable DHCP server: Check the box to allow the router to dynamically assign IP addresses to up to 50 connected devices. Uncheck the box if you have another DHCP server on the network or you want to configure static IP addresses for your network devices.Is this accurate? Or will the RV042 allow more than 50 devices?
Just upgraded my system. I am using D-Link 615 as access point hardwired LAN to LAN to ActiveTec MI424WR N capable Verizon Fios Wireless Modem/Router. The Fios Router is set up with WPA2 security. Intend on having three 615s as Access Points off of ActiveTec. Have a number of wireless devices accessing the network. Have followed instructions from manual to use 615 as Access Point, disabling UPnP and the DNCP Server function on the 615. My ActiveTec IP address is 192.168.1.1 and I changed the 615 to 192.168.1.50. I can type this IP address in my browser and get to the 615 set-up.
I have tried a couple different options in naming the SSID on the 615 set-up. If I name the SSID on the 615 the same as the ActiveTec router, when I go to Connect to a wireless signal where there is overlap, there are two signals that one can connect to, named the same SSID, the Fios is WPA2 secured and the 615 is not. Shouldn't these all be on one SSID? It seems that I have two different networks (different SSIDs) instead of one (rather than the 615 simply serving as an extension of the Fios router as a wired remote access point) with different security protocols (WPA2 and None). The SSID name almost seems meaningless. If I name the 615 SSID the same as the Fios router SSID or something different, I still have the option of selecting one SSID that is secure and one that isn't. If I try to connect to the SSID name associated with the 615 I can get on without providing a password.How do I make it so that one can walk around and go from one area to the next and seamlessly move to the best signal? I did read to select different sets of channels for each access point.
We currently have an ASA 5520 communicating with 10 ASA 5510's, all on static outside addresses. I was asked to add 5 additional 5510's on dynamic address. All worked well in testing until it was decided that some of the dynamic clients needed to talk to each other.
I am currently using a DIR-655 for the home wireless network.DSL into a 2-Wire home portal (not wireless) and ethernet into the DIR-655.I need to connect a number of wired devices in a couple of different rooms. Some streaming HDTV content to other devices in other rooms. I'm thinking of the following:
-DIR-655 routing between the DSL subnet to the internet, the 2.4GHz wireless and a couple of wired devices.
-DAP-1522 routing between the 2.4GHz wireless, 5GHz wireless, and a few wired devices.
-DAP-1522 bridging between the 5GHz wireless and a few wired devices.
All devices will/may need internet access.HDTV content would be between wired devices and only over the 5GHz wireless (no HDTV to/from internet).Is the DAP-1522 the right device(s) for this?
'Use Unicasting' is selected by default in the Dynamic IP (DHCP) connection type.I turned it off based upon the router's support text since the router gets an IP address from my cable modem.I don't understand this option at all. I've searched for data on the topic and I can't make sense of it.I think I made the correct selection by un-selecting 'Use Unicasting.'
When I go into the Network Settings, and the end of the page I find a list named "Number of Dynamic DHCP clients: 7". As far as I know, I should only see 4, all 4 laptops; however, I see 2 UNKNOWN entries in this list, and one name "Macondo". Each of these entries have an option (a link) saying "Revoke" and other "Reserve". I am just wonder if these entries are intruders in my home network. What should I do? I am afraid to break my internet connection. By the way, I set up every single one of my family 4 laptops at home with a WPA-PSK using a very long key.
I've just discovered this thing in Windows Event log. The DHCP-Client log is full with this: the client received a NAK from the DHCP Server. Strangely, they still get the desired IP address. (Which are reserved adresses for the MAC adresses.)So I've looked at the logs in the DIR-615 (rev.D, FW: 4.13), and found this:
As I write this my iPad is connected to my Linksys router. However, my iPad is nor listed as a device in the list of all connected devices. All my other devices are listed just fine. Why I can't find my iPad?
I've noticed that my E4200v2 Smart-Wifi cloud doesn't show all the devices that are connected to my router.To test, last night we turned on EVERYTHING....4 iPod Touches, 2 Xbox's, 1 Blu-ray player connected to Netflix, 1 Directly receiver, 4 laptops,1 desktop,1 iPhone, and made sure all of them were connected to the Wi-fi and actually streaming / downloading/playing something the Smart WiFi only recognized about half of them as being connected. I rebooted the router and it picked up a few more but never accounted for all the devices connected.
If you can't account for all the devices connected to your network, setting-up up reliable Parental Controls is almost impossible.Very disappointed and about ready to start looking for another brand of router. Sad, as I've been with Cisco/Linksys for over a decade and been very satisfied in the past.
I have 25 APs 1141 located in ten floor building and connected to WLC 5508 ver 7.4.100.0. After upgrade from wcl 7.0.116.0 few clients start to complain that there are affected by periodic disconnection from wirreless network. It happens twice an hour. In WLC log I noticed some errors on almost every AP:AP with MAC: c4:0a:yy:yy:zz:xx(AP1) radio 0: Associated Clients falls below max limit number:200. Failure Cause:Clear Maximum Client Limit Reached in WLAN..What does it exactly mean? I have no limit per WLAN (it is set to 0), but in WLC 7.4 i must put some limit for numbers of clients per AP and the max is 200. It is not possible that i have 200 users connected to one AP as in 10 floors there are like 150 users maybe. Number of all connected clients right now is 120.
I have a high school wireless environment that was installed approximately 5 years ago with 1242AG APs. The install was done based on 2.4GHz coverage everywhere, not for 5GHz or for good density. The high school uses wireless cisco 7921G phones for all the staff and teachers. The issue we're running into is over the last couple years more and more students are bringing in iPhones and android phones that can connect to the public wireless ssid. And with the increase of these wireless devices in the classroom, we've been experiencing more and more call dropped on the wireless phones. I have collected information on number of clients on specific APs that are in the area of most of the dropped calls. At times some of these APs have a total of 40 clients associated to them, over half of which are on the public ssid. I have thought about putting all the phones on to the 5GHz radios, but the implementation of the wireless was only for 2.4GHz coverage, so we have coverage gaps on the 5GHz network. We're thinking about adding more APs but the budget isn't available yet for that, so we're looking at what we can do to make this better for the time being.
Main questions are:
Is there a best practices number of max clients per AP in a wireless voice network?
Are there any other options for preventing dropped calls on the wireless?
I should mention I have already looked over the VoWLAN Troubleshooting Checklist at the link below and made the necessary changes to assure we are following the items on the checklist as close as possible.URL
This may sound ignorant but I cannot get either of the antennas off my 615. They are listed as removable reverse SMA but they are so tight I am afraid of damaging it. This is my second 615 after not being able to get one of the antennas off the first. D-link said they should just unscrew but I cannot get either of them to budge. D-link support said the one I had first must have been manufactured wrong so I returned it to new egg and got a new one. Same issue. I need to have an external antenna on the unit.
I'm trying to use 802.1x to authenticate clients on my network with dynamic VLAN assignment from RADIUS. We have IP-Phones(powered by PoE) that only supports EAP-MD5, and we would rather use MAB(it also uses LLDP-MED for some settings) to authenticate the phones using the MAC-range from the phones vendor. The following scenario works perfect:Connect the phone and let it boot up(takes a while) and authenticate with MAB.Connect a computer in the phones data-port and let it authenticate with 802.1x(or fail and reach guest-vlan) However, the following scenario doesn't work:The computer is already connected to the phoneThe phone is then connected to the switch What happends now is that the computer is authenticated using 802.1x before the phone boots up and get's authenticated with MAB. When the phone is ready, it's authenticated with MAB and everything works. However, after a short period(let's say a minute), using `debug authentication all`, we see a "NEW LL MAC: phones mac" message(which is weird since the mac has already been MAB-authenticated), and then we are unable to contact the phone using ping. When I check `show mac address-table` it has now moved the mac from `Port Gi 0/12` to `Port Drop`. However, if I check `show mab interface Gi 0/12` or `show authentication sessions` it lists the phones-mac as `mab auth sucess `.why the first scenario works, and not the second?
The switch is a 3560E PoE 24p with IOS 12.2.58SE2. Sample of the switch-config: network-policy profile 1voice vlan 90!interface GigabitEthernet0/12switchport mode accessnetwork-policy 1authentication control-direction inauthentication event fail retry 1 action authorize vlan 60authentication event server dead action authorize vlan 60authentication event no-response action authorize vlan 60authentication event server alive action reinitializeauthentication host-mode multi-domainauthentication order mab dot1xauthentication priority mab dot1xauthentication port-control autoauthentication periodicauthentication violation replacemabdot1x pae authenticatordot1x timeout tx-period 5dot1x max-reauth-req 1spanning-tree portfast!Btw, when we tried authenticating the phones using 802.1x too (EAP-MD5), there are NO problems in any of the scenarios. However, we want to use MAB instead of 802.1x to avoid the requirement of configuring the phones with a username and password. The RADIUS response was the same when using 802.1x as it is with MAB for the phones (including device-traffic-class=voice AV-pair).
What is the maximum allowed number of wired clients behind a workgroup bridge? In other words, is there a limit on MAC addresses?I assume 1262 AP in WGB mode is connecting to a lighweight AP (1262 or 3502), latest IOS and WLC software. I wasn't able to find the answer from Cisco documentation.
I have just upgraded our WLC from 4.0 to 7.0 (via 4.2). Before the upgrade we had our ACS returning a VLAN based on user group. This seemed to be working without an issue. Now that the WLC is on version 7 this is no longer working correctly. The ACS is returning a VLAN and passing the user but the client can not get an IP from the DHCP server configured.
Example configuration:
SSID-----VLAN
PN-CSC-----CSCVlan: Works PN-Others------OthersVlan: Works
PN-Others-----CSCVlan: No DHCP
When users are trying to be allocated to a vlan that is different from the native one the DHCP fails however both WLANs are configured to point to the management interface so dont have any real connection to the vlan other than by name.
Have there been any changes I haven't seen in the way the dynamic vlan allocation works in version 7?
A small network and uses the Linksys Router BEFSR81 as dhcp.the default Number of addresses is 50 and starts 10.0.0.100 to 10.0.0.149.A new Cisco IP Phone just introduced requires ip addresses and have noticed running out of addreses.Can I increase the number to 120 so that the address range would start from 10.0.0.100 to 10.0.0.219, also, I have a VPN device which automatically configures itself for 10.0.0.199 address and this is /24 network configuration.
I wanted to know the maximum VPN client sessions (using the Cisco VPN client) and Site-to-Site VPN tunnels that I can connect to my ASA 5505 simultaneously.
In other words, if I have x VPN clients and y Site-to-Site tunnels, at any time, does x + y have to be <= 10 (Total VPN Peers)? If yes, can I upgrade to the security plus license to increase the Total VPN Peers to 25?
Licensed features for this platform: Maximum Physical Interfaces : 8 VLANs : 3, DMZ Restricted Inside Hosts : Unlimited Failover : Disabled VPN-DES : Enabled [Code]...
I'm monkeying around with an 881-W. Clients can associate and authenticate to ssid 'test', but they cannot get a DHCP address. Clients plugged into f 0 - 3 get DHCP addresses just fine.
I've looked at a lot of different guides, ran debugs etc. When wifi clients make DHCP requests the server never gets them. So there must be some IRB thing going on.
I have successfully configured my DHCP server because I can ping it from the clients PC and my clients PC automatically grabs IP from my DHCP. How my clients can have access to internet. Here is my hardware setup: 1. I connect clients PC and one DHCP server in one unmanaged switch2. I have my Bell DSL Modem but not connected yet to one of these machines. I do not know how I can configure it yet to work with my machines.The IP I assigned started at 10.10.200.10 to 10.10.200.90How do I connect the DSL and configure so that it may give everyone access to internet?
I'm trying to understand my options for assigning addresses to VPN clients on an ASA 5510. Under the ASDM, I have a field for DHCP servers, radio buttons: none, dhcp link, dhcp subnet, and field: client address pools. Cisco's VPN examples demonstrate setting up a client address pool, which I did, but the VPN client isn't assigned a gateway in the process so it can't connect to anything; I really don't understand the point of this. I'd like to create a DHCP pool on the ASA for VPN clients as this seems to be the standard configuration. However, I don't know where in the ASDM to configure this and how it's applied. The only DHCP options I found involved creating a DHCP server on an interface, which I don't want to do since VPN users aren't on a physical interface, right?
I have new 2504 WLC + 1041LAP. I configured the first DHCP scope on WLC and the first WLAN. Then I set WLC DHCP server in WLAN properties and tried to connect to WLAN with wireless clients.
My wireless clients are able to authenticate on WLAN, but not able to get IPs from DHCP. The only lease that DHCP shows is for 1041LAP.
If I set permanent IPs on my wireless clients, they can connect and ping WLC.
When on the management interface the clients can't get dhcp but the AP's can on the same vlan. I've tried enabling and disabling dhcp proxy, and using a remote dhcp server as well as the internal server. This same config works on the 4402 we're replacing with version 5.2.193 on it.
I've got a 2106 that I'm installing for a customer and having issues with it assigning DHCP to WiFI clients. What's odd is that this was working at one point at home during testing. Only difference at this point is LAN hardware at the customer location.
Simple config- single flat vlan on Cat2960G switch, ASA5505 serving up DHCP for the network. Wired clients are receiving DHCP fine.
Mgmt IP192.168.0.10/24Mgmt Gateway192.168.0.1Mgmt VLAN0Mgmt Int port1Mgmt DHCP server192.168.0.1AP Mgr Int IP192.168.0.11Virtual GW IP1.1.1.1RF group namerfgrp1SSIDxxxxClient Static IP?noCountry Code802.11a/b/g statusenabledRadio resource mgmt statusenabled I've run dhcpd debug on both the controller and the ASA and I see the DHCPD requests on the controller, but I never see them hitting the ASA.
I don't have the specific version of code it's running, but I know it's 6.0. One of my local Cisco account engineers found some Cisco CSC bugs referencing this issue. One TAC cas even referenced stripping all security off the WiFi, connecting the client and then reimplementing the security again.
My company AP 1231G is not passing the DHCP address to the client from the DHCP server, my config listed below basicly the AP is on its own VLAN 10.1.123.1 and the DHCP server is 10.1.10.2 -- trying to use iphelper to pass DHCP to clients and the AP is on static IP 10.1.123.2--
! ! Last configuration change at 13:15:56 +0800 Fri May 25 2012 by root ! NVRAM config last updated at 13:15:56 +0800 Fri May 25 2012 by root !
I recently upgraded a clients WLC and they keep saying they are unable to get an IP address from the DHCP server. It's a simple, flat network and here is what the logs are showing.
*apfReceiveTask: Apr 11 13:37:25.477: %SIM-3-DHCP_SERVER_NO_REPLY: sim_interface.c:1039 Failed to get DHCP response on interface 'management'. Marking interface dirty. *apfReceiveTask: Apr 11 13:37:17.278: %SIM-3-DHCP_SERVER_NO_REPLY: sim_interface.c:1039 Failed to get DHCP response on interface 'management'. Marking interface dirty. *apfReceiveTask: Apr 11 13:37:05.880: %SIM-3-DHCP_SERVER_NO_REPLY: sim_interface.c:1039 Failed to get DHCP response on interface 'management'. Marking interface dirty. *apfReceiveTask: Apr 11 13:13:47.397: %SIM-3-DHCP_SERVER_NO_REPLY: sim_interface.c:1039 Failed to get DHCP response on interface 'management'. Marking interface dirty.
I would like to share one problem with WLC 5508 . we added a new virtual interface on the WLC. One new SSID is associated with this interface.
We created a ACL for this interface to restrict the access via WIFI to certian services. It´s not correct that everything works fine because the change were not applied. [code]
The changes of the ACL are applied on the fly, but for reason we don´t know, the clients don´t get a DHCP IP-Address (after changing the ACL) until the Controller is rebooted.