No ip address for wifi devices

Hello,
We have an Cisco WAP561 (Firmware 1.1.0.4) in our network. The problem is, after a while the connected device's are not getting a DHCP address from the DHCP server anymore.
The DHCP server is a Windows Server 2012 R2 with the DHCP role installed. No NAP configured or installed.
Network: 172.16.0.0 MASK 255.255.0.0
The Cisco is connected to a HP E2620-24-PoEP Switch(J9625A) without additional vlan's (only vlan1)
I've connected the access point to a syslog server and can see that the devices are connecting. See logging below
Nov 15 11:13:58 hostapd[888]: STA 80:be:05:68:89:2d associated with BSSID 18:9c:5d:39:3e:80
Nov 15 11:13:58 hostapd[888]: Assoc request from 80:be:05:68:89:2d BSSID 18:9c:5d:39:3e:80 SSID Technoberg
This is a log from the dhcp server:
11,11/15/14,11:13:59,Renew,172.16.15.132,iSander.domein01.local,80BE0568892D,,3105213757,0,,,,,,,,,0
The problem is not signal strength, I've tried moving the devices close to the access point. I also tried other devices: laptops, several smartphones.
After like +-7 days the devices are not receiving an ip address anymore. After we reboot the accespoint the devices receive ip addresses again.
Thank you in advance.

