ABS not distributing DHCP addresses via hub

Hi --
My home network based on an original Airport Extreme (about 3 years old) was working fine until about two weeks ago, but now I have intermittent problems.
The most serious network problem is that computers with wireless connections are working OK -- they get to the internet with no problem -- but the wired devices (Mac G4, Mac G5, Dell PC, HP printer, Sonos media streamer, all connected via a hub) have lost their local 10.0.1.x addresses and can't acquire new ones. I can't print from any system, and the wired computers can't connect to the internet. The first time this happened I was able to fix it by changing settings on the base station (turning on "interface robustness") but now messing with settings doesn't help.
A less serious problem is the base station loses its internet connection about once a day. This problem is resolved by disconnecting power from the ABS and restarting it.
A suspicious coincidence is that both problems started about the time I bought the two new handsets for our wireless phone system. The phones are 5.8 GHz Panasonic KX series. There used to be 3 handsets, now there are 5. I moved the phone base station away from the ABS but that didn't affect anything.
Has anybody else had ABS problems where wireless connections are OK but wired hub connections don't work? Or problems with interference with 5.8GHz phones? Any other ideas or suggestions?
Original Airport Extreme Base Station Mac OS X (10.4.9)

Similar Messages

WRVS4400N Unable to get DHCP address via wireless

I am having an issue with the WRVS4400N. I am unable to get a DHCP address via wireless. If I connect directly to the router via RJ45, I get a dhcp address an and able to get to the internet. Has anyone ran into this issue.

This seems to be a problem with the latest firmware (v1.01.03) available from Linksys for this router. The stock firmware for my WRVS4400N router assigned DHCP addresses to wireless devices without any issue. As soon as I upgraded the router to v1.01.03, the router no longer assigns DHCP addresses to wireless devices. I have verified there is no issue with the router itself by rolling back to version 1.00.16 with the recovery utility.
One workaround I noticed with firmware v1.01.03 is that the router will actually assign DHCP addresses to wirelss devices temporarily if it assigns a DHCP address to a device connected to the physical port. This only last for a little before the router stops giving out DHCP address to wireless devices though. It's a shame since I was looking forward to some of the features in the v1.01.03 firmware.
Chuck

Not getting DHCP address on HP 8000 Elite

I'm using the Feb 2010 CD. Windows 2003 DHCP server
Boot with the cd and no dhcp address.
If I type "dhcpcd eth0 -n" enough times I will eventually get an address, although the first time it's usually "err, eth0: Failed to lookup hostname via DNS: Name or service not known"
The same CD works OK with a HP dc7900, dc7800, etc. It looks like they all have the same Intel e1000e nic, but maybe no?

I'm starting to investigate issues that may be similar to yours and I had a
thought that I thought I'd share with you ;-)
In what may be a related situation one of our admins is having issues with
the dhcp client on an openSUSE 11.1 (and 11.2) during and after the install
on some Dell servers. Sometimes the dhcp client will not get an ip address.
After some poking he found that there are in fact two dhcp clients available
: dhcpcd (dhcp client daemon) and dhclient (package is called dhcp-client).
The default client in openSUSE - and presumably the Linux environment of
ZENworks Imaging - is dhcpcd v3.x. It seems that there are a number of
reports of this client being problematic. The maintainer of this client has
recently released v5.x which may resolve the issues with v3.x.
In our testing on openSUSE dhclient works much more reliably than dhcpcd,
where "more" is equal to 100%. None of this helps us of course, but it is
background info that leads up to my idea: is it possible to use the other
client, dhclient in the ZEN Linux environment? I don't know if this client
is even included in the ZEN Imaging Linux environment or not. If it isn't
then maybe it might be possible to modify the initrd/root/linux files to
include it. This would at least let you have another means of acquiring a
dhcp ip address. I'm sorry that I do not have the Linux skills to do more
than make a suggestion...
Cheers,
Ron
PS I have submitted an enhancement request via the openFATE website to have
the dhcp client daemon upgraded to v5.x. Maybe if you think it a good idea
you could login to the openFATE portal and vote it up!

