DHCP IP address to client

How machine get IP address from particular subnet
Like we have DHCP server where three scopes are configured & I want to assign IP address from SCOP B to my new machine how can I to do that please suggest.

Hello,
either you have to configure the mentioned IP-Helper, check the router/switch documentation you use to connect the subnets or you have to install a DHCP relay agent in the subnet that should get the DHCP lease from a DHCP server in a different subnet.
http://technet.microsoft.com/en-us/library/dd469685.aspx
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

Similar Messages

Clients not receiving DHCP IP address from HREAP centrally Switched Guest SSID

Hi All,
I am facing a problem in a newly deployed branch site where the Clients are not receiving DHCP IP address from a centrally switched Guest SSID. I see the client status is associated but the policy manager state is in DHCP_REQD.
The dhcp pool is configured on the controller itself. The local guest clients are able to get DHCP and all works fine, the issue is only with the clients in the remote site. The Hreap APs are in connected mode. Could you please suggest what could be the problem. Below is the out of the debug client.
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Adding mobile on LWAPP AP 3c:ce:73:6d:37:00(1)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Reassociation received from mobile on AP 3c:ce:73:6d:37:00
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Changing ACL 'Guest-ACL' (ACL ID 0) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1393)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Applying site-specific IPv6 override for station 10:40:f3:91:7e:24 - vapId 17, site 'APG-MONZA', interface 'vlan_81'
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1393)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Applying IPv6 Interface Policy for station 10:40:f3:91:7e:24 - vlan 81, interface id 13, interface 'vlan_81'
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Applying site-specific override for station 10:40:f3:91:7e:24 - vapId 17, site 'APG-MONZA', interface 'vlan_81'
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1393)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 STA - rates (8): 140 18 152 36 176 72 96 108 0 0 0 0 0 0 0 0
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Initializing policy
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Change state to AUTHCHECK (2) last state AUTHCHECK (2)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 AUTHCHECK (2) Change state to L2AUTHCOMPLETE (4) last state L2AUTHCOMPLETE (4)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP 3c:ce:73:6d:37:00 vapId 17 apVapId 1
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 L2AUTHCOMPLETE (4) Change state to DHCP_REQD (7) last state DHCP_REQD (7)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 apfMsAssoStateInc
*apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 apfPemAddUser2 (apf_policy.c:222) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Idle to Associated
*apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 Scheduling deletion of Mobile Station: (callerId: 49) in 28800 seconds
*apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 Sending Assoc Response to station on BSSID 3c:ce:73:6d:37:00 (status 0) ApVapId 1 Slot 1
*apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 apfProcessAssocReq (apf_80211.c:4672) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Associated to Associated
*apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) State Update from Mobility-Incomplete to Mobility-Complete, mobility role=Local, client state=APF_MS_STATE_ASSOCIATED
*apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) pemAdvanceState2 4183, Adding TMP rule
*apfReceiveTask: May 24 11:35:53.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Adding Fast Path rule
type = Airespace AP - Learn IP address
on AP 3c:ce:73:6d:37:00, slot 1, interface = 13, QOS = 3
ACL Id = 255, Jumbo F
*apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 7006 IPv6 Vlan = 81, IPv6 intf id = 13
*apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Successfully plumbed mobile rule (ACL ID 255)
*pemReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0
*pemReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 Sent an XID frame
*apfMsConnTask_3: May 24 13:26:49.401: 10:40:f3:91:7e:24 Updating AID for REAP AP Client 3c:ce:73:6d:37:00 - AID ===> 1
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) DHCP Policy timeout
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Pem timed out, Try to delete client in 10 secs.
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 Scheduling deletion of Mobile Station: (callerId: 12) in 10 seconds
*osapiBsnTimer: May 24 13:28:59.315: 10:40:f3:91:7e:24 apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
*apfReceiveTask: May 24 13:28:59.315: 10:40:f3:91:7e:24 apfMsExpireMobileStation (apf_ms.c:4897) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Associated to Disassociated
*apfReceiveTask: May 24 13:28:59.315: 10:40:f3:91:7e:24 Scheduling deletion of Mobile Station: (callerId: 45) in 10 seconds
*osapiBsnTimer: May 24 13:29:09.315: 10:40:f3:91:7e:24 apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 Sent Deauthenticate to mobile on BSSID 3c:ce:73:6d:37:00 slot 1(caller apf_ms.c:4981)
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 apfMsAssoStateDec
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 apfMsExpireMobileStation (apf_ms.c:5018) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Disassociated to Idle
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Deleted mobile LWAPP rule on AP [3c:ce:73:6d:37:00]
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 Deleting mobile on AP 3c:ce:73:6d:37:00(1)
*pemReceiveTask: May 24 13:29:09.317: 10:40:f3:91:7e:24 0.0.0.0 Removed NPU entry.