Thank you for your reply.
I did the following:
1. Used port mirroring for the port the cisco is connected on
2. Used the tool you suggested (network monitor)
I can see the DHCP discover message. See logging below (I filtered on protocol DHCP):
35 12:11:07 18-11-2014 1.5023283  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E62 {DHCP:21, UDP:23, IPv4:22}
36 12:11:07 18-11-2014 1.5023283  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E62 {DHCP:21, UDP:23, IPv4:22}
37 12:11:07 18-11-2014 1.5031573  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E62 {DHCP:21, UDP:23, IPv4:22}
38 12:11:07 18-11-2014 1.5039504  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E62 {DHCP:21, UDP:23, IPv4:22}
318 12:11:12 18-11-2014 6.4799871  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E63 {DHCP:92, UDP:23, IPv4:22}
319 12:11:12 18-11-2014 6.4799871  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E63 {DHCP:92, UDP:23, IPv4:22}
320 12:11:12 18-11-2014 6.4809336  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E63 {DHCP:92, UDP:23, IPv4:22}
321 12:11:12 18-11-2014 6.4809336  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E63 {DHCP:92, UDP:23, IPv4:22}
427 12:11:17 18-11-2014 11.4590402  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E64 {DHCP:109, UDP:23, IPv4:22}
428 12:11:17 18-11-2014 11.4590402  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E64 {DHCP:109, UDP:23, IPv4:22}
429 12:11:17 18-11-2014 11.4600525  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E64 {DHCP:109, UDP:23, IPv4:22}
430 12:11:17 18-11-2014 11.4600525  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E64 {DHCP:109, UDP:23, IPv4:22}
597 12:11:22 18-11-2014 16.4379016  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E65 {DHCP:127, UDP:23, IPv4:22}
598 12:11:22 18-11-2014 16.4379016  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E65 {DHCP:127, UDP:23, IPv4:22}
599 12:11:22 18-11-2014 16.4396184  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E65 {DHCP:127, UDP:23, IPv4:22}
600 12:11:22 18-11-2014 16.4396184  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E65 {DHCP:127, UDP:23, IPv4:22}
706 12:11:27 18-11-2014 21.4176741  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E66 {DHCP:136, UDP:23, IPv4:22}
707 12:11:27 18-11-2014 21.4176741  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E66 {DHCP:136, UDP:23, IPv4:22}
708 12:11:27 18-11-2014 21.4186057  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E66 {DHCP:136, UDP:23, IPv4:22}
709 12:11:27 18-11-2014 21.4186057  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E66 {DHCP:136, UDP:23, IPv4:22}
710 12:11:27 18-11-2014 21.4199199  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E66 {DHCP:136, UDP:23, IPv4:22}
711 12:11:27 18-11-2014 21.4199199  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E66 {DHCP:136, UDP:23, IPv4:22}
825 12:11:30 18-11-2014 24.5147776  0.0.0.0 255.255.255.255 DHCP DHCP:Request,  TransactionID = 0x026926FA {DHCP:140, UDP:20, IPv4:19}
826 12:11:30 18-11-2014 24.5147776  0.0.0.0 255.255.255.255 DHCP DHCP:Request,  TransactionID = 0x026926FA {DHCP:140, UDP:20, IPv4:19}
874 12:11:32 18-11-2014 26.3925235  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E67 {DHCP:142, UDP:23, IPv4:22}
875 12:11:32 18-11-2014 26.3925235  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E67 {DHCP:142, UDP:23, IPv4:22}
876 12:11:32 18-11-2014 26.3936105  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E67 {DHCP:142, UDP:23, IPv4:22}
877 12:11:32 18-11-2014 26.3936105  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E67 {DHCP:142, UDP:23, IPv4:22}
981 12:11:37 18-11-2014 31.3748590  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E68 {DHCP:150, UDP:23, IPv4:22}
982 12:11:37 18-11-2014 31.3748590  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E68 {DHCP:150, UDP:23, IPv4:22}
983 12:11:37 18-11-2014 31.3757827  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E68 {DHCP:150, UDP:23, IPv4:22}
984 12:11:37 18-11-2014 31.3757827  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E68 {DHCP:150, UDP:23, IPv4:22}
1251 12:11:42 18-11-2014 36.3559541  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E69 {DHCP:210, UDP:23, IPv4:22}
1252 12:11:42 18-11-2014 36.3559541  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E69 {DHCP:210, UDP:23, IPv4:22}
1253 12:11:42 18-11-2014 36.3567938  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E69 {DHCP:210, UDP:23, IPv4:22}
1254 12:11:42 18-11-2014 36.3567938  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E69 {DHCP:210, UDP:23, IPv4:22}
1312 12:11:44 18-11-2014 38.5468895  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0xDFCD81FF {DHCP:217, UDP:23, IPv4:22}
1313 12:11:44 18-11-2014 38.5468895  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0xDFCD81FF {DHCP:217, UDP:23, IPv4:22}
1314 12:11:44 18-11-2014 38.5478995  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = ACK, TransactionID = 0xDFCD81FF {DHCP:217, UDP:23, IPv4:22}
1315 12:11:44 18-11-2014 38.5478995  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = ACK, TransactionID = 0xDFCD81FF {DHCP:217, UDP:23, IPv4:22}
1378 12:11:47 18-11-2014 41.1441638  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0xDFCD81FF {DHCP:217, UDP:23, IPv4:22}
1379 12:11:47 18-11-2014 41.1441638  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0xDFCD81FF {DHCP:217, UDP:23, IPv4:22}
1380 12:11:47 18-11-2014 41.1456175  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = ACK, TransactionID = 0xDFCD81FF {DHCP:217, UDP:23, IPv4:22}
1381 12:11:47 18-11-2014 41.1456175  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = ACK, TransactionID = 0xDFCD81FF {DHCP:217, UDP:23, IPv4:22}
1400 12:11:47 18-11-2014 41.3318215  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E6A {DHCP:242, UDP:23, IPv4:22}
1401 12:11:47 18-11-2014 41.3318215  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E6A {DHCP:242, UDP:23, IPv4:22}
1402 12:11:47 18-11-2014 41.3327713  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E6A {DHCP:242, UDP:23, IPv4:22}
1403 12:11:47 18-11-2014 41.3327713  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E6A {DHCP:242, UDP:23, IPv4:22}
1491 12:11:51 18-11-2014 46.0188750  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1492 12:11:51 18-11-2014 46.0188750  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1493 12:11:51 18-11-2014 46.0204421  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1494 12:11:51 18-11-2014 46.0204421  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1499 12:11:52 18-11-2014 46.3086373  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E6B {DHCP:250, UDP:23, IPv4:22}
1500 12:11:52 18-11-2014 46.3086373  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E6B {DHCP:250, UDP:23, IPv4:22}
1501 12:11:52 18-11-2014 46.3104105  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E6B {DHCP:250, UDP:23, IPv4:22}
1502 12:11:52 18-11-2014 46.3104105  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E6B {DHCP:250, UDP:23, IPv4:22}
1521 12:11:53 18-11-2014 47.1995378  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1522 12:11:53 18-11-2014 47.1995378  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1523 12:11:53 18-11-2014 47.2004517  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1524 12:11:53 18-11-2014 47.2004517  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1582 12:11:55 18-11-2014 50.0386262  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1583 12:11:55 18-11-2014 50.0386262  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1584 12:11:55 18-11-2014 50.0396278  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1585 12:11:55 18-11-2014 50.0396278  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1599 12:11:57 18-11-2014 51.2872192  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E6C {DHCP:259, UDP:23, IPv4:22}
1600 12:11:57 18-11-2014 51.2872192  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E6C {DHCP:259, UDP:23, IPv4:22}
1601 12:11:57 18-11-2014 51.2886705  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E6C {DHCP:259, UDP:23, IPv4:22}
1602 12:11:57 18-11-2014 51.2886705  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E6C {DHCP:259, UDP:23, IPv4:22}
1765 12:12:00 18-11-2014 55.0241900  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1766 12:12:00 18-11-2014 55.0241900  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1767 12:12:00 18-11-2014 55.0257836  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1768 12:12:00 18-11-2014 55.0257836  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
1785 12:12:02 18-11-2014 56.2658054  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E6D {DHCP:267, UDP:23, IPv4:22}
1786 12:12:02 18-11-2014 56.2658054  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E6D {DHCP:267, UDP:23, IPv4:22}
1787 12:12:02 18-11-2014 56.2666712  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E6D {DHCP:267, UDP:23, IPv4:22}
1788 12:12:02 18-11-2014 56.2666712  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E6D {DHCP:267, UDP:23, IPv4:22}
1808 12:12:04 18-11-2014 58.0682483  0.0.0.0 255.255.255.255 DHCP DHCP:Request,  TransactionID = 0x02598857 {DHCP:269, UDP:20, IPv4:19}
1809 12:12:04 18-11-2014 58.0682483  0.0.0.0 255.255.255.255 DHCP DHCP:Request,  TransactionID = 0x02598857 {DHCP:269, UDP:20, IPv4:19}
1859 12:12:07 18-11-2014 61.2460411  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E6E {DHCP:271, UDP:23, IPv4:22}
1860 12:12:07 18-11-2014 61.2468202  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E6E {DHCP:271, UDP:23, IPv4:22}
1861 12:12:07 18-11-2014 61.2475685  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E6E {DHCP:271, UDP:23, IPv4:22}
1862 12:12:07 18-11-2014 61.2475685  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E6E {DHCP:271, UDP:23, IPv4:22}
2064 12:12:09 18-11-2014 63.8348976  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2065 12:12:09 18-11-2014 63.8348976  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2068 12:12:09 18-11-2014 63.8358960  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2069 12:12:09 18-11-2014 63.8358960  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2109 12:12:12 18-11-2014 66.2214060  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E6F {DHCP:325, UDP:23, IPv4:22}
2110 12:12:12 18-11-2014 66.2214060  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E6F {DHCP:325, UDP:23, IPv4:22}
2111 12:12:12 18-11-2014 66.2222663  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E6F {DHCP:325, UDP:23, IPv4:22}
2112 12:12:12 18-11-2014 66.2222663  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E6F {DHCP:325, UDP:23, IPv4:22}
2182 12:12:17 18-11-2014 71.2010497  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E70 {DHCP:333, UDP:23, IPv4:22}
2183 12:12:17 18-11-2014 71.2018269  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E70 {DHCP:333, UDP:23, IPv4:22}
2184 12:12:17 18-11-2014 71.2025743  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E70 {DHCP:333, UDP:23, IPv4:22}
2185 12:12:17 18-11-2014 71.2025743  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E70 {DHCP:333, UDP:23, IPv4:22}
2259 12:12:18 18-11-2014 72.4494165  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2260 12:12:18 18-11-2014 72.4494165  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2261 12:12:18 18-11-2014 72.4505529  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2262 12:12:18 18-11-2014 72.4505529  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2319 12:12:22 18-11-2014 76.1801118  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E71 {DHCP:343, UDP:23, IPv4:22}
2320 12:12:22 18-11-2014 76.1801118  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E71 {DHCP:343, UDP:23, IPv4:22}
2321 12:12:22 18-11-2014 76.1811241  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E71 {DHCP:343, UDP:23, IPv4:22}
2322 12:12:22 18-11-2014 76.1811241  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E71 {DHCP:343, UDP:23, IPv4:22}
2426 12:12:27 18-11-2014 81.1029685  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2427 12:12:27 18-11-2014 81.1029685  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2428 12:12:27 18-11-2014 81.1038124  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2429 12:12:27 18-11-2014 81.1038124  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2430 12:12:27 18-11-2014 81.1610571  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E72 {DHCP:352, UDP:23, IPv4:22}
2431 12:12:27 18-11-2014 81.1610571  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E72 {DHCP:352, UDP:23, IPv4:22}
2432 12:12:27 18-11-2014 81.1620457  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E72 {DHCP:352, UDP:23, IPv4:22}
2433 12:12:27 18-11-2014 81.1629101  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E72 {DHCP:352, UDP:23, IPv4:22}
2615 12:12:32 18-11-2014 86.1403426  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E73 {DHCP:361, UDP:23, IPv4:22}
2616 12:12:32 18-11-2014 86.1403426  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E73 {DHCP:361, UDP:23, IPv4:22}
2617 12:12:32 18-11-2014 86.1411735  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E73 {DHCP:361, UDP:23, IPv4:22}
2618 12:12:32 18-11-2014 86.1411735  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E73 {DHCP:361, UDP:23, IPv4:22}
2718 12:12:35 18-11-2014 89.3188301  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2719 12:12:35 18-11-2014 89.3188301  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2722 12:12:35 18-11-2014 89.3196306  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2723 12:12:35 18-11-2014 89.3196306  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
2771 12:12:37 18-11-2014 91.1198762  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E74 {DHCP:375, UDP:23, IPv4:22}
2772 12:12:37 18-11-2014 91.1198762  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E74 {DHCP:375, UDP:23, IPv4:22}
2773 12:12:37 18-11-2014 91.1208101  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E74 {DHCP:375, UDP:23, IPv4:22}
2774 12:12:37 18-11-2014 91.1208101  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E74 {DHCP:375, UDP:23, IPv4:22}
3075 12:12:42 18-11-2014 96.0954272  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E75 {DHCP:438, UDP:23, IPv4:22}
3076 12:12:42 18-11-2014 96.0961965  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E75 {DHCP:438, UDP:23, IPv4:22}
3077 12:12:42 18-11-2014 96.0961965  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E75 {DHCP:438, UDP:23, IPv4:22}
3078 12:12:42 18-11-2014 96.0961965  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E75 {DHCP:438, UDP:23, IPv4:22}
3136 12:12:43 18-11-2014 97.9179605  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3137 12:12:43 18-11-2014 97.9187662  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3138 12:12:43 18-11-2014 97.9195746  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3139 12:12:43 18-11-2014 97.9195746  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3228 12:12:46 18-11-2014 100.7812184  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3229 12:12:46 18-11-2014 100.7812184  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3230 12:12:46 18-11-2014 100.7823339  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = ACK, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3231 12:12:46 18-11-2014 100.7823339  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = ACK, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3238 12:12:47 18-11-2014 101.0732782  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E76 {DHCP:452, UDP:23, IPv4:22}
3239 12:12:47 18-11-2014 101.0732782  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E76 {DHCP:452, UDP:23, IPv4:22}
3240 12:12:47 18-11-2014 101.0740867  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E76 {DHCP:452, UDP:23, IPv4:22}
3241 12:12:47 18-11-2014 101.0748700  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E76 {DHCP:452, UDP:23, IPv4:22}
3274 12:12:47 18-11-2014 101.7821477  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3275 12:12:47 18-11-2014 101.7821477  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3276 12:12:47 18-11-2014 101.7833989  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = ACK, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3277 12:12:47 18-11-2014 101.7833989  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = ACK, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3357 12:12:49 18-11-2014 103.7882301  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3358 12:12:49 18-11-2014 103.7890064  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3359 12:12:49 18-11-2014 103.7897565  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = ACK, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3360 12:12:49 18-11-2014 103.7897565  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = ACK, TransactionID = 0xDFCD8200 {DHCP:249, UDP:23, IPv4:22}
3382 12:12:50 18-11-2014 104.3573135  0.0.0.0 255.255.255.255 DHCP DHCP:Request,  TransactionID = 0x026926FB {DHCP:457, UDP:20, IPv4:19}
3383 12:12:50 18-11-2014 104.3580837  0.0.0.0 255.255.255.255 DHCP DHCP:Request,  TransactionID = 0x026926FB {DHCP:457, UDP:20, IPv4:19}
3416 12:12:51 18-11-2014 106.0527848  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E77 {DHCP:459, UDP:23, IPv4:22}
3417 12:12:51 18-11-2014 106.0535728  0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xAB910E77 {DHCP:459, UDP:23, IPv4:22}
3418 12:12:51 18-11-2014 106.0543257  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E77 {DHCP:459, UDP:23, IPv4:22}
3419 12:12:51 18-11-2014 106.0543257  172.16.10.3 255.255.255.255 DHCP DHCP:Reply, MsgType = OFFER, TransactionID = 0xAB910E77 {DHCP:459, UDP:23, IPv4:22}