1142 Autonomous AP not passing DHCP address to clients

Hi there,
I do hope someone can help me out here because I am having a nightmare with a single AP.
Setup is as follows:
5 existing APs already on site, all working correctly plugged into a 48 port 2960, (non poe).
customer wants to add another AP to extend capacity.
Installed AP, (config attached) mirrored switchport settings, (below) and fired it up.
Outcome: if you are on a static IP or have received DHCP through another AP then everything works as it should. But DHCP requests are never fulfilled if connected through this AP. (this goes also for a laptop with an existing DHCP address if you go through the \release \renew process) DHCP is served by a server living on the switch.
The AP lives on VLAN 2, hence native .2 on both ends, and wireless clients should recieve a VLAN 1 address. All the other APs, (1131s) are working without a problem and this is driving me NUTS! Have been through configs and every screen of the GUI but cant find any difference in set up. Apart from different AP models the new one is on a pwrinj4 while the others are on pwrinj3's.
Switchport settings:
interface GigabitEthernet0/1
description Connect to wireless AP
switchport trunk native vlan 2
switchport trunk allowed vlan 1,2,1002-1005
switchport mode trunk
AP Config
aaa authentication login default local
aaa authentication enable default enable
aaa authorization exec default local
aaa authorization network default local
aaa session-id common
dot11 vlan-name *** vlan 1
dot11 vlan-name *** vlan 2
dot11 ssid ***
   vlan 1
   authentication open
   authentication key-management wpa optional
   wpa-psk hex ***
username manager privilege 15 password ***
username user privilege 0 password ***
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
encryption key 2 size 128bit *** transmit-key
encryption mode ciphers tkip wep128
encryption vlan 1 key 2 size 128bit *** transmit-key
encryption vlan 1 mode ciphers tkip wep128
ssid ***
channel 1
station-role root
interface Dot11Radio0.1
encapsulation dot1Q 1
no ip route-cache
bridge-group 254
bridge-group 254 subscriber-loop-control
bridge-group 254 block-unknown-source
no bridge-group 254 source-learning
no bridge-group 254 unicast-flooding
bridge-group 254 spanning-disabled
interface Dot11Radio0.2
encapsulation dot1Q 2 native
no ip route-cache
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
bridge-group 1 spanning-disabled
interface Dot11Radio1
no ip address
no ip route-cache
encryption key 2 size 128bit *** transmit-key
encryption mode ciphers tkip wep128
encryption vlan 1 key 2 size 128bit *** transmit-key
encryption vlan 1 mode ciphers tkip wep128
ssid ***
no dfs band block
channel dfs
station-role root
interface Dot11Radio1.1
encapsulation dot1Q 1
no ip route-cache
bridge-group 254
bridge-group 254 subscriber-loop-control
bridge-group 254 block-unknown-source
no bridge-group 254 source-learning
no bridge-group 254 unicast-flooding
bridge-group 254 spanning-disabled
interface Dot11Radio1.2
encapsulation dot1Q 2 native
no ip route-cache
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
bridge-group 1 spanning-disabled
interface GigabitEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
interface GigabitEthernet0.1
encapsulation dot1Q 1
no ip route-cache
bridge-group 254
no bridge-group 254 source-learning
bridge-group 254 spanning-disabled
interface GigabitEthernet0.2
encapsulation dot1Q 2 native
no ip route-cache
bridge-group 1
no bridge-group 1 source-learning
bridge-group 1 spanning-disabled
ip http server
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
control-plane
bridge 1 route ip
line con 0
transport preferred all
transport output all
line vty 0 4
transport preferred all
transport input all
transport output all
line vty 5 15
transport preferred all
transport input all
transport output all
interface dot11Radio 0
ssid ***
no shutdown
interface dot11Radio 1
ssid ***
no shutdown
power inline negotiation injector installed
interface BVI1
ip address 10.25.97.245 255.255.255.0
no ip route-cache
ip default-gateway 10.25.97.1

