20 Feb
2004
20 Feb
'04
12:20 p.m.
There is a windows-host in our homenetwork which prefers to stay invisible
from others. The server is set up as authentication server and works fine
even for this computer except that the computer I mentioned doesn't show up
in any browse list. (even in network neighbourhood on its own desktop).
The computers ip is correctly resolved if I use only the hostname part. I
added it to hosts and even to lmhosts (which should not even be needed
because there is also dns). Wins-support is enabled and I told the windows
hosts to use wins. I also switched the lm-advertising from automatic to on,
with no results.
Does anybody know what I should watch for? The weird thing is that two other
machines are as far as I can tell set up exactly the same way and they show
up in network neighbourhood.
Samba version is 3.0.1
Thanks for any hints.
20 Feb
20 Feb
2:18 p.m.
Hi,
On Fri, 20 Feb 2004, Jay Christnach wrote:
There is a windows-host in our homenetwork which
prefers to stay invisible
from others. The server is set up as authentication server and works fine
even for this computer except that the computer I mentioned doesn't show up
in any browse list. (even in network neighbourhood on its own desktop).
The computers ip is correctly resolved if I use only the hostname part. I
added it to hosts and even to lmhosts (which should not even be needed
because there is also dns). Wins-support is enabled and I told the windows
hosts to use wins. I also switched the lm-advertising from automatic to on,
with no results.
Ugh, normally you only enable TCP/IP plus sharing on the
Windows boxes, none of that WINS stuff or (lm)hosts fiddling.
Just see about proper DNS setup on the network (not even sure
if that's absolutely necessary). bind ain't that hard to
manage, at least for such routine stuff.
Does anybody know what I should watch for? The weird
thing is that two other
machines are as far as I can tell set up exactly the same way and they show
up in network neighbourhood.
Samba version is 3.0.1
Have you tried an "smbclient -L //ip.of.the.box"?
I imagine all boxes are present on the same workgroup or domain?
What kind of Windows is it, XP? If so, check if any of the builtin
firewalling is active, check if there's XP AntiSpy that would be
blocking accesses (or slow them down immensely).
The Samba book might also give some insight (should be much
better than any MS doc anyway).
<evil grin>Depending on the use of the machine - see if the user
would even notice if you put a KDE box instead.</evil grin>
Greets & hth, Eric
7393
days inactive
7393
days old
1 comments
2 participants
participants (2)
-
Eric Dondelinger -
Jay Christnach