Samba related question.

[p.lussier at comcast.net]

In a message dated: 11 Feb 2004 13:08:26 EST
"Kenneth E. Lussier" said:

>DHCP doesn't assign hostnames, it assigns IP addresses (and other
>various info).

Well, that's not exactly true, among the 'other various info' you 
mention, DHCP can and is used to assign:

  - hostnames
  - IP addresses
  - DNS servers
  - NIS servers
  - WINS servers
  - Bootp servers
  - and 'other various info' :)

>DNS is used to resolve those IP addresses to names. You
>can have a box that has foo for a hostname, 192.168.1.2 for an IP
>address, and an entry in DNS that resolves 192.168.1.2 to the name
>bar.domain.com. You can ping 192.168.1.2 or bar.domain.com, but the name
>foo will show up in network neighborhood and it cannot be ping'd by foo
(if there is a WINS server in the picture, you can make this even more
>convoluted).

Actually, the name 'foo' might NOT show up in NetworkNeighborhood.  
Ping usually uses a gethostbyname() call to resolve hostnames to IP 
addresses and gethostbyname() usually will try all available 
resolution mechanisms, WINS, DNS, etc.  So ping will succeed if DNS 
is properly configured to refer to a DNS server which will resolve 
the IP for foo properly.

NN, on the other hand usually only uses WINS for resolution, which is 
why, when you open up NN, you only see a 'Microsoft Network' icon, 
which, when clicked, either shows you nothing, or only other Windows 
systems.  However, if you install UNIX Services for Windows, you will 
also see NFS servers.  (Remember, MS view of the world seems to be 
that there are only 2 types of servers, Print and File.  If you have 
USW installed, then it only shows you NFS servers and LPR/LPD servers).


-- 

Seeya,
Paul
--
Key fingerprint = 1660 FECC 5D21 D286 F853  E808 BB07 9239 53F1 28EE

	It may look like I'm just sitting here doing nothing,
   but I'm really actively waiting for all my problems to go away.

	 If you're not having fun, you're not doing it right!