1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Internet connection sharing

Discussion in 'Networking (Hardware & Software)' started by Hennie, 2002/03/17.

Thread Status:
Not open for further replies.
  1. 2002/03/17
    Hennie

    Hennie Guest Thread Starter

    Somebody please help!!!
    I have a small home network.Running Windows 2k professional on 2 machines.Tried hours to get the network going with a crossover cable to no avail.Eventually got myself a hub and couldn't get it going on TCP/IP.Installed NetBEUI and the network is going.

    I cannot now enable ICS on the other machine and whatever I do it doesn't seem to work!If I disable Netbeui the network doesn't work.I have tried the normal steps i.e. IP adresses etc.

    PLEASE HELP!!!

    THANX.
     
  2. 2002/03/18
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Are you using dial-up or broadband for internet access? Reason I ask, the simplest solution by far if you are using cable or DSL is to replace the hub with a router/switch. There may be a way to it work with dial-up as well but I can't say for sure. If you have a router/switch, it will deal with the TCP/IP setups quite nicely and will give you internet access on both PCs without having to mess with ICS.

    Re: your current situation - several things could be giving you problems with trying a TCP/IP setup.

    NIC speed and HUB speed mismatch. The hub probably wants a 10mbs connection. Your documentation should say. Your NICs are probably set to auto for speed. Try locking them into the same speed the hub wants. If it will do 100mbs, then set the cards that way. Otherwise use 10mbs.

    IP addresses and subnet masks - you will need to be using IP addresses and a subnet mask that put both PCs on the same subnet. Otherwise, no IP traffic will work unless you have a router in place.

    ICS requires TCP/IP be enabled. Problem is, your ISP will then assign an IP address to the PC which likely will not match up to any you have on the other PC.
     
    Newt,
    #2

  3. to hide this advert.

  4. 2002/03/18
    Zephyr

    Zephyr Inactive

    Joined:
    2002/01/21
    Messages:
    1,519
    Likes Received:
    0
    That's the way it works for me on Adelphia.net cable but they say in the near future that multiple computers can access through one hookup but I'm sure some more George Wsshingtons will be required.
     
  5. 2002/03/19
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Received by email from Hennie
    Replied to him
    Current to Hennie -

    Lets eat this apple one bite at a time. First priority is to get IP working on your machines so when you try the ICS, you will know that a bad IP setup isn't the problem. Some of this may already be OK but I'll list it anyway.

    Put both machines in the same workgroup. Make sure the workgroup name isn't too long. I sorta like using LOCAL.

    Specify IP addresses for each PC. Try 10.0.0.1 and 10.0.0.2 with a subnet mask of 255.255.255.0

    Make sure Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks are both active.

    From a cmd prompt on each PC

    Ping -t 127.0.0.1 and see if you get a good response. Let it run for around 100-200 cycles. They should all give the same results with no timeouts and no long return times. Thad address is the "loopback" address for the NIC so you are pinging the back side of the local NIC. No cabling involved. If it fails, you either have a bad NIC, a bad slot, or a problem with the TCP/IP setup on the PC. At any rate, it will not ever work unless the problem is identified and fixed.

    If the above is OK, try pinging each machine from the other. If that works, we can move on. If it fails, you are looking at a cable problem or maybe a problem with the hub. Cable most likely. Speed setting between NIC and hub port possibly. Bad port possibly. You would think that if Netbeui works your cables/hub/etc. are OK but occasionally it just ain't so. They can be marginal and Netbeui will work but TCP/IP won't.

    Post back your results.
     
    Newt,
    #4
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.