1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Cannot connect to adsl modem/router

Discussion in 'Tech Support' started by Henchman:crg, 24 Dec 2006.

  1. Henchman:crg

    Henchman:crg What's a Dremel?

    Joined:
    9 Feb 2005
    Posts:
    749
    Likes Received:
    0
    This is a pretty serious problem with my dads computer.

    Basically the router cannot see the computer, and when doing ipconfig it reports Autoconfiguration IP Address of 169.254.8.77

    Cannot ping the router on 192.168.0.1 have connected the router to my own computer using same cables, all works perfectly.

    also tried renewing, been on the phone to aol for an hour, no luck so far.

    Only other thing I have found out is it seems to be related to APIPA.

    Can anyone help?
     
  2. Glider

    Glider /dev/null

    Joined:
    2 Aug 2005
    Posts:
    4,173
    Likes Received:
    21
    If it works perfectly on your computer, I think you should check your dad's config... Maybe some nasty piece of software installed itself...
     
  3. AJB2K3

    AJB2K3 What's a Dremel?

    Joined:
    12 Dec 2005
    Posts:
    1,605
    Likes Received:
    4
    thought the ip was 192.168.0.2?
    Is the subnet on your dads set to 192.168.0.1? as well as ip set to 169.254.8.77 (or what ever it may end up.
    I had an issue that matched this when i forgot to set the subnet mask.
     
  4. Henchman:crg

    Henchman:crg What's a Dremel?

    Joined:
    9 Feb 2005
    Posts:
    749
    Likes Received:
    0
    Have also run several virus and spyware tools, the computer is now clean.

    The router cannot see the computer either, its a netgear 4 port modem/router, the light for the port its plugged into flashes very fast always I have a solid green light with my computer connection.

    Not sure if its hardware?
     
  5. Henchman:crg

    Henchman:crg What's a Dremel?

    Joined:
    9 Feb 2005
    Posts:
    749
    Likes Received:
    0
    Something to do with APIPA (a way of trying to talk on a network when it thinks there is no DHCP server)

    so IP address of 169.254.x.x is typical with this configuration, but I cant get rid of it and work normally?
     
  6. AJB2K3

    AJB2K3 What's a Dremel?

    Joined:
    12 Dec 2005
    Posts:
    1,605
    Likes Received:
    4
    Have you checked the subnet mask on BOTH computers
    Linksys use 192.168.0.2 for the router then assign ips to following net devices however for a pc to go through the router it needs to have the subnet set to match the ip of the router.
    BTW is the winbloze fire wall blocking it?
    Shut down the firewals one at a time followed by the av software then anything else using the network.
    *edit* seams mine has changed to a different base ip.
    *edit 2* I forgot that mine now auto set this all up now. £25 phone bill to both linksys and bt fixed this :wallbash: :wallbash: :wallbash:
     
  7. Henchman:crg

    Henchman:crg What's a Dremel?

    Joined:
    9 Feb 2005
    Posts:
    749
    Likes Received:
    0
    uninstalled firewalls, turned off windows firewall, disabled all anti-virus, still have same problem.

    Running out of ideas here, unless someone can give me some more, I've tried all the obvious things, just got to find the root of the problem some how
     
  8. DougEdey

    DougEdey I pwn all your storage

    Joined:
    5 Jul 2005
    Posts:
    13,933
    Likes Received:
    33
    Have you tried to manually set the IP, subnet etc...
     
  9. Henchman:crg

    Henchman:crg What's a Dremel?

    Joined:
    9 Feb 2005
    Posts:
    749
    Likes Received:
    0
    Even set IP manually, cant ping the modem/router at all.
    Think if someone doesnt have the answer its going to be a re-install of the os.
     
  10. DougEdey

    DougEdey I pwn all your storage

    Joined:
    5 Jul 2005
    Posts:
    13,933
    Likes Received:
    33
    Is it onboard NIC or seperate card? And who's the manufacturer?
     
  11. airchie

    airchie What's a Dremel?

    Joined:
    22 Mar 2005
    Posts:
    2,136
    Likes Received:
    2
    Have you checked the cable?
    Is the NIC enabled in device manager?
    Is the NIC set to recieve an IP automatically?

    I think you mean the default gateway need to be set to the IP of the router, not the subnet mask.
    Generally, the subnet masks on the router and all the PCs connecting through it are 255.255.255.0.
    If the PC is using APIPA (Automatic Private IP Addressing btw) it means it doesn't see a DHCP server on the network.
    So either the router is not set to assign IP addresses to clients or the cable is dodgy.

    As a test, you could check all the settings on the PC that works (type ipconfig /all in command prompt) and manually assign those setting to the PC that doesn't work (don't forget to unplug the working PC before you apply the settings on the other or you'll get a conflict).

    If it works then increment the IP address and all should be good (ie, if IP is 192.168.0.2 then change it to 192.168.0.3).

    Good luck. :)

    <EDIT>
    Re-reading this.
    I think it might be useful to suggest some settings for you.

    Router is likely to be:-
    IP - 192.168.0.1
    Mask - 255.255.255.0

    PC 1
    IP - 192.168.0.2
    Mask - 255.255.255.0
    Gateway - 192.168.0.1
    DNS - Unknown but you can take it from the working PC

    PC2
    IP - 192.168.0.3
    Mask - 255.255.255.0
    Gateway - 192.168.0.1
    DNS - Set same as PC1
     
    Last edited: 24 Dec 2006
  12. severedhead

    severedhead What's a Dremel?

    Joined:
    19 Dec 2002
    Posts:
    1,479
    Likes Received:
    1
    You could try reinstalling TCP/IP.

    If you damage the registry its not my fault!

    1. Click Start, and then click Run.
    2. In the Open box, type regedit, and then click OK.
    3. In Registry Editor, locate the following keys, right-click each key, and then click Delete:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
    4. When you are prompted to confirm the deletion, click Yes.
    Note Restart the computer after you delete the Winsock keys. Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer after you delete the Winsock keys, the next step does not work correctly.

    1. Right-click the network connection, and then click Properties.
    2. Click Install.
    3. Click Protocol, and then click Add.
    4. Click Have Disk.
    5. Type C:\Windows\inf, and then click OK.
    6. On the list of available protocols, click Internet Protocol (TCP/IP), and then click OK.

    If Internet Protocol (TCP/IP) does not appear, follow these steps:
    a. Click Start, and then click Search.
    b. In the Search Companion pane, click More advanced options.
    c. Click to select the following three check boxes:
    • Search system folders
    • Search hidden files and folders
    • Search subfolders

    d. In the All or part of the file name box, type nettcpip.inf, and then click Search.
    e. In the results pane, right-click Nettcpip.inf, and then click Install.

    7. Restart the computer.
     

Share This Page