Hi Scott,
Yes, the only difference is as this is a 1142 I was instructed to put it onto one fo the Gb ports. I tried the Ap on a known working port to rule out switch config to no effect.
Here is the extended switch config:
interface FastEthernet0/44
description Connect to wireless AP
switchport trunk native vlan 2
switchport trunk allowed vlan 1,2,1002-1005
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/45
description Connect to wireless AP
switchport trunk native vlan 2
switchport trunk allowed vlan 1,2,1002-1005
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/46
description Connect to wireless AP
switchport trunk native vlan 2
switchport trunk allowed vlan 1,2,1002-1005
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/47
description Connect to wireless AP
switchport trunk native vlan 2
switchport trunk allowed vlan 1,2,1002-1005
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/48
description Connect to wireless AP
switchport trunk native vlan 2
switchport trunk allowed vlan 1,2,1002-1005
switchport mode trunk
spanning-tree portfast
interface GigabitEthernet0/1
description Connect to wireless AP
switchport trunk native vlan 2
switchport trunk allowed vlan 1,2,1002-1005
switchport mode trunk
interface FastEthernet0/44
description Connect to wireless AP
switchport trunk native vlan 2
switchport trunk allowed vlan 1,2,1002-1005
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/45
description Connect to wireless AP
switchport trunk native vlan 2
switchport trunk allowed vlan 1,2,1002-1005
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/46
description Connect to wireless AP
switchport trunk native vlan 2
switchport trunk allowed vlan 1,2,1002-1005
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/47
description Connect to wireless AP
switchport trunk native vlan 2
switchport trunk allowed vlan 1,2,1002-1005
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/48
description Connect to wireless AP
switchport trunk native vlan 2
switchport trunk allowed vlan 1,2,1002-1005
switchport mode trunk
spanning-tree portfast
interface GigabitEthernet0/1
description Connect to wireless AP
switchport trunk native vlan 2
switchport trunk allowed vlan 1,2,1002-1005
switchport mode trunk
Not sure about the spanning tree settings on the others: I didnt set those up and am a great believer in the "if it aint broke, dont fix it" maxim!

Hyper-V - Legacy NIC not getting DHCP address at boot, but when OS loads the NIC gets a DHCP address

Hi, I have a strange issue with DHCP.
I have a lab environment on a single Hyper-v 2012 Server. AD, DNS & DHCP exist on a single virtual machine, I have a flat network 192.168.1.x, all VM's are on this network. I have authorised DHCP and Setup the scope.
A VM has a legacy adaptor, the legacy nic is configured in the boot order as the first device.
When I boot the machine I do not get a DHCP address, however when the OS boots the Legacy NIC then gets a DHCP address??
I need to use a legacy NIC as I need to PXE boot the VM, however I should get an IP address at boot time, which I don't get.
I have run Wireshark on the DHCP server, I can see the legacy NIC do a "DHCP Discover and the DHCP Server respond with a DHCP Offer" however all communication ends there. I have disable all firewalls and I see no reason for this not to work.
I have done tis before with no issues but I am unable to get this to work on this server!!!!!

Hi
According to your description , it is recommended to make sure or do :
        In your environment , there is no any other valid DHCP, BOOTP or proxy DHCP offers.
        Make sure if the DHCP server is overload.
        So suggest to test that creating a new “internal virtual switch” and change the settings of VM which provide DHCP service to connect to the new “virtual switch”.
        Then create a new VM use legacy NIC also connect to the new “internal virtual switch” and try to PXE Boot.
Hope this helps.
Best Regards
Elton ji
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.

Phones not getting IP address via DHCP server on same VLAN

Hello....we have a new series of Cisco SF-200s and one new Cisco SF-300. All switches are operating in layer 2 mode currently. Let's say for all intents and purposes, all ports are in VLAN1....pretty much default setup. There is a fiber backbone between uplink ports...and it is working correctly it appears.
There is a DHCP server allocating addresses 192.168.0.60 thru 192.168.0.79. Subnet mask is 255.255.255.0.
PCs and laptops successfully receive an IP address and can access things.....such as surfing the internet. Tested that from multiple switches....all seems to work just fine.
However, it seems that some newly purchased phones (Digium models) simply will not acquire an IP address like the PCs and laptops do.
Pretty broad question....but just wondering.
Thanks!

