HELP! Network connection completly dead!

TheSmJTheSmJ
edited September 2003 in Hardware
On the machine in my sig, I was setting the computer's local IP in the TCP/IP's settings. After I set the settings, just as I have on my other machines, to an IP of 192.168.0.20 (which is not used anywhere else on the LAN) the computer refused to go online.

Thinking this as odd, I set both the DNS and IP settings to automatic (the way they were before) and the computer STILL refuses to connect, only this time the machine cannot see the LAN either!

I've been through the other computer's settings (which are all working fine) and set ALL settings IDENTICAL to the working machines. Still no go. No internet, no LAN.

I checked all the cables, they're fine. Both the LAN adapter (I’m using the nForce 2's onboard LAN) and the router light up with the connection. I disabled/re-enabled the onboard LAN adapter in the BIOS, Windows still wont work.

Aside from doing yet another repair install, I cannot think of anything I have not tried, but I know there is something I missed. This just doesn’t make sense.

Comments

  • leishi85leishi85 Grand Rapids, MI Icrontian
    edited September 2003
    try unplug the router's power for aboutr 1 min, and use automatical setting, see if it works.
  • EMTEMT Seattle, WA Icrontian
    edited September 2003
    Have you disabled DHCP on the router? That's the only good reason it would not work properly when all is set to detect automatically.

    What exactly do you mean, refused to go online? What could/couldn't you do? e.g... ping IP addresses, lookup DNS names...
  • TheSmJTheSmJ
    edited September 2003
    EMT said
    Have you disabled DHCP on the router? That's the only good reason it would not work properly when all is set to detect automatically.

    What exactly do you mean, refused to go online? What could/couldn't you do? e.g... ping IP addresses, lookup DNS names...


    :doh:

    Yeah, the DHCP server was disabled... must have done that after I reset the router while trying to find out why setting the local IP wasn't working.

    Wierd that I couldnt even connect to the router on the effected machine. If I was without another couple machines to connect to it with, I dunno what I'd do....


    Thanks for jogging my memory EMT! I knew it was something stupid I was missing. :respect:

    Now to get the local IP set the way I want it. There's no reason why that wont work either...
  • EMTEMT Seattle, WA Icrontian
    edited September 2003
    Hmm that's good :)

    So what happens if you copy down the settings DHCP gives to it (I'm assuming it works that way now, right?) and then set those same settings manually?
  • TheSmJTheSmJ
    edited September 2003
    actually, the reason for the IP settings not taking was because I used the actual ISP's gateway, rather than the "bridge", or gateway actually connecting the LAN to the internet.

    So, I fixed that as soon as I realized what was wrong. Everything's 100% now.
  • EMTEMT Seattle, WA Icrontian
    edited September 2003
    Alright, cool then :)
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited September 2003
    Excellent. There is one other way that CAN happen, though. That is to assign an OUT-OF-SUBNET IP to a client and have the router it is hooked to secured to feed only to a defined subnet to reduce chances of a LAN segment hack, or to make a workgroup a segment to make that workgroup have less segment traffic collisions internal to the workgroup.

    But, you learned two things:

    First, your ISP router is programmed at least partly right-- it is rejecting private (LAN, reserved for) addresses or your LAN router is in fact blocking the LAN from getting to the ISP (both actually good for the LAN in a security sense). Second, your LAN router is feeding DHCP right.

    John.

    John.
Sign In or Register to comment.