From: José Luis Gómez Dans ([email protected])
Date: Tue Nov 07 2000 - 11:44:47 CET
On Tue, Nov 07, 2000 at 08:40:41AM +0000, Daniel Bourrion wrote:
>
> With smbclient -L localhost -N, i get this on my mulinux laptop :
>
> « Get_Hostname : unknown host mulinux
> failed to get my hostname
> added interface ip=0.0.0.0 bcast=255.255.255.255 nmask=0.0.0.0
> Get_Hostname : unknown host mulinux
> Get_Hostname : unknown host mulinux
> erro connecting to 127.0.0.1:139 (connection refused) »
Good, it isn't working, we know there's an error so we can
subsanate it! (eternal optimism here...). The problem here arises from
the fact that mulinux calls the box you run it on mulinux by default (I
think it has a default domain, but I'm not sure of this). What you want
to do is to make sure your computer _knows_ the mulinux computer by
name. You can do this in two ways. The simplest is to probably add it to
/etc/hosts. It might look something like this:
127.0.0.1 k3wlb0x localhost
xxx.xxx.xxx.xxx mulinux
where xxx.xxx.xxx.xxx is mulinux's address (you can check this with
ifconfig -a.
Anyway, I have just realized that this is all very well, but
it's not relevant to your first problem. It looks as if your own mulinux
server isn't even aware of itself! I presume that localhost isn't
properly configured. Again, (and now in your mulinux), you can edit
/etc/hosts and add an entry like the one above, but in this case
127.0.0.1 mulinux localhost
so that smbclient can resolve the localhost to itself.
Sorry about the random divagations, try that and see what
happens!
Regards,
José
-- José L Gómez Dans PhD student Tel: +44 114 222 5582 Radar & Communications Group FAX; +44 870 132 2990 Department of Electronic Engineering University of Sheffield UK --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
This archive was generated by hypermail 2.1.6 : Sat Feb 08 2003 - 15:27:16 CET