Problem with Linksys Router Model WRT110 Not Assigning IPs With DHCP?

Hello,
I recently purchased this router (WRT110) to take the place of my old Belkin that was continually dropping connections (which was a real pain when trying to download stuff off the Internet).
However, I cannot get this router to assign IPs to wired or wireless computers. I spent around 2 hours talking to Linksys support technicians (two total) before they finally told me the router was defective.
So, I went back to the store and got an exchange. But, it's the same story with this router, the connections can't get past the "acquiring network address" stage in the connection process.
I would like to think that this has more to do with my ISP than the router, but if I set up a static IP on the wired computer I can connect to the Internet and the router through its default gateway. Setting up a static IP on the wireless computer doesn't seem to work, however. If the ISP was a problem, wouldn't the router not detect the Internet connection at all?
DHCP is definitely enabled on the router also.
My ISP is a small town owned company. I have a wireless broadband connection, which works similarly to satellite, only the connection is broadcast via a tower and is received with an outside antenna. 
I still need to contact them about this, but I figured it could hurt to ask here and see some of your suggestions.
Thank you!
~RJG

UPDATE: I contacted my ISP today and the technician I spoke with said he didn't know of any problems any routers would have with their wireless broadband. I tend to agree with him, as I've configured two routers previously using my connection and I've never had any difficulty until now. He suggested changing the ethernet cable and releasing/renewing my IP address, both of which I did but I continued to have the same issues.
But, after doing some more research I found some settings that actually allowed my wireless computer to connect. There was a post in these forums referring to modifying the MTU, changing it from Auto to Manual and changing the value to 1458 actually seemed to work, as well as strengthening the connection by changing the beacon interval. Anyway, I can connect wirelessly now.
Also, I connected my Linux computer (Ubuntu 8.04 Hardy Heron) to the router and was able to connect instantly, no problems whatsoever. So, out of my three computers, two are connecting, but my wired Windows computer is still having issues. However, if I set a static IP for that computer, I can connect fine.
I'm thinking maybe there is something wrong with the NIC card in that computer, but how would one test something like that?
It doesn't make sense to me, I would really appreciate any input. Thank you!

