Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Internet suddenly stopped working on LAN cables

Options
  • 23-09-2007 12:16am
    #1
    thechamp87
    Registered Users Posts: 970 ✭✭✭


    Any ideas guys??
    Suddenly stopped working on cable. only works on wireless.

    I dont really know much about the finer details but i went interent settings and it says invalid IP. IP address reads something like 0.00.00.00 or something like that?

    Thanks...


Comments

  • Options
    #2
    ethernet
    Registered Users Posts: 3,568 ✭✭✭ethernet


    Don't try using connecting by cable and wirelessly at the same time. So wireless works. What settings is that connection using? Has is a static IP address or receiving one by DHCP? Compare that to the settings for your ethernet connection.

    Open up the Command Prompt and type: ipconfig /all
    This will make it easier to compare these settings. Tell us what's there.


  • Options
    #3
    _CreeD_
    Registered Users Posts: 4,148 ✭✭✭_CreeD_


    Normally if your PC cannot find any DHCP servers at all it assigns itself an address beginning with 169.254.x.x, 0.0.0.0 points to a problem a bit higher up. Either on your PC or the Router/DHCP server services and configuration.

    Check the connection LEDs on the Wired NIC and the Router's switchports, there should be 2: one always on to show a physical connection, and another intermittently flashing to show activity.

    No Lights, or just the connection light but no activity?
    Try a different port on the Router if possible, ditto with the cable.

    Solid connection light, intermittent activity?
    If the DHCP service has failed your Wired NIC lease may have timed out first. From the IPCONFIG results above look for some key details on your Wireless NIC, namely IP Address and Default Gateway. They will most likely both be 192.168.1.?, regardless go to Network Connections under the Control panel, choose your Wired NIC and right-click/properties, select TCP/IP properties and switch to using a manually entered address. Just fill in the first 3 sections, where IP Address = Wireless IP address +1 (so if it was 192.168.1.2, use 192.168.1.3), subnet mask will default to 255.255.255.0 leave it that way, set the Default Gateway to the same as the Wireless gateway. Okay your way out of there and go to a command prompt, type PING (default gateway address), so if the DG was 192.168.1.1 you would type "PING 192.168.1.1", mainly what you're looking for here is that it says either Timed-Out or "Reply received" the other details aren't important for this test. If you get a reply then do the following steps, if you don't it's a bit more serious....
    Reverse the steps on Network Connections / Properties/TCP etc. above, set both fields under TPC/IP to automatic. Reset your router, when it has rebooted from a command prompt run IPCONFIG / RELEASE followed by IPCONFIG / RENEW, check your IPs as suggested above again. Your Wired NIC should have a 192.168.1.? address and you should be able to run that PING command if everything worked to plan.


Advertisement