Some dhcp clients not reaching internet

This afternoon, I noticed that my iPhone was no longer reaching the internet. Later, we noticed my husband's (new!) iPad and my son's MacBook were not reaching the internet either. At least my MacBook was still reaching the internet. In all cases, the connectivity with the airport was fine; 4-5 bars, most of the time. All were connected yesterday, I believe. We made no real changes. I had my iPhone right next to my MacBook and both had good connections to the wifi, but only the MacBook was reaching the Internet.
I went into Airport Utility and looked at the Time Capsule and found a long list under DHCP clients (maybe 9), but only 4 on the wireless clients list. I researched the issue, finding very little except generic suggestions (update software and reset the Time Capsule). The software was up to date; resetting it did fix the problem, at least for now. I am concerned it will happen again.
Our airport devices:
- Time Capsule running 7.5.2
- 2 Airport Expresses, also running 7.5.2.
Most, if not all, our wifi devices are up to date, including my MacBook running 10.6.5 and my iPhone running 4.2.1.

I'm not sure this is quite the same since simply restarting our Time Capsule fixed things for us. It is annoying since I don't want to have to restart the Time Capsule every week or so when it fails this way, but restarted did fix this, at least temporarily.
Another possibility I came across is that an ISP might limit the number of devices you can connect to the Time Capsule, but that wasn't the case for us. I'm thinking the Apple person you talked to probably checked on this, though.
Hope you can figure it out!
- Liz, aka liz4cps

Similar Messages

DHCP Clients Not showing in Server Admin....but are there

Hi,
DHCP has just recently stopped showing me the MAC addresses of connected clients. It always says 0 though I know through the logs that DHCP is working. Any ideas? I will give more info if needed but wondering if it's maybe a bug or something?
Thanks.

try if this helps:
_*Music Folder Files Not Added v2.0*_
This application will list the file paths of the files in your designated "iTunes Media" folder which are not in iTunes' library. Additionally, you can select a different parent folder and its contents will be compared to the iTunes library. Options to Add a selection of found files to iTunes or move them to the Trash.
JGG

UC560 - CUE can not reach internet

Hello all, new here, but not new to using Cisco equipment. I am however new to the phone side of Cisco.
I'm currently working on an issue with my CUE traffic not routing out to the internet, however I'm feeling rather stumped at the moment and was hoping to get some insight from the community.
As a bit of background - on my UC560 the CUE IP is not the default, I had to change it due to an IP conflict (that was a painful process). If I have a terminal open to the UC560, I can ping the CUE, and ping out to the internet. If I open the session to the CUE, I am able to ping the UC560, however unable to ping an internet IP (i.e. 8.8.8.8).
Here are the results of a sh ip route:
S*    0.0.0.0/0 [1/0] via 10.1.0.1
      10.0.0.0/8 is variably subnetted, 7 subnets, 3 masks