#does the client at the remote site roams between AP that connects to different WLC?
#type 9 is not good.
*pemReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0
#Does your dhcp server getting hits.
#Also, get debug dhcp message & packet.
#Dhcp server is not responding.
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) DHCP Policy timeout
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Pem timed out, Try to delete client in 10 secs.

DHCP still giving out addresses to clients on the Deny filter

My DHCP server is handing out addresses to clients that I have put on the deny list. The "Enable Deny List" is checked. Its not to every client either. It is just a handful that keeps popping back. What am I missing?

Hi Alphateam,
Have you confirmed that the deny is on all interfaces, wired and wireless of said machines.

Incorrect DHCP server address to wireless client

Guys,
I have deployed a centralized wireless architecture with 2 x wisms in each of our DCs. I just noticed the clients are receiving incorrect DHCP server address, please note there is no issue with connectivity, i just want to know why incorrect DHCP server address is handed out to the clients.
The DHCP server address received is apparently virtual interface address of the WiSM. i am running WiSM firmware 7.0.116.0
Any information is appreciated.
Cheers
AP

DHCP proxy is pretty usless in my mind. It was something that lingered from the old airespace days. In fact if you ask many cisco se's they will tell you they wished they didnt default to proxy. Also, if you ever use cisco ISE, you will need to disable proxy, becuase you will need to configure a helper pointing to the ISE box for DHCP finger printing.
Steve points out, if you use the WLC as a DHCP server it is a requirement to have it on. But we all agree here on CSC (Steve, Leo, Blake, myslef), that the DHCP server on a WLC is not robust and is problematic at times.

IOS7 DHCP IP address scopes being depleted

I work for a large school district in Texas. We have a large deployment of iPads (10,000+) as well, we encourge BYOD.
Our district has recently updated to iOS7. We now are experiencing IP address scopes running out of IP's, 6000 per campus for students, 5 campuses. With some testing we found the iOS7 devices leave the network - IE: go to sleep mode or disassociate from wireless in some fashion, generally for just a short period, 1 hr or 2. Once the iOS7 devices rejoin the network they are not keeping their original IP address and allocated another IP thus in a days time depleting IP addresses.
Our DHCP lease times are set for 8 hours.
We have tested this with iOS6 devices and these devices leave and rejoin and retain their original IP address from the scope.
I was wondering if any other ISD or other enviroment with a large deployment of iOs devices have seen this problem?
Thanks
LB

Hi All,
Found this thread when searching for a solution to a similar dhcp problem on Friday.
I came across this issue when building a wireless env similar to LB_MISD. Although in my env I have a linux server for dhcp and have two pools (one for known and another for unknown clients). Ios 7 devices were actually making so many requests it caused the DHCP server to stall at times.
From the logs I noticed that I had problems with unknown clients but not with known clients ..... the difference - an assigned hostname in dhcp for the known clients.
IOS 7 seems to require a hostname be given to the client device with the rest of the dhcp offer. To get around this I added an extra line to the dhcp pool that send the clients mac address back as it's hostname. It does not appear to actually get used by anything but does seem to fix the problem.
"option host-name = concat ( binary-to-ascii (16, 8, ":", substring (hardware, 1, 6));"
I don't know what the equivalent config would be for a windows server or home router - although a workaround might be to grab the mac addresses of all the IOS 7 devices and reserve an address and create a hostname for each device --- a pain yes but at least the dhcp server may work for everyone else?

AP12000 can not assign IP address to client

