{"id":1095,"date":"2021-09-23T14:55:19","date_gmt":"2021-09-23T14:55:19","guid":{"rendered":"https:\/\/www.practicallynetworked.com\/?page_id=1095"},"modified":"2022-04-27T15:06:45","modified_gmt":"2022-04-27T15:06:45","slug":"using-dhcp","status":"publish","type":"post","link":"https:\/\/www.practicallynetworked.com\/using-dhcp\/","title":{"rendered":"Using DHCP"},"content":{"rendered":"

Many connection sharing programs have a\u00a0DHCP<\/a>\u00a0server that you can use to automatically assign TCP\/IP information to your Client computers. \u00a0 The sharing software that comes with many of the new phone-line and wireless Home networking kits includes this capability.<\/p>\n

Why, then, do I recommend manually assigning TCP\/IP information?\u00a0 Here’s the list of reasons:<\/p>\n

    \n
  1. \n

    Not all sharing programs (the “free” Wingate 2.1x version in particular) include a DHCP server.
    \nSo you’ll have to know how to do it anyway.<\/p>\n<\/li>\n

  2. \n

    Using one NIC and running a DHCP server is a sure-fire way to get the attention of your cable ISP and possibly get “de-provisioned”.
    \nIn spite of all my warnings about using two NICs, some people insist on trying to share their connection using only one NIC.\u00a0 When your DHCP server starts trying to hand out addresses to other users’ computers on your local network node, expect to be “noticed” by your ISP!<\/p>\n<\/li>\n

  3. \n

    Trying to minimize the chances of incorrectly configuring TCP\/IP on the Sharing Server and Client computers.
    \nI figure that if you set things manually, you’ll know how they’re set, rather than letting something automatically set it for you.<\/p>\n<\/li>\n<\/ol>\n

    In fact, a properly configured sharing setup with a DHCP server can operate very smoothly and be especially helpful if you have laptops that you move back and forth between your shared network and your office or other remote location. Here is a list of conditions under which it’s ok to use a DHCP server:<\/p>\n

      \n
    1. \n

      You are using\u00a0TWO NICS\u00a0on your Sharing computer (but you knew that anyway, didn’t you?)
      \nAND
      \nthe DHCP server comes as part of your sharing software.<\/p>\n

      OR<\/p>\n<\/li>\n

    2. \n

      You are using a hardware router that contains a DHCP server.<\/p>\n<\/li>\n<\/ol>\n

      In the above cases, go ahead and set your\u00a0client\u00a0computer TCP\/IP as follows:<\/p>\n

        \n
      • For Windows:\n
          \n
        • \n

          IP address:\u00a0“Obtain an IP address automatically”<\/p>\n<\/li>\n

        • \n

          Subnet Mask: N\/A<\/p>\n<\/li>\n

        • \n

          WINS Configuration:\u00a0Disable WINS resolution<\/p>\n<\/li>\n

        • \n

          Gateway:\u00a0Make sure there are\u00a0NO entries.<\/p>\n<\/li>\n

        • \n

          DNS Configuration:
          \nNOTE! DNS settings apply to all NICs in a given computer, so you can’t set them differently for the LAN NIC.<\/big>
          \nThis is the most difficult setting and depends on how your Sharing software or router works.
          \nRead and follow the instructions that come with your Sharing software or hardware router.<\/p>\n<\/li>\n

        • \n

          Bindings:\u00a0Check\u00a0Client for Microsoft Networks\u00a0and\u00a0File and Printer Sharing for Microsoft Networks\u00a0if you don’t have any other protocol (NetBeui, IPX\/SPX) installed and bound to these items. Otherwise uncheck them.<\/p>\n<\/li>\n

        • \n

          Advanced:\u00a0no changes<\/p>\n<\/li>\n

        • NetBios:\u00a0no changes.<\/li>\n<\/ul>\n<\/li>\n
        • For MacOS\n
            \n
          • \n

            Set the “Configure” setting to “Using DHCP Server”<\/p>\n<\/li>\n

          • \n

            Make sure there are no entries in the other fields.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n

            Happy DHCPing!<\/p>\n","protected":false},"excerpt":{"rendered":"

            Many connection sharing programs have a\u00a0DHCP\u00a0server that you can use to automatically assign TCP\/IP information to your Client computers. \u00a0 The sharing software that comes with many of the new phone-line and wireless Home networking kits includes this capability. Why, then, do I recommend manually assigning TCP\/IP information?\u00a0 Here’s the list of reasons: Not all sharing programs (the “free” Wingate 2.1x version in particular) include a DHCP server. So you’ll have to know how to do it anyway. Using one NIC and running a DHCP server is a sure-fire way to get the attention of your cable ISP and possibly <\/p>\n","protected":false},"author":2,"featured_media":5596,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"_links":{"self":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts\/1095"}],"collection":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/comments?post=1095"}],"version-history":[{"count":1,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts\/1095\/revisions"}],"predecessor-version":[{"id":5603,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts\/1095\/revisions\/5603"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/media\/5596"}],"wp:attachment":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/media?parent=1095"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/categories?post=1095"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/tags?post=1095"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}