Similar Messages

  • Hi, I have a wireless linksys router model WRT54G. what i...

    Hi, I have a wireless linksys router model WRT54G. what i want to do it´s configure a network in my home. I have 2 pc´s, a laptop an a desktop. what I should do to be able to share files,music,videos. between both computers? the laptop has Windows Vista, the desktop has Windows XP Professional. could you give me more details? step by step.   thank you really much.

    its really simple to set up a network, first make sure that all computers are in the same workgroup by right clicking on my computer, then properities, then computer name.
    there you can make the setting for the work group
    do not use the default one, create your own, do this for each computer.
    next thing is to choose any folder that you want to share and right click on it, select sharing, then check the two boxes to share this folder and the other one to allow others to make changes to this folder.
    doing this bypasses the trouble od setting up passwords for right now.
    you should not have the network up and running with folders being shared with all in that workgroup.
    you may want to check the manual for vesta as it may do things a bit differant that xp
    you could also run the create a network wizard in the xp system. 

  • DHCP - one server, 2 scopes, 2 NICs, one scope is not assigning IPs

    Hi all,I just setup a DHCP server and one of the 2 scopes is not assigning IPs. Here’s my setup:DHCP running on Windows Server 2008.I have 2 VLANs – VLAN1 192.168.2.0 for our network and VLAN2 192.168.20.0 for guests. I started the DHCP role on the DC. I put one NIC of the server on VLAN1 and one NIC on VLAN2. Bindings on both NICs. I created two scopes – corporate scope 192.168.2.0 and guest scope 192.168.20.0. When I connect a laptop to a port on VLAN1 I get an IP just fine, when I connect it to a port on VLAN2 I don’t get an address. If I assign a static IP on VLAN2 to my laptop I can ping the DHCP server just fine, but as soon as I switch back to dynamic the laptop doesn’t get an IP address. I move the cable over to VLAN1and it works just fine.The router IP and DNS server information are different on each scope, but I’m not even...
    This topic first appeared in the Spiceworks Community

    Hi all,I just setup a DHCP server and one of the 2 scopes is not assigning IPs. Here’s my setup:DHCP running on Windows Server 2008.I have 2 VLANs – VLAN1 192.168.2.0 for our network and VLAN2 192.168.20.0 for guests. I started the DHCP role on the DC. I put one NIC of the server on VLAN1 and one NIC on VLAN2. Bindings on both NICs. I created two scopes – corporate scope 192.168.2.0 and guest scope 192.168.20.0. When I connect a laptop to a port on VLAN1 I get an IP just fine, when I connect it to a port on VLAN2 I don’t get an address. If I assign a static IP on VLAN2 to my laptop I can ping the DHCP server just fine, but as soon as I switch back to dynamic the laptop doesn’t get an IP address. I move the cable over to VLAN1and it works just fine.The router IP and DNS server information are different on each scope, but I’m not even...
    This topic first appeared in the Spiceworks Community

  • Problem with DHCP Router Dir-615

    I have a problem communicating via Wi-Fi between the MacBook and DLinkDir-615 Router.
    The problem occurs when I turn on the MacBook. The Mac can not get IP via DHCP from the router. The only solution is to reboot the router.
    The problem occurs only with the MacBook and sometimes even with the iPhone 4.
    All other devices (Windows PC, PS3, Xbox) have no problem.
    Do you know how to do?

    Most likely it's Lion doing its nonsense. I have the exact same issues right now, after updating to 10.7.3. If you updated too, you should search other threads on how to fix this issue. Personally, setting a static IP did the trick. What is stranger for me, is that even after updating, for a week or so, everything worked fine. I still don't know if it's Mac OS that's doing something, or the router, or both. My strongest guess right now, is that because of a handshake issue with the DHCP server of the router, the router gets messed up and is unable to work properly until a reboot is made. I still don't get it why it worked well for me for a while.

  • Linksys router page does not render properly

    recent firefox upgrades do not allow a normal view of a linksys router page.
    missing text, missing selection items.
    items that do appear are selectable, but it is some subset of a properly rendered page.
    this worked properly before,
    all cache cleared,
    abp and scriping turned off.

    more information, ABP was the culprit, deselection on page
    resolved rendering problem.
    ..never mind... (Emily Lietilla)
    jr

  • GE Simon home alarm system has problem with dhcp

    I have a GE Simon alarm system that instead of using a phone line connection to the monitor station uses tcpip. With my old D Link router it was fine but since changing to the WRT160NL router it seems to lose the IP that is served to it. I reset the system and it picked up 192.168.0.111 and was working ok. but within a day it somehow changes to 192.168.0.49. This happens even if i reserve an IP that is in the range of my dhcp settings. Has anyone ever heard of this issue or is anyone else using this system and it is working for them? My alarm vendor asked me first thing when I called them if I was using a linksys router. He said they always have this problem with linksys.

    Thanks for your reply. That is exactly how i added it to the list. New symptom. previously i had modified the router address to 192.168.0.1 from the factory 192.168.1.1 I did this because my print server was already set to use that subnet and it was easier. When the GE system failed it went from a router assigned address of 192.168.0.106 and changed to 12.168.0.49. it was not accessable at that time. Now that I have changed the router back to the default .1.1 and set the alarm to always be a specified address, when it failed it was not accessable but on the EasyLink screen. That is where i could see that it was set to .49 before. Now it just says that it is offline. So i rebooted the GE Alarm again and it has come back up for almost a day again. One other thing that I noted is that it seemed to fail when it's lease ran out on the IP address. I set the time to 9999 and everything else in my network has gone to a 7 day time for the client release except for the GE alarm. it always comes up with less than half a day. I haven't caught it exactly when it rolls over so i am not sure about how much time but now that i have started to look it is always some short time. Does anyone know how to change the client release to 'never'? most routers have that feature.

  • 2008 r2 hyper-v guest with static IP always looses network connectivity after every restart - no problem with DHCP

    Hello,
    We are running 2008 R2 domain with one physical DC and other running in VM on Hyper-V host (2008 R2 Standard). The host has 4 NICs and is configured to use one physical NIC for itself (management) and the hyper-v guest is configured to use another dedicated/physical
    NIC (through microsoft virtual switch) just for itself.
    I noticed that after setting the hyper-v guest with a static IP address all works fine only until guest restart. When the guest boots up the IP address is still configured correctly in IPv4 properties, but there is no network connectivity at all and in fact
    the guest shows running APIPA config in ipconfig /all output. That situation continues until I remove the virtual NIC from hyper-v guest, remove the virtual switch from dedicated NIC on host and then reconfigure it (using same settings as they were). very
    annoying.
    For time being I switched the virtual DC (problematic hyper-v guest) to a DHCP IP and configured DHCP server (running on physical DC machine, not on hyper-v host) to store a reservation for the hyper-v guest so it always gets the same "static"
    IP configuration.
    Is there some kind of a problem/bug with using static IP on (2008 R2) hyper-v guests? is there a hotfix for static IP config in hyper-v guest environment?
    both 2008 R2 OSes (host and guest) are up to date with all updates (synced with Microsoft, not WSUS).

    OK, I'm not at the office now, but took my time to test out the restart scenarios on problematic virtual guest remotely.
    No dice, same as it was, everything works fine after guest has IP configured in DHCP mode (IP reservation of 192.168.1.5 for specific MAC address) and it doesn't work after restart in static IP mode (same address, works before restart of guest).
    I also took "arp -a" outputs at each step from host server and that was always saying there is only a single host (192.168.1.5 = VDC = problematic virtual guest) assigned to that IP address and always with same MAC, so that pretty much rules out
    ARP/MAC troubles and no issues with switches/routers getting spoofed. Problem is most likely with the virtual guest (WS2008R2) or within the host running same OS.
    Here are outputs:
    A) VDC has IP configured in DHCP mode - always same, survives through restart (all works)
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . : CD.lan
    Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter
    Physical Address. . . . . . . . . : 00-15-5D-01-D3-00
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::b9af:6679:3142:8799%13(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Thursday, January 30, 2014 5:34:48 PM
    Lease Expires . . . . . . . . . . : Friday, February 07, 2014 5:35:26 PM
    Default Gateway . . . . . . . . . : 192.168.1.254
    DHCP Server . . . . . . . . . . . : 192.168.4.5
    DHCPv6 IAID . . . . . . . . . . . : 268440925
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-6F-5F-C2-00-15-5D-01-D3-00
    DNS Servers . . . . . . . . . . . : 192.168.1.5
    192.168.4.5
    NetBIOS over Tcpip. . . . . . . . : Enabled
    ARP -a output from host server at that time:
    Interface: 192.168.1.4 --- 0xc
    Internet Address Physical Address Type
    192.168.1.5 00-15-5d-01-d3-00 dynamic
    B) VDC has IP configured in static mode - BEFORE RESTART (all works)
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter
    Physical Address. . . . . . . . . : 00-15-5D-01-D3-00
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::b9af:6679:3142:8799%13(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.254
    DHCPv6 IAID . . . . . . . . . . . : 268440925
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-6F-5F-C2-00-15-5D-01-D3-00
    DNS Servers . . . . . . . . . . . : 192.168.1.5
    192.168.4.5
    NetBIOS over Tcpip. . . . . . . . : Enabled
    ARP -a output from host server at that time:
    Interface: 192.168.1.4 --- 0xc
    Internet Address Physical Address Type
    192.168.1.5 00-15-5d-01-d3-00 dynamic
    C) VDC has the same IP configured in static mode - AFTER RESTART (no more network connectivity at all, LAN in Public zone)
    Windows IP Configuration
    Host Name . . . . . . . . . . . . : VDC
    Primary Dns Suffix . . . . . . . : CD.lan
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : CD.lan
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter
    Physical Address. . . . . . . . . : 00-15-5D-01-D3-00
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::b9af:6679:3142:8799%13(Preferred)
    Autoconfiguration IPv4 Address. . : 169.254.135.153(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.0.0
    Default Gateway . . . . . . . . . : 192.168.1.254
    DHCPv6 IAID . . . . . . . . . . . : 268440925
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-6F-5F-C2-00-15-5D-01-D3-00
    DNS Servers . . . . . . . . . . . : 192.168.1.5
    192.168.4.5
    NetBIOS over Tcpip. . . . . . . . : Enabled
    ARP -a output from host server at that time:
    Interface: 192.168.1.4 --- 0xc
    Internet Address Physical Address Type
    192.168.1.5 00-15-5d-01-d3-00 dynamic
    Throughout the testing, the hyper-v host IP configuration and IPconfig output was always staying same.
    The Network Connection #2 is the only one the host uses (not shared with hyper-v guests).
    The Network Connection #4 is assigned to Microsoft Virtual Switch hence why it doesn't show up in results, like below:
    Windows IP Configuration
    Host Name . . . . . . . . . . . . : HYPER-V
    Primary Dns Suffix . . . . . . . : CD.lan
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : CD.lan
    Ethernet adapter Local Area Connection 3:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331i Adapter #3
    Physical Address. . . . . . . . . : 9C-8E-99-52-15-91
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Ethernet adapter Local Area Connection 2:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331i Adapter #2
    Physical Address. . . . . . . . . : 9C-8E-99-52-15-90
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::dc78:8a3b:38a5:7af3%12(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.254
    DHCPv6 IAID . . . . . . . . . . . : 312250009
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-67-52-8F-9C-8E-99-52-15-93
    DNS Servers . . . . . . . . . . . : 192.168.4.5
    192.168.1.5
    NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Local Area Connection:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331i Adapter
    Physical Address. . . . . . . . . : 9C-8E-99-52-15-93
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    On Monday I will install more test guests in Hyper-V host (WS2008R2), in variety of flavors like 7x64, 8.1x64, ws2012r2, and see if they show similar problems with static IP configuration when utilizing a dedicated NIC from host server.
    Don't get me wrong, I can live with virtual DC running on DHCP IP reservation (which is based on MAC), because the virtual DC pretty much requires a physical PDC (hosting also DHCP in my network) to be present for safety reasons ... however I prefer a static
    IP configuration on all servers, hence my question and surprise why it doesn't work.

  • Time Capsule/AirPort Express problem with DHCP server

    Hi everyone,
    I seem to be having some weird issue with my home network.  I use a Time Capsule (2011) as my main router and a new AirPort Express as a wireless bridge (router set to "Extend a wireless network", the LAN port is connected to network printer).  Recently, it seems that at least once or twice a week that the DHCP server on my router stops working.  Computers that have static IP addresses have no problem accessing the internet or my local network, but  devices that don't have static IPs  are unable to join the network (over Wi-Fi or ethernet) because they are not being assigned an IP.  This never happened before.  I'm not sure if it has anything to do with the recent firmware update.  Anybody else seem to be having this problem?  I am able to get the DHCP server working again by restarting the Time Capsule or by setting the computer or device that won't connect to a static IP.  Really curious why this seems to be happening…
    Thanks for all the help guys

    I am having the same problem with the same setup: a 2011 Time Capsule and an Airport Express. I've had my Aiport Express hooked in for about 2 years, so I know it is not the problem. The only difference I have is the DHCP will stop working on the ethernet, but still work over WiFi from the TC. Rebooting the Time Capsule fixes the DHCP issue.
    I am running version 7.6.4 in the Time Capsule.

  • Problem with DHCP! Please help!

    I have WRT54GL ver 1.1 and last firmware 4.30.12
    My router can't get IP via DHCP from ISP. When I plug my PC it gets IP without problems but process of receiving IP is rather long. I checked traffic and found that Router tries to send 3 packets of DHCP-Discover with the same transaction ID every 2 sec, and then router changes transaction ID !!! DHCP server has big delay and answer on these packets in 20-30 sec but router has already changed transaction ID !
      PC do not changes transaction ID and keeping sending Discover packets, later PC successfully receives IP.
    What can you advise? How can I receive IP?
    P.S. I can't use static IP.

    Well i feel in this case you can reset your router and re-confugure all the settings on your router back again, i hope this might solve your problem.

  • Problem with DHCP

    Hi there...
    I guess the problem has been solved many times, but i don't find any thread that deals with it.
    I use the AEB to connect wireless devices (such as MacBooks) to our ethernet network. So I have connected the AEB to the existing ethernet through one of the ethernet ports. All devices (even the AEB) in the network got static IP adresses. I use the 192.168.0.x range. I configured the AEB with a static IP adress and the gateways and the DNS server.
    Then i configured it to distribute IP adresses via wireless. I used a designated range of 10 adresses within my pool I use for the static IP adresses which are reseverd for this purpose.
    Now the problem: Very often the MacBooks or Wintel Notebooks, that try to connect to the AEB get an adress in this range: 10.x.x.x
    Even the gateway provided shows an adress within this range.
    Devices with this adress have of course serious trouble connecting to other Macs in the network and have a functional but very, very slow internet connection.
    How can I solve this? (tried all i know. Have this problem for very long, even with my old AEB)
    Hinne

    Hi,
    It sounds like one possible reason for the network problems you are having is because you have set up 2 devices (routers) on the network to generate IPs via DHCP.
    When setting up the AEB, you don't want it to assign IPs, you want it to act as a wireless bridge and merely 'extend' the range of the network to a group of wireless clients. If you have 2 devices generating DHCP then there will be conflicts, especially if both are in the 10.x.x.x range.
    The desired situation is where your wired DHCP server, probably a modem/router or something, is the device that generates IPs and the AEB passes those IPs to wireless clients.
    To do this, remove the static ip assigned to the AEB (optional, I think), connect to the AEB using airport admin utility, go to network and uncheck 'distribute IPs'. That should do it.
    If that doesn't work, post back!!
    JS

  • Problems with DHCP and virtual PC connected to an AP in autonomous mode

    I've a virtual machine (Windows 7) on my MacBook running on VMWare Fusion 6 running in bridge mode and can't get an IP address from my DHCP server. NAT mode in VMWare is working, but not an option.
    I've tracked down the problem with Wireshark to the DHCP Offer that is dropped by the Cisco AP:
    On the LAN side I've captured the packets and could see that the DHCP-DISCOVER from the Windows client was answered by the DHCP server with a DHCP-OFFER (all these packets are broadcasts in the same layer 2 network), but the OFFER was not forwarded by the 1142 AP running in autonomous mode, version 15.2(4)JA.
    The problem looks to be similar to a previous discussion with WLCs where a solution is available meanwhile, see:
    https://supportforums.cisco.com/discussion/11350776/dhcp-issue-inside-vm-connected-wireless-network
    http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_01110010.html#ID2828
    Is there any solution for APs running in autonomous mode?
    Jan

    It's already a while ago, but recently I got a new router at home and have upgraded the AP to 15.3(3)JAB as well. I'm not sure what the exact reason was, but the problem reappeared. I'm a Mac user and need the bridging mode at home for my home automation system that only comes with some windows tools. Therefore I spend some time to figure out more details and was able to solve the problem.
    It turned out, that the AP needs to get an IP address by DHCP, otherwise the Windows machine never gets an IP address. I was able to see the DHCP discover broadcast from my virtual Windows PC as well as the DHCP offer from my home router. Even the packets from the DHCP relay agent (the AP with ip-helper) and the reply packet from the home router were shown with a DHCP debug on the AP and also with Wireshark on the LAN, but these broadcasts were not forwarded to wireless client. I've used Wireshark to capture packets on the WLAN adapter of my Macbook to verify that these packets were dropped on the AP and not on the Macbook with VMware Fusion. For some unknown reason the AP (acting as a bridge!) does not forward these broadcasts to the wireless client. 
    After playing around it turned out, that it WORKS if the AP itself is configured as a DHCP client and does not have a static address AND there is a DHCP entry for my virtual Windows PC like this:
    ip dhcp pool Macbook
     host 192.168.128.44 255.255.255.0
     client-identifier 0100.5056.1234.56
     dns-server 192.168.128.1
     default-router 192.168.128.1
     domain-name home.local
    It's a bit weird that the AP itself needs to be a DHCP client and I can't explain why, but this setup works for me. I like to keep the DHCP server on my home router, so I've only added this DHCP reservation on the AP. 

  • Mac osX question regarding persistent LAN problem using Linksys router

     We are eight months into this problem.
    I had this up on the apple help board 6 months ago but could only get a band aid fix for the problem.
    (The "band aid" is explained on the link below.) 
    We have since exhausted 3 other professional help folks.
    We are using the WRT54GS ver. 5.
    Before we were using BEFSx41 ver. 2 and we had same problem.
    The full description of the problem can be found on this page...
    http://discussions.apple.com/thread.jspa?messageID=9062933#9062933 
    ANY well thought out suggestions deeply appreciated.
    Thanks. 

    Sorry dude, definitely sounds like a mac problem (i.e. editing the cnf files on mac s). Unless you are blocking a special service, which you probably aren't, then its definitely not the router. The reason I say that is all traffic gets transferred at layer 2 of the OSI model, in this case. IP addressing is layer 3 (router/network layer). Short answer is all traffic gets "switched" via mac address, not ip in this case. Your router here is more like a switch that provides dhcp and a default gateway to get to the internet. Any unknown mac (media access control, not mac/apple) traffic will get "routed" to the wan.
    Message Edited by bubbateeth on 02-27-2009 01:46 AM

  • Problem with DHCP self-assigned IP number

    Hi
    I have just purchased a 24" iMac running 10.5.3 it is on my home network with a pb12 (10.3.9), a mini (10.4.11) and a lacie nas drive all connected via a router to my broadband modem. The IP set up I'm using is 192.168.x.x on 255.255.255.0. The modem is set up as a DHCP server to give out addresses starting with 192.168.1.3 and so forth. All my original machines work fine with this system, but the iMac when it turns on it self assigns itself 169.254.x.x on 255.255.0.0 and thus won't play with the other computers of the internet. Even if I set the settings to manual and type in 192.168.1.8 on 255.255.255.0 with the router at 193.168.1.1 it still won't connect to the network.
    Does anyone have any thoughts on this problem?
    thanks for any help in advance.

    I have just noticed that when the imac is restarted it self assigns itself 169.254.x.x on 255.255.0.0 if I then talk out the network cable and click "renew DHCP Lease" a couple of times until the fields are blank, then plug back the cable and click "renew DHCP Lease" I then do get a 192.168.x.x on 255.255.255.0 setting?
    This works around the problem but doesn't solve it.
    Just did a second restart and this time is correctly assigned a 192.168.x.x IP address.
    On the third restart it is back to a 169.254.x.x IP number!!!
    Message was edited by: think.different

  • Problem with DHCP not flushing unused leases

    We have a small network of approximately 40 devices that get IP addresses via DHCP. We have had at least one encounter where we used up all available 254 addresses in the DHCP pool. Come to find out, unused leases are not flushed.
    Is there a utility or CRON job that should be running and perhaps has stopped, that will periodically flush unused leases? We had the lease time set for a couple days, and today changed it to 2 hrs, but it still isn't flushing.
    Thanks

    Hi RiBridges,
    it might be to soon to check wether "flushing" occurs or not. As the man page of bootp states regarding DHCP:
    "The server removes an expired lease entry only when it runs out of addresses, and needs to reclaim an address in order to fulfill a new request."
    -Petra

  • I have the linksys router model wrt54g and FaceTime won't sign in, it tells me to check my Internet connection... Please help

    I have enabled all of the ports needed and it still tells me to Check my Internet connection

    Sorry thats any*

Maybe you are looking for