Hi Greg,
Might be interesting to goto the following sections of the GUI disable the discovery protocols;
1. Administration>Discovery -LLDP >properties
2. Administration>Discovery -CDP >Management interface
3 Smartports >Properties > Admministrative Auto Smartports is disabled.
the switches are real smart and may pre-empt what you are trying to achieve.
regards dave

5508 WLC not releasing DHCP addresses

Have a WLC 5508 running 7.0.230 with internal DHCP server. Timeout is 3600 seconds. The IP addresses never seem to be released.
The controller will show 70 clients but 254 addresses will be assigned. Has anyone else experienced this problem?

#Check "Lease remaining time" change in this value on the WLC for the clients that are not currently connected and already connected to it. Watch if its getting removed/refreshed once the lease time is expired.
#Cross reference with cli as well.
#If its an open wlan, client pass by will get an ip, so what admin seeing could be new client keep coming in and its an expected behavior.
#Find if time is static or client's dhcp entry doesn't remove once lease time expired.
#Per design, WLC doesn't release the internal dhcp ip when the client sends deauth to WLC, however, it should when the timer gets expired for clients that were currently not connected.

Router not issusing DHCP addresses to AP clients

So I have configured a DHCP pool on my router to issue DHCP leases to wireless clients in my network - the clients can see the SSID broadcasting and can connect successfully. The only problem is that they don't receive an IP address.
IPCONFIG shows the 169.254 etc address...the network status shows "Limited or no connectivity" when hovering over the icon.
We used to have the clients receive their leases from a server which worked with the IP helper command...is there something simple I'm missing here?
Thanks in advance.

Please see below...
Last configuration change at 16:18:21 UTC Thu Jul 10 2014 by admin
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname XXX
boot-start-marker
boot-end-marker
logging buffered 51200 warnings
no aaa new-model
ip cef
ip dhcp excluded-address 10.26.129.1
ip dhcp excluded-address 10.26.129.253
ip dhcp excluded-address 10.26.129.254
ip dhcp excluded-address 10.26.129.2
ip dhcp pool guest
network 10.26.129.0 255.255.255.0
dns-server 208.67.222.222 208.67.220.220
default-router 10.26.129.1
interface Tunnel5
ip address 172.17.5.4 255.255.255.0
ip mtu 1400
ip tcp adjust-mss 1360
tunnel source 12.1xx.xx.xx
tunnel destination 199.4x.xxx.xx
interface Embedded-Service-Engine0/0
no ip address
shutdown
interface GigabitEthernet0/0
description Data Networks
no ip address
duplex auto
speed auto
interface GigabitEthernet0/0.1
description Main Data VLAN
encapsulation dot1Q 1 native
ip address 10.27.129.2 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/0.3
description DMZ VLAN
encapsulation dot1Q 3
ip address 10.28.129.2 255.255.255.0
interface GigabitEthernet0/0.20
description Guest VLAN
encapsulation dot1Q 20
ip address 10.26.129.1 255.255.255.0
ip access-group 121 in
interface Serial0/0/0
description XXX
ip address 12.1xx.xx.xx 255.255.255.252
ip nat outside
ip virtual-reassembly in
encapsulation ppp
service-module t1 cablelength short 440ft
service-module t1 timeslots 1-24
ip forward-protocol nd
ip http server
ip http access-class 23
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip route 0.0.0.0 0.0.0.0 12.1xx.xx.xx
ip route 10.10.0.0 255.255.255.0 172.17.5.5
ip route 10.10.200.0 255.255.255.0 172.17.5.5
ip route 10.27.130.0 255.255.255.0 172.17.5.5
ip route 10.27.131.0 255.255.255.0 172.17.5.5
ip route 10.28.129.0 255.255.255.0 10.27.129.1
ip route 129.155.20.0 255.255.252.0 10.27.129.1
ip route 129.155.84.0 255.255.252.0 10.27.129.1
ip route 129.155.168.0 255.255.248.0 10.27.129.1
ip route 172.17.0.0 255.255.255.0 172.17.5.5
ip route 172.17.2.0 255.255.255.0 172.17.5.5
ip route 172.17.3.0 255.255.255.0 172.17.5.5
ip route 192.168.2.0 255.255.255.0 172.17.5.5
access-list 2 permit 12.2xx.xx.xx
access-list 2 permit 10.27.129.0 0.0.0.255
access-list 2 permit 192.168.2.0 0.0.0.255
access-list 2 permit 10.27.131.0 0.0.0.255
access-list 2 permit 10.27.130.0 0.0.0.255
access-list 2 permit 10.10.0.0 0.0.0.255
access-list 2 permit 10.10.200.0 0.0.0.255
access-list 2 permit 12.2xx.xxx.xxx 0.0.0.7
access-list 2 permit 172.17.5.0 0.0.0.255
access-list 2 permit 199.4x.xxx.xxx 0.0.0.15
access-list 2 permit 10.26.129.0 0.0.0.255
access-list 121 permit tcp any host 10.27.129.31 eq 67
access-list 121 permit udp any host 10.27.129.31 eq bootps
access-list 121 permit ip any any
access-list 121 permit ip 10.26.129.0 0.0.0.255 host 10.14.0.6
access-list 121 deny   ip 10.26.129.0 0.0.0.255 10.0.0.0 0.255.255.255
access-list 121 deny   ip 10.26.129.0 0.0.0.255 172.16.0.0 0.15.255.255
access-list 121 deny   ip 10.26.129.0 0.0.0.255 192.168.0.0 0.0.255.255
access-list 121 deny   icmp 10.26.129.0 0.0.0.255 10.0.0.0 0.255.255.255
access-list 121 deny   icmp 10.26.129.0 0.0.0.255 172.16.0.0 0.15.255.255
access-list 121 deny   icmp 10.26.129.0 0.0.0.255 192.168.0.0 0.0.255.255
control-plane
line con 0
login local