upgrade to the latest firmware.
want to setup ap1200 as a dhcp server for wireless client. but it seems there something wrong with setup. client cannot get IP address from AP. please take a look my configuration
version 12.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname xxx03
enable secret xxx.
username admin password xxx
ip subnet-zero
ip dhcp pool xxxpool3
network 192.168.105.72 255.255.255.248
default-router 192.168.105.65
domain-name xxxx.com
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
ssid XXX WLAN
authentication open
guest-mode
speed basic-1.0 basic-2.0 basic-5.5 basic-11.0
rts threshold 2312
station-role root
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 FastEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
bridge-group 1
no bridge-group 1 source-learning
bridge-group 1 spanning-disabled
interface BVI1
ip address 192.168.105.69 255.255.255.192
no ip route-cache
ip default-gateway 192.168.105.65
ip http server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag/ivory/1100
bridge 1 route ip
line con 0
line vty 0 4
login local
line vty 5 15
login
end

You will need to provide some additional detail about your setup.
Version of CRM?
Is IDF and/or ADFS setup?
Some basic things to check:
From the client computer, does a nslookup of the CRM server name resolve? If not, it may be a DNS issue.
Is the CRM site in IIS listening to all IP addresses? Or set to listen to only one?
Was a host header set up in IIS for the CRM site?
What error do you get when you use the CRM server name from the client machine? Only IP addresses working is a sign of a kerberos issue. Check that you have the correct SPN's created for a non machine account running the CRM app pool in IIS.
Jason Peterson

Wireless 2504,user not getting dhcp ip address

Hi i have configured wlc 2504 .in that i have configured two interfaces.one is guest, 2nd is internal user,
the pblm when user try to connect with that contain ssid user not getting ip address,
i have connected only one link between core to wlc on port 1.for guest interface i used port 4.but no physical link.
Please help this

There are multiple ways how the clients can get their IP-address in a WLC deployment.
From the WLC-FAQ:
How does DHCP work with the WLC?
A. The WLC is designed to act as a DHCP relay agent to the external DHCP server and acts like a DHCP server to the client. This is the sequence of events that occurs:
Generally, WLAN is tied to an interface which is configured with a DHCP server.
When the WLC receives a DHCP request from the client on a WLAN, it relays the request to the DHCP server with its management IP address.
The WLC shows its Virtual IP address, which must be a non-routable address, usually configured as 1.1.1.1, as the DHCP server to the client.
The WLC forwards the DHCP reply from the DHCP server to the wireless client with its Virtual IP address.Note: You can also configure the WLC to act as a DHCP server. For more information on how to configure a WLC as a DHCP server, refer to the Configuring DHCP Scopes section of the document Cisco Wireless LAN Controller Configuration Guide Release 5.1.
If you want more in-depth information you should read "DHCP with the WLC":
http://www.cisco.com/en/US/partner/products/ps6366/products_tech_note09186a0080af5d13.shtml
Don't stop after you've improved your network! Improve the world by lending money to the working poor:
http://www.kiva.org/invitedby/karsteni

Cisco E1000 wont connect to internet anymore - not getting DHCP ip address from Comcast modem

Very strange issue...
I have Comcast HSI and have been using my Cisco (Linksys) E1000 for about 3 years now. Bought it as a refurb.
My issue is that the E1000 is NOT receiving the DHCP info from my Comast modem.
The internet works when my laptop is directly attached to the modem; but when connecting the modem internet port
to the E1000 internet port it is NOT grabbing my ISP DHCP ip address thus no clients can broswe 'wired or wireless'.
I even updated the firmware and am starting to think its time to get a 'BRAND NEW' router as this makes NO SENSE!
I cannot release/renew as i have NO ip address to release. I have even tried to configure the E1000 as a static
using the ipconfig/all from when the laptop and modem was connected. Comcast says they see nothing on their end.
I also factory defaulted the router and redid the config to no avail.
Any help would be appreciated.
Solved!
Go to Solution.

You need to enable MAC address clone on the router to recognize the connection from your cable modem. The link below would tell you how to configure the router to work with a cable connection and how to do MAC address clone.
Setting up a Linksys router with Cable Internet service

802.1x and DHCP assigned addresses

