Hostname Requirements

Joanne Callahan (jc46@cornell.edu)
Thu, 5 Jan 1995 09:41:19 -0500


>Date: Fri, 2 Dec 1994 15:46:09 -0500
>Reply-To: kennerly@nr-tech.cit.cornell.edu
>Sender: owner-CU-SEEME-L@cornell.edu
>X-PH: V4.1@listproc.mail.cornell.edu (Cornell Modified)
>From: Richard Kennerly <kennerly@nr-tech.cit.cornell.edu>
>To: <CU-SEEME-L@cornell.edu>
>Subject: Hostname Requirement for CU-SeeMe Windows
>X-To: cu-seeme-l@cornell.edu
>X-PH: V4.1@cornell.edu (Cornell Modified)
>X-Listprocessor-Version: 7.1 -- ListProcessor by CREN
>
>Windows users:
> Here's a repeat of some more info about hostname requirements.
>--------
>Hostname Requirement for Windows CU-SeeMe
>
> Your Windows machine will need a hostname. CU-SeeMe for Windows
>will not work without it (this requirement may disappear soon).
>The way to provide a hostname is to make an entry into the hosts file.
>The format for the hosts file is:
>
>
><your IP address> <name for your PC>
>
> For example, you might decide to use the hostname WillieBob. If
>your IP address was 128.32.64.88, the entry in your hosts file would
>look like:
>
>128.32.64.88 WillieBob
>
> Your HOSTS file should be in your Windows Sockets directory (the
>same directory that contains your 'winsock.dll'). This directory must
>be in the PATH before windows is started.
>
> If you don't already have a hostname for your PC, you may want to
>contact your network administrator about getting one assigned. If your
>host name is defined in a Domain Name Server (DNS) accessible to your
>PC, you won't need to have a HOSTS file. Keep in mind, in this case,
>that if you can't reach your DNS, you'll get the "GetHostByName() Error"
>message.
>
> While this issue has been a problem for many it has worked on all
>stacks after some work (The FTP software hitch mentioned below took
>many phone calls to a very patient user at NSF before solving).
>
>Things to verify:
>
>*) Verify that you've only got one HOSTS file (there might be a bad one
> earlier in your path). Use FILE MANAGER, File Menu, Search - Search
> for hosts, start from c:\, check the 'Search All Subdirectories box.
> If you find entries other than the one you expect to find in your
> Winsock directory, consider removing or updating them.
>
>Possible stumbling blocks:
>
>*) You're using FTP PCTCP and you've something set in the "Domain
> Completion" box. This can cause your software to not find its real
> hostname in the hosts file.
>
>*) When Defining your hostname with your Winsock Customization software,
> do not include the domain name in the hostname specification. For
> example, if WillieBob is in the domain cit.cornell.edu, do NOT specify
> WillieBob.cit.cornell.edu as the hostname. Just enter WillieBob and
> enter the domain in its place.
>
>Rich Kennerly
>
>