WLC2412-Clients Not receiving DHCP addresses

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. Any advice would be greatly appreciated.
*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.
*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.

(Cisco Controller) show>interface detailed management
Interface Name................................... management
MAC Address...................................... 64:00:f1:91:5d:40
IP Address....................................... 192.168.8.3
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 192.168.8.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 8
Quarantine-vlan.................................. 0
Physical Port.................................... 1
Primary DHCP Server.............................. 192.168.8.49
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... No
Guest Interface.................................. No
L2 Multicast..................................... Enabled

VWLC clients getting DHCP address from management VLAN

Hi,
We have a strange scenario whereby some wireless employees are obtaining addresses from the management VLAN.
Some details:
DHCP managed by MS DHCP 2008 R2 (in remote data centre)
Cisco vWLC AIR-CTVM-K9 running v7.6.110.0
AP's are a mix of 2602 and 3702 (46 and 2 of each respectively)
SSID's are employee, guest, and production devices (all mapped to their own interface with relevant VLAN tag as per normal)
AP's all in FlexConnect mode as per vWLC caveats
Some employees are receiving addresses in the wireless management VLAN. This network only has six DHCP addresses available as it is solely for AP's, WLC and HSRP gateway. Obviously this gets exhausted very quickly leaving us with a scenario where clients are not obtaining DHCP addresses.
I understand that with FlexConnect mode, it will assign IP's from the native VLAN. What I don't understand is why most clients receive addresses in the correct VLAN, but a handful do not, and then cannot get an address from DHCP. Obviously the ideal scenario would be to put the AP's into local mode but unless this has changed in a SW release then I don't believe it's possible...
My question is: How do I get ALL the employees to obtain addresses from their interface and not the management VLAN?
Thanks in advance.

Hi,
I think we need a closer look to your configurarion to eliminate some possibilities:
- What is the WLAN security you choose?
- What is the interface that is configured under the WLAN?
- Does your WLAN have local switching enabled?
- If your security is using RADIUS server, do you have AAA override enabled under the WLAN config?
- If your security is using RADIUS server, do you send any attributes to the users?
- You have eliminate that clients that got management vlan IPs are always on same AP or they can be on any AP.
HTH
Amjad