I've done a lot of reading on this but I am still confused. I'm not a Microsoft guru so I don't really know waht is going on with login scripts, or cached user/pass.
Scenario 1
==========
I have 802.1x implemented and Joe the contractor comes into the office and plugs in his laptop. He is a guest. I allow guests to have access to a guest VLAN. How can Joe automatically get an IP address, or does he have to do ipconfig /renew?
Scenario 2
==========
What is the behind the scenes process that takes place for my corporate users that login to a domain....how do they get DHCP assigned addresses?
Thanks

I assume from what you have written 'Joe' doesn't have an 802.1x supplicant on his PC? Therefore the switchport eapol frames are ignored by the PC and after a timeout the port is placed in the guest vlan. You need to make sure DHCP is enabled for the guest vlan - either add the appropriate entried to the protecting ACL or add a scope on the router? Depending on the timeouts you may have some delay issues here; I would test this before you roll it out.
For clients with 802.1x supplicants what happens is the PC effectively thinks it is disconnected from the network until the supplicant has authenticated. Once it has authenticated the PC thinks the network adapter is then connected and it will attempt to lease an IP address by broadcasting a DHCP request.
There are however a few 802.1x supplicants and I am not sure how they all integrate with the host O/S. I know the built-in Microsoft one operates as I have described.
HTH
Andy

WRT54GX2 Wireless Security Enabled DHCP blocked for wireless clients

Hey gang,
My subject says it all. Yesterday I updated my WRT54GX2 version 1's firmware to the latest and greatest.I first reset the box, and rebooted. I updated the firmware. On the first attempt I picked the wrong image file. The machine halted and told me bad image. I then found and installed the correct image. I then added an Admin password, and entered a new SSID. I left the DHCP settings at the default. I then set wireless security at WPA Personl/WPA2 with TKIP&AES.
I found the wired client could obtain an IP address and to connect to the internet. The wireless clients could connect, but could not obtain an IP address.
I left the wireless security settings off.
Any suggestions?

The wireless security settings are correct. The wireless clients "CONNECT" to the WRT54GX2. The clients stall on obtaining an IP address via DHCP. Fixing the clients with static IP addresses also does not work.
I repeat: The wireless clients successfully connect to the WRT54GX2. The WPA/WPA2 & TKIP/AES settings are correct. The clients cannot receive a dynamic IP address.
On Friday I will reset the box for 30+ seconds. I doubt this will have any effect. I reset it on Tuesday twice on Tuesday, and still have the problem.
Any help appreciated.
-WJ

DHCP exclude address range option config on Instant 2.0

Q: DHCP exclude address range option config on Instant 2.0
A: This article applies to Instant 4.2 and above.
Before 4.2, Use exclude-address as a range option was not available.
Since IAP is getting used as an Edge device, the features needs to be in compliance with industry standard.
From 4.2 onwards, IAP local DHCP server will support exclude IP address as a range.
With this feature we are supporting the following
A. exclude-address ip1
B. exclude-address ip1 ip2
Show dhcps command will show the excluded range and available range

I found this on TCPIPGUIDE.com that supports my findings.
"One difference between BOOTP and DHCP is that certain communications from the client to the server are unicast. The most noticeable instance of this is when a client tries to renew its lease with a specific DHCP server. Since it sends this request unicast, it can go to a DHCP server on a different network using conventional IP routing, and the relay agent does not need to be involved."

Hardware-address or client-indentifier

I read several docs about the dhcp manual bindings. Im not even tried yet but can somebody tell me which is right(hardware-address or client-indentifier) for Cisco IP Phones?.
Thanks.

Paul, the 01 is at the end or at the begining of the mac ?.
Paul, I have one of those "nice" user that do not wat vlans in the network. Is a 25 ip phones and 30 pcs, "corportate policy" he said....
I had to convince him to use dhcp for the ip phones.
Im looking for a way to give ip addr to the ip phones only.
Because there is only one vlan I dont want the dhcp lease ips to the pcs, only for ip phones.
Manual bindings may be, but also I need some docs for dhcp class.
Can you give some ideas?.
Thanks.

PXE Boot a Hyper V Guest - Not receiving a DHCP IP Address