C        10.1.0.0/24 is directly connected, Vlan1
L        10.1.0.228/32 is directly connected, Vlan1
C        10.1.1.0/24 is directly connected, Vlan100
L        10.1.1.1/32 is directly connected, Vlan100
C        10.10.10.0/30 is directly connected, Vlan90
S        10.10.10.1/32 is directly connected, Vlan90
L        10.10.10.2/32 is directly connected, Vlan90
I will be happy to share more configuration items as requested. Any help would be greatly appreciated.
As an additional note, I would need the Vlan90 (CUE) traffic routed (Or maybe NAT'd) through the UC560, as I can not make any changes to the current router.
Thank you in advance!

The existing LAN is on the 10.1.0.0 Network. When I session into the CUE, I can ping 10.1.0.228 (The LAN IP of the UC560), but I can not ping 10.1.0.1 (LAN Router - which I can not adjust routes) or any other LAN hosts.
Is there a way I can setup a route for the 10.10.10.0 through the LAN interface (10.1.0.228) of the UC560? Or a way to NAT the 10.10.10.0 traffic behind that interface?

Some messages are not reaching my webmail INBOX

I use an email forwarder so that my email address is [email protected] (It's not really xyzzy but you get the idea.) They redirect messages to my actual Verizon email address.
In the past week, some emails sent to xyzzy are not getting to VZ. POBOX says they are forwarding them and sent me the following for one test message:
I have found the message in question:
138587ec 6 10:41:56 sepia postfix/cleanup[21713]: 7F50A40A675: message-id=<[email protected]>
138590ec 6 10:41:56 sepia postfix/qmgr[32466]: 7F50A40A675: from=<SRS0=+HRw=6S=pobox.com=[email protected]>, size=1018, nrcpt=1 (queue active)
138599ec 6 10:41:56 sepia postfix/smtp[21995]: 7F50A40A675: to=<[email protected]>, relay=a-pb-fb-quonix.pobox.com[208.72.237.7], delay=0, status=sent (250 2.0.0 Ok: queued as C31D97308)
If you still cannot find this message, I would suggest contacting Verizon with these logs to find out if they know where this message went. According to our logs, this message was sent successfully to your forwarding address.
I chatted online with a VZ tech support person who didn't know what an email forwarder was but he said that someone would call me in 15-20 minutes. When no one called in an hour, I called VZ. I got to Shilpa on the second level who insisted that I had to download and run a program that would let them control my PC. I refused, offering to send them an email with the above message from POBOX.COM. She insisted on the remote assistance app, and then decided that she could not help me if I did not comply. I asked for her supervisor. She agreed to transfer the call and then placed me on hold FOR TWO HOURS, at which point VZ terminated the call.
I'm hoping that some VZ email wizard can pass the above log to an email administrator who can solve the problem of the never-appearing emails.
Thank you in advance.

pjh wrote:
I use an email forwarder so that my email address is [email protected]. (It's not really xyzzy but you get the idea.) They redirect messages to my actual Verizon email address.
In the past week, some emails sent to xyzzy are not getting to VZ. POBOX says they are forwarding them and sent me the following for one test message:
I have found the message in question:
138587ec 6 10:41:56 sepia postfix/cleanup[21713]: 7F50A40A675: message-id=<[email protected]>
138590ec 6 10:41:56 sepia postfix/qmgr[32466]: 7F50A40A675: from=<[email protected]>, size=1018, nrcpt=1 (queue active)
138599ec 6 10:41:56 sepia postfix/smtp[21995]: 7F50A40A675: to=<[email protected]>, relay=a-pb-fb-quonix.pobox.com[208.72.237.7], delay=0, status=sent (250 2.0.0 Ok: queued as C31D97308)
If you still cannot find this message, I would suggest contacting Verizon with these logs to find out if they know where this message went. According to our logs, this message was sent successfully to your forwarding address.
I chatted online with a VZ tech support person who didn't know what an email forwarder was but he said that someone would call me in 15-20 minutes. When no one called in an hour, I called VZ. I got to Shilpa on the second level who insisted that I had to download and run a program that would let them control my PC. I refused, offering to send them an email with the above message from POBOX.COM. She insisted on the remote assistance app, and then decided that she could not help me if I did not comply. I asked for her supervisor. She agreed to transfer the call and then placed me on hold FOR TWO HOURS, at which point VZ terminated the call.
I'm hoping that some VZ email wizard can pass the above log to an email administrator who can solve the problem of the never-appearing emails.
Thank you in advance.
If the email forwarder is not getting a bounceback, set your spam detector to save messages instead of deleting them in verizon.net and see if they show up in your spam folder.
If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer as Accepted Solution so others can see the solution to the problem.
"All knowledge is worth having."

DHCP client not working on WLAN after boot [Win XP]

Hi.
I've got a problem with a Lenovo T61 with Windows XP SP2.
I've browsed the forums, and I haven't seen anyone else with a similar problem.
The WLAN works on this computer, but I have to turn it off and on before it works.
If I boot the computer with no ethernet cable connected, log in and wait for Windows to connect to a WLAN, I get limited or no connectivity.
The computer is able to connect to the WLAN I have chosen, but when it is supposed to recieve an IP adress from the DHCP Server it doesn't.
I either have to right click the wireless icon at the lower right of the screen and press repair, or I have to turn off and on the wireless radio with the switch on the laptop.
When I do this it works as normal.
If I use Access connections to set up a wireless connection, specify an SSID, encryption and choose to get IP from DHCP it works. I recieve an IP adress without turning the WLAN radio off and on.
The person using this computer is travelling a lot, and he is not very good with computers, so he doesn't want to use Access Connections to manually make a profile for each WLAN he uses.
How can I fix this and use windows to mange WLAN connections without having to using "repair" or turning the WLAN radio off and on?
Thanks in advance.

There is another thread on this problem about not recovering TCPIP addresses on this forum. the thread recommends installing an update. http://forums.lenovo.com/lnv/board/message?board.id=T_Series_Thinkpads&thread.id=1620
Does the laptop have SP3 installed. I found this to be very helpful on my T23.
ThinkPad T23, 2647 HU8, Based on 2647-8RU: PIII-M 1.20GHz (512KB), 512MB RAM, 40.0GB HDD, 14.1 XGA(1024x768) TFT LCD, 8x8x24x/8x CDRW/DVD, Modem(MPCI), Ethernet(CDC), WinXP Home, Linksys Wireless B adapter.

DHCP Client not setting obtained nameserver info

Solaris 8
The dhcpagent file was modified so that the nameserver info is requested: PARAM_REQUEST_LIST=1,3,6,12,43
By default, #6 was missing. After a boot, running dhcpinfo and requesting the data for #6, results in three IP addresses being displayed.
The problem is that those three values are not set anywhere, so no resolving is done. If I manually place the values into resolv.conf, then resolving works. Obviously I need this to happen automatically.
Any clues as to what to do so that automatic configuration of nameserver info obtained via DHCP will be appreciated.
Thanks in advance
MB

Having multiple DIFFERENT nameserver addresses is fine, it will just try them in sequence. But I see no point in having the same IP repeated and that might be a bad thing relative to performance (or it might be smart enough to ignore duplicates)
As for the .plist files, no idea. Since the Cisco VPN is not using system prefs I don't think that would be an issue, but don't know what these files are really used for. i also tired the same setup (installing the Cisco VPN) on a system that has not been touched in ages (an old mac cube server as my backup/media server) and it had the same result. That leads me to think it is something on the remote end, yet my linux box connects and sets its nameserver just fine. I don't recall just when this started happening, maybe its a 10.4.10 issue (at least both Macs are on 10.4.10) ???

DHCP client not working

Ok here is the scenario:
I have a laptop with an up to date Arch installation, at home I use a static ip with my router which still has dhcp enabled for some other desktops.
Now at work I needed to use DHCP, so i reconfigured rc.conf to say eth0="dhcp". But it never got an ip address, it always fails. When I checked with ethereali could see the outgoing dhcp packet but no response from the server, the cable and server were clean because all was well under Windows. I tried both dhcpcd and dhclient but no luck with either.
I then compared the packets under windows and arch and came to the conclusion that the only noticeable difference is that the DHCP message type is "DHCP Request" under Windows and for some reason is "DHCP Discover" under arch (there's a binary difference in the packet and thats the way ethereal names the types). Now i'm wondering why the hell does it do that? Why can't dhcpcd and dhclient send a normal dhcp request? Am I missing something really obvious here? Because Dhcp is making me look like an idiot :S And I really need to get online under Linux for work.
Any help is appreciated. Thx.
EDIT: I also have Arch on my desktop, and just tried it using dhcp there, and it works fine. It might be worth mentioning that my desktop is rather out-of-date when it comes to packages while my laptop is prettymuch up-to-date. And yup the packet type is also "Dhcp Request" when i try it on my desktop instead of "Dhcp Discover".. weird.

Solved: Was a driver problem, if you have a broadcom wired ethernet chipset, you need the driver from broadcom because the kernel has some kind of reversed driver built in and it doesn't work properly.

Can not reach internet from vlan on 3560 switch but can from switch

ISP provided me IP (207.70.170.42) and gateway address(207.70.170.41) connecting to their router( meto E).
I can ping outside the network when logged into the switch through telnet but not when connected through a pc on the vlan.
I can ping the IP address on port GI0/1 207.70.170.42 from the PC on vlan 99 (192.168.20.3).
What do I need to configure to get the VLAN to send traffic to the internet.
Tried ip route 0.0.0.0 0.0.0.0 207.70.170.41
Tried ip route 192.168.20.0 255.255.255.0 207.70.170.41
Tried ip route 192.168.10.0 255.255.255.0 207.70.170.41

Hi @rbrewer02,
Are you doing NAT or PAT for private IP addresses? Remember that the ISP just see the public IP address that it gives to you (207.70.170.42 in your case).
You should configure NAT so that your private IP ranges get translated into your public IP address.
If you need help in configuring NAT just tell me.
Rgrds,
Martin, IT Specialist

Some emails not reaching their destination

Since moving from MobileMe to iCloud some emails are not reaching their destination.

the same way!
Some letters do not reach the destination with iPad iCloud mail. In iCloud they fall into the "Sent", but do not come to a different destination some letters.

Domain client not appear in network neighbourhood

Hi,
I have server 2012 DC.
Some Domain clients not appear in network neighbourhood.
Any suggestion.
Anuj Gupta

Hi,
Are all of the existing machines Windows XP?
The computer is running Windows XP and the LLTD protocol is not installed. Before a computer running Windows XP can be detected and appear on the network, you need to install the LLTD protocol on that computer. For more information, please refer to Microsoft
website below.
http://support.microsoft.com/kb/922120
The computer is running Windows XP and firewall settings are preventing Windows from detecting it. Check the firewall settings and make sure that file and printer sharing are enabled. If you are using Windows Firewall, see Understanding Windows Firewall
settings. If you are using another firewall, check the information that came with your firewall.
Andy Altmann
TechNet Community Support

Why do some devices show up as wireless clients and not DHCP clients

When looking at the 'Logs and Statistics' section it shows me the MAC addresses of 3 wireless devices I have on my W/LAN (Macbook and 2 wireless PVR's) in the 'wireless clients' section but no info on the 2 wireless PVR's in the DHCP clients section. Only the Macbook appears there with its ip address shown. Can anyone tell me how to find out the ip addresses of these 2 other devices. I tried connecting one of the PVR's via a cat 5 but that one still doesn't show up in the DHCP clients section.

Esterhazyinoz wrote:
Can anyone tell me how to find out the ip addresses of these 2 other devices. I tried connecting one of the PVR's via a cat 5 but that one still doesn't show up in the DHCP clients section.
Try scanning with WakeOnLan to get a list of all devices and their IP addresses. If the devices got fixed IP addresses at the factory, they won't show up under DHCP.

Clients not getting DHCP from external server

Hi,
I have a 4402 (version 7.0.235) working with 10 units of 1121 APs connected to it. The WLC is not configured to work in LAG mode. Physical portt #1 is connected to the Main Switch (trunk). I have 3 WLAN mapped to 3 Different VLAN and Everything (security and internal, external DHCP) is working swell...
Now- I have connected Physical port #2 directly to an ADSL Router (giga port), Configured Port 2 as untaggedwith the proper IP details.
I have configured this interface to receive DHCP from the ADSL Router and for some reason, Clients are not getting addresses.
When I assign a Static address to my laptop I get internet access and all is nice. I tried configuring The WLC internal DHCP server (instead of the ADSL router) and that didn't help. It seems like a DHCP problem but I dont understand the source of the problem of think of the solution.
When turning off the proxy settings I noticed that it helped. Is there anything to do with that? The problem was that after a while the other WLANs starting causing DHCP issues as well.
What is supposed to be configured? Any Expert is the House?
I attached a crappy drawing..

Hi Scott,
Thanks for your answer.
So what you are basicly saying is that I have 2 choices: 1 - disable the Proxy option on the WLC and work with external DHCP servers (internal will not work when this is enabled). 2 - Enable the Proxy option and only work with the WLC internal DHCP.
I have installed many WLCs this way, having Different DHCP Servers (external and internal) for multiple WLANs.
What do you think may be different this time? The router that I am using isn't the most expencive but it is providing DHCP to other clients (wired client) with no problems.
Thanks!!!

WLC2504 clients not receiving DHCP leases

I'm stock with a 2504 using version 7.0.220.0 that won't lease out DHCP adresses
Wifi clients are unable to get a DHCP lease from an external DHCP server.
The WLC are handling 3 WLAN, 2 using internal DHCP server, 1 (that wont work) using external DHCP. The external DHCP server, is a router/firewall (out of my reach) that suffered from a power out, a short while ago, ever since the DHCP is not working on that VLAN, if client are getting static ip adresses, everything works fine. If i'm using the same network link, and plug it into a computer, I get a DHCP address.
I've enable DHCP proxy
Debbuging DHCP, using: Debug DHCP packets enable
Gives me this:
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP received op BOOTREQUEST (1) (len 308,vlan 20, port 1, encap 0xec00)
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option len (including the magic cookie) 72
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: message type = DHCP INFORM
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: 61 (len 7) - skipping
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: 12 (len 1) - skipping
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: vendor class id = MSFT 5.0 (len 8)
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: 55 (len 13) - skipping
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP options end, len 72, actual 64
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP dropping packet (no mscb) found - (giaddr 0.0.0.0, pktInfo->srcPort 68, op: 'BOOTREQUEST')
Thanks

Hi Steen,
When a client is in DHCP REQ state on the controller, the controller drops DHCP inform packets. The client will not go into a RUN state on the controller (this is required for the client to pass traffic) until it receives a DHCP discover packet from the client. DHCP inform packets are forwarded by the controller when DHCP proxy is disabled.
Please check this, if still u r facing issue then provide more info.
Can you please paste a client debug of the client having DHCP issues.
Go to cli of the wlc and run the client debug . Diconnect the client then reconnect and gather the output and post.
Regards

WEC7 DHCP Allocator not sending ACK for a DHCP client

Hi All,
I have a WEC7 device configured as DHCP Allocator.
My PC (windows 7) will get ip from DHCP allocator successfully.
WEC7 ip settings:
ip: 169.254.0.1
subnet: 255.255.0.0
DNS: 0.0.0.0
My PC Ip after got ip from WEC7 DHCP Allocator:
ip : 169.254.0.3
net mask: 255.255.0.0
DHCP server: 169.254.0.1
DNS server : 169.254.0.1
Default Gateway: 169.254.0.1
I have another device (Ethernet based energy Meter), I am getting below problem
-> Meter will send DHCP DISCOVER Command (Broadcast)
-> DHCP Allocator Sends DHCP OFFER command back (Broadcast)
-> Meter will send DHCP Request to DHCP Allocator (Broadcast)
Now meter expects DHCP ACK command but DHCP allocator not sending any command.
within ~3 sec Meter start sending DHCP DISCOVER Command. this will happen continuously.
some time DHCP server will send ACK, but by that time Meter start sending DHCP DISCOVER command.
I Tried testing this meter by connecting to my PC directly and running a simple DHCP Server on my PC, here Meter connected to sample server and got ip from server.
The DHCP Concept is working with WEC7DHCP Allocator to PC client, Meter to PC as server but not with WEC7 server and Meter.
I compared the packets, only the difference i can identify is PC client is configured with Host name and Meter not have nay host name.
Any idea on whats wrong with WEC7 and Meter combination?
Do you know any third party DHCP server?
Please suggest me,
rakesh

Hi All,
The problem is not yest solved.
As I mentioned in last post, only the difference between My PC and Meter is Meter don't have Device Name and we are not able to configure it.
Device Name is the real Problem? If yes how can i eliminate this dependency?
For Static ip allocation at HKEY_LOCAL_MACHINE\Comm\ConnectionSharing\Addresses\Address, aslo there is dependency on Device name, is it possible to map the ip to MAC instead of Device name?
One more thing I observer that, DHCP allocator will send response for DISCOVER or REQUEST after 3 seconds. As Meter will send next discover before getting ACK, please check below log.
But in PC the entire DHCP registration will finish within 1 sec, I am not understanding why DHCP Allocator delaying for responding
Any suggestions will be really appreciated. Please recommend any third party DHCP Server if any available (we are ready to purchase also)
Thanks in Advance
DHCP Allocator (WEC7) Ip: 169.254.0.1
ip allocated from WEC7 for my PC : 169.254.0.15
Meter ip : 0.0.0.0
rakesh

DHCP client does not work poperly after systemd and Gnome 3.6 upgrade

Upgraded my system today from Gnome 3.4 to 3.6 (and systemd was updated as well), and since then acquiring an IP address using DHCP does not work anymore.
I am using IPv4 only internally, but neither dhclient or dhcpcd manages to get an IPv4 address.
It seems like IPv6 is priority one, and beacuse there is no IPv6 DHCP server available NetworkManager aborts the whole setup process.
To make sure that IPv6 should not be considered, I have changed "method" in NetworkManager to "Ignore" for IPv6.
I have also tried to downgrade NM to 0.9.6.0 from 0.9.6.4 (since that version works on another, not upgraded, machine), without any result.
Also switched dhclient to dhcpcd, without any result.
The machine is a "pure" systemd machine.
DHCP works for other devices in the network.
Versions:
systemd 195-2
NetworkManager 0.9.6.4
isc-dhclient-4.2.3-P2
I have no issues on a system where following versions are running:
systemd 189-4
NetworkManager 0.9.6.0
dhcpcd 5.6.2
Log: http://pastebin.com/2wMC0JLe

Think I have identified the issue now.
Neither dhcpcd or dhclient is sending the host name properly to the DHCP server anymore. I had an IP address reserved in the DHCP server for my host and after deleting this reservation my host is able to acquire an IP (dynamic) address. The reserved static address could never be acquired.
Conclusion: dhclient and dhcpcd is not sending the host name as before, causing the DHCP server to get stuck (while waiting for the host name) whenever a NIC with a reserved IP address is requesting an IP address.
Downgrading the dhcp clients has not yet worked, so there might be some underlying component that is causing the problem. ath5k? systemd?

Some dhcp clients not reaching internet

Similar Messages

Maybe you are looking for