DHCP via Hyper-V VM, Server2012r2 Hyper-V host, clients not getting IP address

You have to authorize a dhcp server as Britv8 says. That's the only way it'll start dishing out leases. That's standard for Windows DHCP server in an AD Domain.
Also there's 0 reason to mention Hyper-V here. The whole point of virtualization is to do hardware level abstraction.

I recently encountered this. Setup:
Initial setup of the system was at a different location from its final destination, with different network equipment (switches) between the two. No teaming is involved, however.
Set up the system at its final destination, with DHCP via a Hyper-V VM (Server2012r2), Server2012r2 Hyper-V host, physical clients on the lan were not getting IP address.
The physical server box has a 4-port Intel Gigabit ethernet card.
I moved the setup (Hyper-V Virtual Switch manager) so that the interface for the DHCP server VM was isntead using one of two built-in Broadcom adapters.
While this topic seemed promising,
http://community.spiceworks.com/topic/251317-hyper-v-vm-not-leasing-ip-s-dhcp
unfortunately, "fiddling about" was not what I was looking for as possible solution.
My notes for the resolution:
Hyper-V system running...
This topic first appeared in the Spiceworks Community

Distributing IP address only not working

Hi everybody!
I have a "big" problem with my brand new AirPort Extreme (802.11n).
I bought it as replacement to my old AirPort Express (802.11g) because I needed an Ethernet LAN port but now the new one can't do what the old good airport express was doing perfectly.
This is my network configuration: there's the provider's router (Zyxel Prestige-645R) with just one ethernet port which is connected to the AirPort Extreme's WAN port. I've deactivated the router's DHCP service but NAT service is still active.
The AirPort Extreme is configured to distribute a range of IP addresses only, without acting as NAT.
This means that it only uses DHCP to distribute the IP addresses, while port forwarding is done by the router's NAT.
I did this because I needed to see my router from any wireless client and because double-NAT caused me few problems in the past (I can't manage to switch off the NAT on the router).
So the router is 10.0.1.1, the AirPort Extreme 10.0.1.2 and the company's server 10.0.1.250.
(The server handles DNS service)
Now, the AirPort Extreme is configured to distribute IP address from 10.0.1.3 to 10.0.1.21.
This is AirPort Extreme's internet configuration:
IPv4: Manual
IP Address: 10.0.1.2
Subnet Mask: 255.255.255.0
Router: 10.0.1.1
DNS Servers: 10.0.1.250
The problem that came out only with the AirPort Extreme is that it fails to give internet connection to DHCP clients! If I assign a static IP it works, if use DHCP it doesn't.
The only abnormal thing I found out is that DHCP clients get as Router the IP 10.0.1.2 (which is the AirPort Extreme) instead of 10.0.1.1 (which is the provider's router). I THINK the problem is there...
The strange thing is that it's configured exactly as the AirPort Express and that worked!
Any advice?
It's URGENT.
Thanks

That can be an option.
I thought it would have been better this way... I'll try and let you know.
The only bad thing is that with the AEBS I could assign static IPs via DHCP using the DHCP client ID, I was considering that for not having to change all the configuration on each computer every time it changes.
But if this is the only way, well I'll use it.

WRT54G: Static mode set on WAN side, but still sometimes pulls address via DHCP!

We've had (6) WRT54G (v5) installed in a building, for about (2) years now, with no previous problems. Now, ALL of them are doing something weird. They are all set for Static mode on the WAN side (we have static ip addresses for these), yet every now and then they will spontaneously pull an address via DHCP on their own. When they do this, the setting itself doesn't change. It will still show "STATIC" in the pull down list. But, the address will no longer be the address we assigned to the unit, and will instead appear to be an address that it pulled via DHCP.
Thanks, in advance, for any help and insight into this strange problem.
David

Ah. In that case, we're not going to put our client through the frustration of chasing a ghost in the machine. We'll just replace them with new ones. But, I'll try this on them in my spare time and let you know how it goes.
Thanks for your assistance,
David
Message Edited by ld-systems on 09-19-2007 08:01 AM

Cisco 891 not getting IP address with DHCP with latest IOS

Hi,
I have a few Cisco 891 routers that are configured as DHCP clients on the WAN interface.
For some reason when I boot the router with a late IOS, the router is not receiving an address.
It works just as expected with the older IOSes.
Any ideas of what changed?
This is how the interface is configured:
interface FastEthernet8
ip address dhcp
no ip redirects
no ip unreachables
no ip proxy-arp
duplex auto
speed auto
no cdp enable
This IOS does not work:
c890-universalk9-mz.154-3.M2.bin
While these do work:
c890-universalk9-mz.150-1.M7.bin
c890-universalk9-mz.151-2.T2.bin
c890-universalk9-mz.152-1.T1.bin
Doing a "show ip interface brief" shows that FastEthernet8 is unassigned with the affected IOS.
With the older IOSes there is an IP address.
I had to downgrade two routers due to this issue, and did not have plenty of time to troubleshoot.
Both of the routers are connected to DSL from the same ISP...
Anyone seen anything like this before?

Add another one to the list.
I have a MacBookPro3,1 that connects to WIFI no problem. It used to connect to ethernet when I originally bought it, however I've been using WIFI exclusively for the past 2 years.
Recently I had a need to connect via ethernet and it wouldn't work at home (apple airport router). I next tried connecting via ethernet at a friends house using a linksys WRT54G, no dice either. I have the computer in the lab today (University Network) and I get the same error. 3 different locations, 3 different routers, all same problem. It used to connect to home and university networks ethernet right away.
IP address assigned is 169.xxx.xxx.xxx - subnet - 255.255.0.0
no other info. It's showing up as connecting to the network, but unable to communicate with DHCP. It does work if I enter all of the information in manually.
At first I thought I had messed something up in networking preferences as I tend to play around with things alot. However I did a complete system format, and fresh install of OSX Lion and I still have the same problem, without any of my meddling around to confuse things.
What gives?

Satellite Pro L300-12H not getting IP from DHCP router via cable

My Vista Premium SP1 laptop is connected via wireless connection to a Buffalo ADSL modem/router model WBMR-G54 which works fine. However, I tried the other day to connect up the LAN card via RJ45 cable to the router and it won't work! I get the message "limited connectivity" and an IP of 169.254.xxx.xxx which suggests it is not getting an IP from the router.
I been on various web sites and tried all sorts of things like unchecking ipv6 on the LAN card properties, turning off DHCP Broadcast flag in the registry (as per micrsoft issue) etc. but to no avail.
Anybody got any suggestions to get it working?
NB: I took the laptop into work and connected it to the Windows 2003 server network and got a DHCP IP straight away!?!

Hi wakefijr,
To be honest, it's still worth checking with your ISP or the router manufacturer because they will be able to guide you through the settings of the router. You're quite right about the 169.254.xxx.xxx IP address, it means that the DHCP server within the router isn't assigning an IP address to the laptop so the laptop is assigning itself an IP address via APIPA.
Short of checking the DHCP router settings, one other thing you could do is disable APIPA and try using the alternate IP configuration, this is how:
* Go to the *Start Menu* and in the *Start Search* box, type in *ncpa.cpl* and hit Enter, this will open up network connections
* Go into the properties of the LAN and properties of IPv4
* Click on the *Alternate Configuration* tab
* You will see that it is set to APIPA, you can change to *User configured* and input an available IP address, the correct subnet mask (most likely 255.255.255.0) and default gateway.
* Click *OK* as many times as you need to save all changes, then reboot with the RJ45 cable connected.
What this will then do is make the laptop try looking for a DHCP server to assign an IP address, but if no DHCP server is assigning an IP address to this laptop then it will assign one that should work on the network.
But really check router configuration as a priority.

ABS not distributing DHCP addresses via hub

Similar Messages

Maybe you are looking for