Similar Messages

  • Luxadm probe / Could not find the loop address for  the device at physical path

    Using EMC FibreChannel Disks on a Solaris 10
    # luxadm probe
    No Network Array enclosures found in /dev/es
    Error: Could not find the loop address for the device at physical path.
    # echo $?
    255
    Any ideas how to fix?
    Thank,
    Marcel

    Hi Marcel,
    Which Solaris 10 release is this?
    I found a very old bug that says this problem is already fixed in Solaris 10 although the bug description says
    its mostly seen on Solaris 8 and 9.
    https://bug.oraclecorp.com/pls/bug/webbug_print.showbug?c_rptno=15123550
    The bug says that these errors are displayed when StorADE 2.1 is running its rasagent cron job, which executes a luxadm display. 
    This process runs in the background so the user is not aware that another luxadm display process is running.
    Work-around: Do not run Storade rasagent cron job at same time as another luxadm display process.
    I hope this might help to debug this problem but I puzzled why this might be happening if its already fixed.
    Let me know if the workaround helps or so I can follow-up with the right support team.
    Thanks, Cindy

  • How do I open ports on my airport extreme and assign a fixed IP Address for a device connected to my network?

    I recently had a security system installed in my house.  One of the features is an EPAD which enables me to have a virtual keypad on my iphone, and computer to operate the alarm system.  The technician was not familiar with Mac's and Airports.  How do I open port 80 to 80 in my airport and assign a fixed IP address for the EPAD?  Apparently this is what is needed to make this work.

    There are three ranges of "strictly local" IP addresses reserved for local Network use:
    192.168.xxx.yyy
    172.16.xxx.yyy
    10.xxx.yyy.zzz
    What your Router does for you is to act as your agent on the Internet.Your requests are packaged up and forwarded on your behalf, and only when a response is expected is the response returned to your local IP address.
    Directing Network Traffic to a Specific Computer on Your
    Network (Port Mapping)
    AirPort Extreme uses Network Address Translation (NAT) to share a single IP address with the computers that join the AirPort Extreme network. To provide Internet access to several computers with one IP address, NAT assigns private IP addresses to each computer on the AirPort Extreme network, and then matches these addresses with port numbers. The wireless device creates a port-to-private IP address table entry when a computer on your AirPort (private) network sends a request for information to the Internet.
    If you’re using a web, AppleShare, or FTP server on your AirPort Extreme network, other computers initiate communication with your server. Because the Apple wireless device has no table entries for these requests, it has no way of directing the information to the appropriate computer on your AirPort network.
    To ensure that requests are properly routed to your web, AppleShare, or FTP server, you need to establish a permanent IP address for your server and provide inbound port mapping information to your Apple wireless device.
    To set up inbound port mapping:
    1) Open AirPort Utility, select your wireless device, and then choose Base Station > Manual Setup, or double-click the device icon to open its configuration in a separate window. Enter the password if necessary.
    2) Click the Advanced button, and then click Port Mapping.
    3) Click the Add button and choose a service, such as Personal File Sharing, from the Service pop-up menu.

  • TS1398 ip address for wifi?

    How do I know the IP Address for my home wifi?

    Find your IP address assigned by your Internet provider here.
    http://www.findmyip.com
    Use an IP scanner app to find your local network IP addresses. They will start with 10.x.x.x or 192.x.x.x
    When connected to your wifi network with your iPod, you should find the IP assigned here
    Settings > WiFi Networks > Choose your network > IP Address
    Basic troubleshooting steps  
    17" 2.2GHz i7 Quad-Core MacBook Pro  8G RAM  750G HD + OCZ Vertex 3 SSD Boot HD 
    Got problems with your Apple iDevice-like iPhone, iPad or iPod touch? Try Troubleshooting 101
     In Memory of Steve Jobs 

  • HT204053 Same email address for apple devices

    Can I use the same email address for itunes and app store for my all my apple devices?

    It sounds as though you are trying to create a new iTunes store account using the details of an existing account, you need to sign into your old account not create a new one. Navigate to settings > store, scroll down to the bottom, tap on your Apple ID and then tapthe "sign out" button. Then sign in again using the iTunes store details you wish to use.

  • Find ip address for network device?

    Hi,
    Have question about the IP address, i got NAS (buffalo) which is work great with snow leopard.
    I can access network drive from finder, which is show as Wd-Mybookworld
    My problem is sometime i need to access to the NAS to config it, but i cannot find the ip address for Wd-Mybookworld
    How can i check the ip address of the NAS, if i can see and access it by its name in the finder???
    Or can i juts put its name in the safari address bar and let it link to ip automatically?
    Your help are much appreciate.

    Thank for the answer, however, this answer didnt get me the IP address but get me the link to the device name.
    For example,  my device name is "Ned-MyBookWorld" i can access without ip address by type
    http://ned-mybookworld.local./   in the safari address bar
    Thank again for your help

  • CM7/8.5 - Is MAC address for a device stored any other place other than device name?

    We are interested in obtaining the MAC of a soft phone through a query to the RIS port.  Everything is working fine as long as the MAC address that is written to the device name field by default is not changed by a user to read something else like machine name.  Is there a field other than device name that we should be querying for a device to always be sure to get the MAC address of a device? 
    Currently the XML returned by the RIS port is parsed to get the CmDevices.Name.  The returned MAC address is formed by returning this name minus any occurrence of the string "SEP".

    Hi,
    CNAME resource records are recommended for use in the following scenarios:
    • When a host that is specified in an A resource record in the
    same zone needs to be renamed
    • When a generic name for a well-known server, such as www, must resolve to a group of individual computers (each with individual A resource records) that provide the same
    service, for example, a group of redundant Web servers
    Therefore please try to create your CNNAM record in the same zone and try again.
    The related KB:
    Adding, Changing, and Deleting Resource Records
    http://technet.microsoft.com/en-us/library/cc779020(v=ws.10).aspx
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Multiple ICLOUD Email addresses for multiple devices.......HELP

    In our family we have an IPOD, IPHONE, IPAD, and another IPOD Touch. How do I setup additional emails under my main ICLOUD email address? I have created several but it won't allow me to link it to the mail ICLOUD account. I want each device to have their own icloud email but still be able to access all of my content.

    Each iCloud account only has a single iCloud email account.  You can create up to 3 alias addresses within the account, but they will all receive email in the same inbox.
    If you want each person to have their own email account (inbox), and still be able to access the other iCloud data in your main account, you would need to create "secondary" iCloud accounts on each person's device.  You can do this by going to Settings>Mail,Contacts,Calendars>Add Account>iCloud and signing in with a different Apple ID.  Secondary accounts can be used for Mail, Notes, Contacts, Calendars, Reminders.  If you only want to add a new mail account, you can just turn Mail to On in the secondary account.  The only drawback to this approach is that secondary iCloud email accounts only support fetch email, not push.  Push mail is only supported in the primary account.

  • Bridging from a Netcomm router to my EA6500, duplicate home IP addresses for both devices ?

    I'm attempting to bridge from a Netcomm router to my EA6500, I can set the Netcomm into bridging mode no problems and as expected the Internet is gone.
    Next step is to access my EA6500 to configure it to manage Internet access however when I try 192.168.1.1 to get to my EA6500 it takes me to the WEB interface for the Netcomm router as it's default IP is also 192.168.1.1, so I'm stuck.
    So they have the same default IP address, how do i get to my EA6500 to finish the configuration ???
    Thanks
    Tony

    From what you're describing... It doesn't sound like your modem/router is in full bridge mode. Sounds like half bridge.
    I guess you could disconnect the EA6500 from modem. Reset EA6500 to factory defaults. Change the local IP address of the EA6500 to 192.168.2.1. And then reconnect the EA6500 back to the modem.

  • Ip address for WIFI

    Hi,
    I am using my Macbook pro in the office, and it detects differnt IP everyday,
    I need to Fix one single IP manually.
    When i connect with manually its not getting connected,
    Kindly help me to solve this,
    Thanks n Regards
    Dinesh.N

    There is no word of static, still i confused to make it on static, can you explain step by step
    Thanks in advance

  • Can I use my Time Capsule for wifi parental control?

    Can I use my Time Capsule for WiFi parental control.  The objective first is to use a time clock to control internet access (completely on or off).  Second objective is to use the Time Capsule which is also the WiFi router for more selective internet control?  Anyone out there have any tips on making this work?  We have Time Warner cable feeding the house internet, which is then corrected to the 2Tb Time Capsule which also provides our WiFi.  Any information including other alternatives would be most appreciated.  Surely we are not the only parents on the planet with this issue.  Thanks very much!

    how do I get the Mac addresses for each device (this won't be a problem, I demand the device, check it, and then return it).
    What wireless devices are we looking at here?
    Most devices have the AirPort ID or MAC Address or Hardware Address printed on the back or bottom of the device
    Otherwise, you can learn the correct number by process of elimination. Turn off all wireless devices except your Mac computer....if it is connecting using wireless.
    Open Macintosh HD > Applications > Utilities > AirPort Utility
    Click on the Time Capsule icon
    Look for Wireless Clients and click on the numerical IP address that is displayed
    Another box will open
    Look for the Hardware Address. It will be displayed as xx : xx : xx : xx :xx : xx
    Write that down and note that it is your Mac.
    Now, connect another wireless device and repeat the sequence.  Click on the "other" listing that you see to find out more info about that device.  Write down the ID or Address and note what device it is. Then power it off.
    Do the same for each wireless device that you want to have limited access.
    Post back when you have all the info.

  • I can use my time capsule for wifi, but can't connect for backup

    I have been using my TC for a couple of years now, always as a router and backup disk.  I went on a long trip then came back and tried to connect to it, I can use the wifi, but I can't connect to the disk to see it or use it for backups.  I also have a PC connected to the TC and I can see the contents on there through explorer.
    Any ideas would be appreciated...

    how do I get the Mac addresses for each device (this won't be a problem, I demand the device, check it, and then return it).
    What wireless devices are we looking at here?
    Most devices have the AirPort ID or MAC Address or Hardware Address printed on the back or bottom of the device
    Otherwise, you can learn the correct number by process of elimination. Turn off all wireless devices except your Mac computer....if it is connecting using wireless.
    Open Macintosh HD > Applications > Utilities > AirPort Utility
    Click on the Time Capsule icon
    Look for Wireless Clients and click on the numerical IP address that is displayed
    Another box will open
    Look for the Hardware Address. It will be displayed as xx : xx : xx : xx :xx : xx
    Write that down and note that it is your Mac.
    Now, connect another wireless device and repeat the sequence.  Click on the "other" listing that you see to find out more info about that device.  Write down the ID or Address and note what device it is. Then power it off.
    Do the same for each wireless device that you want to have limited access.
    Post back when you have all the info.

  • Cisco ip to mac address of a device?

    What command can I run in CLI, to get a mac address that is associated with a provided ip address?
    Context: In order to access wifi, users have to go through a web authentication. Upon submiting their credentials, we are able to see their ip address. We want to query router api with cli or something, to find a mac address based on the ip.
    Any pointers?

    It is usually not possible for a person to get the MAC address of a computer from its IP address alone. These two addresses originate from different sources. Simply stated, a computer's own hardware configuration determines its MAC address while the configuration of the network it is connected to determines its IP address.
    However, computers connected to the same TCP/IP local network can determine each other's MAC addresses. The technology called ARP - Address Resolution Protocol included with TCP/IP makes it possible. Using ARP, each computer maintains a list of both IP and MAC addresses for each device it has recently communicated with.
    Most computers allow you to see the list of IP and MAC addresses that ARP has collected there. In Windows, Linux and other operating systems, the command line utility "arp" shows this information. Using "arp," you can in fact determine the MAC address of some computers from their IP address. ARP works only within the small group of computers on a local area network (LAN), though, not across the Internet. ARP is intended for use by system administrators and is not generally useful as a way to track down computers and people on the Internet.

  • SG200-08 Loosing MAC addresses of connected devices

    I have a SG200-08 Switch that has in the last month been acting up with certain types of traffic.  On June 7, 2013 I installed the 1.0.6.2 firmware upgrading from 1.0.5.1.  Updating the firmware has not helped. 
    Last week Tuesday a server that was connected to that switch disappeared from the network, looking at the trouble I had to reboot the server and traffic began to flow.  After rebooting the server I found only 1 of 2 MAC addresses from the 1 NIC showing up on the port.
    Today I have a Xerox Workcenter connected to the switch on another port and while working on changing settings on the device I stopping being able to reach the device, could not even ping it.  I went into the switch port showed active, but no MAC address found in the dynamic table for that port. After rebooting the switch I could reach the Xerox again.
    I rebooted the switch on Friday near the end of the day and it was doing better till this morning, all MAC addresses for connected devices were showing up OK.  Is the device defective?  It had been working OK previously, it is connected to another switch on port 1, and that shows a proper table of dynamic MAC addresses.  In both cases of loosing a device it was being used not dormant or in any kind of low power mode.

    Dear Michael,
    Thank you for reaching Small Business Support Community.
    Based on the symptoms; SG200 working fine before, it seems to work ok after reboot, and latest firmware already installed.  It seems to me like a hardware failure but still, in order to confirm, it would be a good idea to restore to factory conditions and configure it manually again.  Just in case that does not help I suggest you to contact the Small Business Support Center for further assistance;
    https://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html
    Please let me know if there is anything I can assist you with in the meantime.
    Kind regards,
    Jeffrey Rodriguez S. .:|:.:|:.
    Cisco Customer Support Engineer
    *Please rate the Post so other will know when an answer has been found.

  • DHCP scope only for WiFi

    Hi. Is it possible to configure some DHCP scope on Windows Server 2012 R2
    only for WiFi devices?
    Maybe some policy?
    Thank you!

    Hi,
    Base on my experience, in the enterprise environment, we usually create a private vlan for the wireless terminal.
    Therefore you can create a dedicated scope for the wireless terminal device.
    More information:
    What's New in DHCP in Windows Server 2012 R2
    http://technet.microsoft.com/en-us/library/dn305900.aspx
    Configuring a DHCP Superscope
    http://technet.microsoft.com/en-us/library/dd759168.aspx
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

Maybe you are looking for

  • Multiple NLS in one web server

    Hello all , currently i have the following: DB1 ,ar8mswin1256 characterset , accessed from web application with nls = ar8mswin1256 . DB2 , WE8ISO8859P1 characterset , accessed from web application with nls = WE8ISO8859P1. i want to consolidate the tw

  • Two safari browsers on the same Mac- how to remove one?

    Since my windows PC broke, I had used my kids' mac min lately. In order to complete an on-line form I had to instal the 4.0 version of Safari. I followed the instructions on the website (with the form) and linked to apple and downloaded version 4.0 t

  • Importing a video in Photoshop CS3, only white background appears?

    Uhm, hello. I have googled about this for a couple of hours and I can't find an answer. Ok, so here's what I do. File>Import>Video Frames to Layers>Then I choose the video and also the parts I want>OK. But only white background appears. Also the fram

  • Memmory card not reading through USB cable while ...

    Hi,am using Xpressmusic 5130.When i connect it to PC using USB cabe and selecting Data Storage option,it is showing 'Memmory card in use by another application,Please wait'.And  i didnt find any appln using memmory card at that time.Bui i could trnsf

  • Problem with memo field displaying

    I have a table in MS access with a memo field. Everything the user inputs in the field is recorded in the table. When I try to output the memo field I am on getting part of the field. Attached is the code for displaying the data from the acty_comment