Hello Everyone,
I am trying to PXE boot a Hyper V guest, but am not getting a DHCP IP Address. Eventually the DHCP query times out and loads into the guest OS I have manually installed. See the PXE Boot Screen below. When in the installed guest OS, I do receive
a DHCP IP address as shown below. I am utilizing the Legacy Network Driver. I don't think it is related to VLAN identifier, but tried with/without and still no go. Any ideas what could be preventing this? Please let me know.
PXE Boot Screen:
CLIENT MAC ADDR: 00 15 5D F2 99 0C GUID: B366BBA1-D503-4D64-A77E-77474F3A2193
DHCP.........-
PXE-E51: No DHCP or proxyDHCP offers were received.
DHCP IPCONFIG in Guest OS:
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix . : mywork.com
   IPv4 Address. . . . . . . . . . . : 10.242.242.251
   Subnet Mask . . . . . . . . . . . : 255.255.255.128
   Default Gateway . . . . . . . . . : 10.242.242.129
Thanks,
Ron

Hi Ron,
A solution is provided in this thread. You may need to have a look on the steps below:
• PXE-E51: No DHCP or proxyDHCP offers were received.
The client did not receive any valid DHCP, BOOTP or proxyDHCP offers. To resolve this issue, check each of the following network configuration items:
DHCP services are not available on the network to which the PXE-enabled NIC is connected.
A DHCP proxy or IP helper address is not configured for the subnet on which the PXE client is connected.
The switch port connected to the PXE NIC is running Spanning Tree Protocol, EtherChannel Protocol, or Port Aggregation Protocol and is thus not activated immediately when a link is detected. This forces the DHCP request from the PXE client to timeout.
DHCP is available on the network, but PXE is not.
The network cable is not attached to the PXE-enabled NIC on the target server.
See: http://social.technet.microsoft.com/Forums/en-US/d06413a4-af2b-4736-a510-c0a68eb880cf/cannot-get-certain-machines-to-pxe-boot
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

WTR54GS Fails to obtain a DHCP IP Address from Upstream

Greetings!
I had effectively given-up on Linksys Router WTR54GS, as it was advertised that it could be plugged into a pre-existing network (friends home network, a hotel room ethernet jack, etc), but sadly the WTR54GS itself is incapable of obtaining a DHCP IP Address from an upstream DHCP server (like the hotel, etc).
I have tried repeatedly to work with Linksys Support but everyone wants to blame the upstream router, suggesting that I change it's configuration to "Bridged-mode". Yeah, right. Like I'm going to walk down to the hotel lobby main desk and tell them that they need to place THEIR network in bridged mode just so my WTR54GS will work. I was willing to believe that the first router (version 2.0) that I was sent was defective, and let Tech Support talk me into returning it to my vendor and seeking a replacement.
I receieved the replacement (this time version 1.0) and had EXACTLY the same problem. I returned that one as well (marked defective) after talking with Ellen in Linksys 2nd Level Technical Support. She promised this would be referred to the Linksys Engineering group for further study. This was 4+ months ago.
I would like to buy another one, but am hesitant to buy because I just do not trust Linksys Technical Support anymore. Can someone please confirm that Linksys Engineering is aware of this problem, acknowledges its existence, and has resolved (or is at least working on resolving) this problem?
-Elrendhel
Forum Administrator, Product Reviewer, & Moderator at MobilitySite,
Forum Admin, Lead Tech Support Mgr & Moderator at GPS Tuner,
Moderator at Microsoft's Windows Mobile Owners Circle forums.

So you have connected WTR through the correct (blue) port to the internet connection?
You have configured the WTR for wired internet connection type?
You have configured the WTR for DHCP?
What does the WTR say on the Status page?
Have you tested the WTR inside your home network?

DHCP beginning address problem.

Hi guys,
I cannot understand how to configure my TC. I put exactly the same network settings as they were in the Airport Express to share the Internet connection. Everything works fine except the internet itself. The problem as I see it is that dhcp beginning address cannot be set far away from the static IP. In my case, the static IP is 213.170.70.** and I only can change these ** last figures in the dhcp range.
But this conflicts with my provider and I have no internet while the TC itself works fine. If I set "share the only address" it doesn't help either.
Anybody can help?
Many thanks in advance.

None really. These are the three IP Address ranges available for Private Networks. The Internet Engineering Task Force (IETF) has directed the Internet Assigned Numbers Authority (IANA) to reserve these IPv4 address ranges for private networks. This has been published in RFC 1918.
More info: Wikipedia: Private network

DHCP IP address to client

Similar Messages

Maybe you are looking for