Re: (fqdn) hostname resolution when using DHCP

1999-12-31 Thread John Hasler
Phil Brutsche writes: > Samba won't necessarily work if you don't have the hostname pointing to > the IP in /etc/hosts. Are you saying that samba will may not work if you have both lines, like this? 127.0.0.1 hasler.dhh hasler localhost 192.168.1.1 hasler.dhh h

Re: (fqdn) hostname resolution when using DHCP

1999-12-31 Thread aphro
On Fri, 31 Dec 1999, Salman Ahmed wrote: ssahme >Could this be a case of the DHCP server treating Windows clients ssahme >differently than non-Windows clients ? Majority of the DHCP clients at ssahme >our place are Windoze boxes. yes, if they are pointed at different DNS then anything is possible

Re: (fqdn) hostname resolution when using DHCP

1999-12-31 Thread Phil Brutsche
A long time ago, in a galaxy far, far way, someone said... > Salman Ahmed writes: > > What should I add to this file so I can ping from the machine itself by > > giving its fqdn hostname ? > > 127.0.0.1 matrix. matrix localhost. > > With this line any process on the machine can reach the machine

Re: (fqdn) hostname resolution when using DHCP

1999-12-31 Thread John Hasler
Salman Ahmed writes: > But the second line in /etc/hosts will have to be updated/modified > whenever the DHCP lease for that IP address runs out. If you have a proper localhost line in /etc/hosts you don't actually need the IP of your interface in there at all. -- John Hasler [EMAIL PROTECTED] (J

Re: (fqdn) hostname resolution when using DHCP

1999-12-31 Thread John Hasler
Salman Ahmed writes: > What should I add to this file so I can ping from the machine itself by > giving its fqdn hostname ? 127.0.0.1 matrix. matrix localhost. With this line any process on the machine can reach the machine itself via the fqdn, the hostname, or just 'localhost'. Phil Brutsche wr

Re: (fqdn) hostname resolution when using DHCP

1999-12-31 Thread aphro
On Thu, 30 Dec 1999, Salman Ahmed wrote: ssahme > ssahme >Whenever I try to ping this machine (from itself) by giving the ssahme >fqdn hostname, I get an error message like: ssahme > ssahme > unknown host matrix.domain.com ssahme > ssahme >nslookup on that fqdn hostname gives an error message sayi

Re: (fqdn) hostname resolution when using DHCP

1999-12-31 Thread hypnos
<<< No Message Collected >>>

Re: (fqdn) hostname resolution when using DHCP

1999-12-31 Thread Phil Brutsche
A long time ago, in a galaxy far, far way, someone said... [...] > Some more questions: I seem to be getting the same IP address through > DHCP. That's the way it works - each time you reboot you get the same IP until the lease time runs out. > After the DNS config update, I can ping this machin

Re: (fqdn) hostname resolution when using DHCP

1999-12-31 Thread aphro
On Thu, 30 Dec 1999, Salman Ahmed wrote: ssahme >I got one of the network admins to update their DNS config so that the ssahme >hostname of the machine is mapped to the machine's ethernet address. ok ssahme >Some more questions: I seem to be getting the same IP address through ssahme >DHCP. Afte

Re: (fqdn) hostname resolution when using DHCP

1999-12-30 Thread aphro
On Wed, 29 Dec 1999, Salman Ahmed wrote: ssahme >how this work ? Will this approach require the network sysadmins to ssahme >change their (internal) DNS configuration ? Our network admins know of ssahme >only one OS: Windoze, and generally don't know d*** about ssahme >Unix/Linux/*BSD, so I am a l

Re: (fqdn) hostname resolution when using DHCP

1999-12-29 Thread aphro
you could add a domain to a DNS in your local network so that works, or what is probably easier is look for the lmhosts file on the windows box (use find) it may be called lmhosts.sam or some shit, add the ip and the names there, it seems to be window's version of /etc/hosts. you may have to renam