Wi Fi connection dhcp bogus address

New Iphone --- Im a network admin and im trying to set up my personal home wireless network on my I phone.
linksys router -- yes mac filter wep 128
phone appears to connect but is diplaying bogus ip address's outside my network and wont allow me to connect to itunes ==== ANy ideas would be greatly appreciated...

What do you mean by Bogus IP address?
If you have a Linksys Router and have not customized it too much. Then the IP and Router IP should both start with 192.
On the iPhone go to Settings-WiFi- Tap on your network, then Tap on Renew Lease. See if that allows a new IP address to hit the iPhone.
If it does not. Then tell your iPhone to Forget this Network, and Do not reconnect.
Now power the Linksys Router off for 2 to 5 min. Then power back on. In 2 to 3 min go to your iPhone. Connect to your network. And see if valid IP address information enters.
Please also remember if you are using Mac Address Filtering that you will need to input the iPhones Mac address into the iPhone itself.

Similar Messages

  • 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

  • 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?

  • 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 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

  • 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

  • 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.

  • 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]

  • Windows storage server 2012 share not connecting by share name but connecting thru IP address from windows XP machines

    We have a windows storage server 2012 (HP storage server) in our domain. All of sudden We had a issue, connecting the server shares using the share name only from XP machines, but it is connecting through IP address with a delayed response. We are getting
    the below error message from all the windows XP SP2 machines in our domain.
    "\\<share name> is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have a access permissions.
    Login Failure: The target account name is incorrect."
    But it is connecting while we are trying from windows 7 machines.  Also the other server shares (Windows 2003 server) are connecting without any issues using the share name. In addition to this we gave everyone permission for this share. And it worked
    well before but not now. Could you please suggest any solution for this complex issue?
    Thanks,
    UdayaKumar S

    Hi,
    We are getting the below critical alert mail often from our storage server. This could be the problem? 
    vent from Blade NODE01.*****.com, In Enclosure: EM-E83935ED70F6, Network Interface Lost Connectivity.
    Description: "A network interface has failed. An Ethernet adapter's status changed from OK to Error, or an Ethernet team's status changed to Error from another state."
    Source: CIM Indication from CSP Provider
    Date: 02-06-2014 Time: 18:52:26
    Blade: NODE01.****.com
    NetworkAddresses:
    Severity is Critical
    Recommended Actions: Check the network cables, switches, and hubs for the cause of the failure.
    Note: For More information please refer the Windows System Logs in the Event Viewer

  • Azure Virtual Machine cannot connect to Internet addresses following update on 8/7/2014

    I've got a Windows Server 2012 virtual machine running in Azure that prior to system updates that were rolled out last week could connect to Internet addresses such as Yahoo.com without issue. I do not currently have any virtual networks configured for this
    Azure tenant nor have I modified any of its network settings, so the VM was making the connections with its default network configuration. On August 7, 2014 I rebooted the virtual machine to apply some required system updates to the operating system, and following
    that reboot the VM could not longer connect to the Internet. I am able to lookup domains in DNS, but cannot ping those domains from the command line or open web sites via a browser.
    I've released its IPconfig via the command line and rebooted the server multiple times, both from within a remote desktop connection and from the Azure Management Portal, but these actions have not resolved the issue. 
    Are there additional configuration steps I need to take to reconnect this VM to Internet sites, or has something changed which requires me to make further changes?
    Thank you,
    John
    MCITP and MCTS: SharePoint, Virtualization, Project Server 2007
    My books on Amazon: The SharePoint 2010 Disaster Recovery Guide and
    The SharePoint 2007 Disaster Recovery Guide.
    My blog: My Central Admin.

    Just to close this out, I've been able to resolve the issue. It looks like somehow a Windows Update changed the proxy server settings in Internet Options on the server, and that was preventing traffic from successfully leaving the server. Once I removed
    that setting, the issue was resolved.
    MCITP and MCTS: SharePoint, Virtualization, Project Server 2007
    My books on Amazon: The SharePoint 2010 Disaster Recovery Guide and
    The SharePoint 2007 Disaster Recovery Guide.
    My blog: My Central Admin.

  • Releasing unused DHCP IP addresses in OSX Server 10.4

    In OSX Server 10.4.11 is there any way to release unused DHCP client addresses in the Server Admin app? We have 73 clients showing (and only 30 on the network) because various computers have been added to the network and removed/reinstalled at various times, and that means we're running out of available addresses in our little chunk of the subnet.
    We've previously set a longish lease time on DHCP addresses because we've had problems in the past with sleeping Macs being woken up and having clashing IPs with other Macs that have had that IP reassigned to them, but it means that we do have a long list of unused DHCP clients.
    Does Server 10.5/10.6 allow the release of DHCP addresses from the admin app (oh, for a right-click delete!), or is that just not possible in the DHCP protocol (NB I'm trying to release unused IP addresses, not asking live clients to rescind their IP address).

    It's not legal within the DHCP protocol - as far as the server is concerned, that IP address has been handed to the client and should be reserved for that client until the lease expires. The server has no way of knowing whether the client is still using the address.
    You may be able to break the rules, though - the server stores the DHCP leases in /var/db/dhcpd_leases, so you should be able to stop the DHCP server, edit the file to remove the unnecessary leases, then start the server back up. No guarantees, tho'.

  • Problem with my linksys WRT120N i can't connect to the address 192.168.1.1

    Hello friends
    i need help cuz i can't connect to the address 192.168.1.1
    i didn't change the address 192.168.1.1 to an other address but i can't connect to this last i want to change my options
    i really need help plz 

    Make sure that the computer is connected to the router on the Ethernet port..Now,check the ip address on the computer....Click Start >> All Programs >> Accessories >> Command Prompt...A black box will appear(Command Prompt)...In the Command Prompt window type ipconfig and press 'Enter'...Look for Ethernet Adapter Local Area Connection IP Address , Subnet Mask and Default Gateway...
    IP Address should be 192.168.1.x, Subnet Mask : 255.255.255.0, Default Gateway : 192.168.1.1 (assuming your router is 192.168.1.1)...
    If you get the above mentioned IP Address, Subnet and Gateway Address then you should ping the Gateway, type ping 192.168.1.1 and press Enter...If it gives you request timed out then disable any firewalls, security softwares on the computer...
    If you get 4 replies then,Adjust the Browser Settings on the computer....Open an IE, click Tools >> Internet Options, then delete all files, cookies, history, forms...Goto "Connections", make sure Never Dial a Connection is checked, click on LAN Settings and make sure all the options are unchecked...Once you are done click on O.k...Close the IE and re-open it...

  • I can't connect to my address book?

    I have 3 email accounts and only my icloud email will connect to my address boo but I cant connet the other does any

    Hi LaFemmeco,
    If you access Send via Adobe Reader, you can take advantage of your local address book, so that might make the process a bit easier for you. If you don't have Reader, you can download it from www.adobe.com/products/reader.html.
    Please let us know if you have additional questions.
    Best,
    Sara

  • DHCP Server Address Range

    Hi there,
    I was wondering if there was a way to change the built-in DHCP server address range from 192.168.1.x to, say, 192.168.0.x?  For example, when you change the router IP from 192.168.1.1 to 192.168.0.1.  I noticed that when you commit such a change, the DHCP range does not update accordingly.  Any ideas?
    Thank you,
    Paul
    Solved!
    Go to Solution.

    Your DHCP server range should update automatically to the 192.168.0.x  subnet when you change your "Local IP address" to 192.168.0.1.   Be sure to use a computer that is wired to your router when you do this.  Also, be sure to click on "Save Settings", then wait (3 to 60 seconds) for the screen to refresh.  You will likely be disconnected from the router when you do this.  Do not worry about this.  Power down the router and your computer.
    Next, wait 30 seconds, then reboot router and computer.  Your Local IP address and the DHCP server range should now have the same subnet.

  • Connection to PAT address without pre-existing xlate

    Hello Experts,
    We recently migrated to ASA 9.1.5 from ASA 8.6. Everything worked well except static object NAT. Let me make you understand with an example.
    My inside host 10.12.7.93 is not able to do name resolution from 8.8.8.8. or 8.8.4.4.
    object network 10-12-7-93
     host 10.12.7.93
     nat (INSIDE,OUTSIDE) static 199.96.217.225
    end
    Packet capture command output is shown below.
    packet-tracer input inside udp 10.12.7.93 10056 8.8.8.8 53
    Phase: 1
    Type: ROUTE-LOOKUP
    Subtype: input
    Result: ALLOW
    Config:
    Additional Information:
    in   0.0.0.0         0.0.0.0         OUTSIDE
    Result:
    input-interface: INSIDE
    input-status: up
    input-line-status: up
    output-interface: OUTSIDE
    output-status: up
    output-line-status: up
    Action: drop
    Drop-reason: (nat-no-xlate-to-pat-pool) Connection to PAT address without pre-existing xlate
    What i have observed is that there is a policy pat for destinations 8.8.8.8 and 8.8.4.4 for some inside hosts. Not that 10.12.7.93. What can be the issue? is it some bug in ASA 9.1.5? Your suggestions and comments will be really appreciated.

    Karthik,
    First of all thank you for the kind consideration.
    I will test it without object NAT today and will share the result with you. I am pretty sure it will work that way. The issue is that it was all working well while using 8.6. We have production running and there are 40-50 object NATs running. I cannot afford to add all of them in NAT section 1. Cause this does not make any sense.Since the dynamic PAT is in section 3 and object NAT in section 2. So technically since my traffic matches in section 2 . It should implement that NAT instead of staying in NAT section 3.This is the NAT which is causing conflicts. But this is NAT section 3 and my object NAT for the host is in section 2.
    nat (INSIDE,OUTSIDE) after-auto source dynamic LOWER-SEGMENT x.x.x.x destination static DNS-SERVERS DNS-SERVERS service DNS-TCP DNS-TCP
    nat (INSIDE,OUTSIDE) after-auto source dynamic LOWER-SEGMENT x.x.x.x destination static DNS-SERVERS DNS-SERVERS service DNS-UDP DNS-UDP
    LOWER-SEGMENT: Tthis object group carries the subnet 10.12.7.0/24
    While my section 2 NAT is
    object network 10-12-7-93
     nat (INSIDE,OUTSIDE) static y.y.y.y
    end

Maybe you are looking for