Did you put the WINS ipaddress in the windows client? if it don't no where to get the info I have found it to get the info. There is a way to put that in the DHCP Server setting, that is beyond me.
Also you can do a locate tdb files and do a tdbdump on the wins info.
Do you have user accounts, like any setup?
Also do you have "host allow = " and "host deny = " along with the "interfaces =" setup correctly?
Some things to look at.
Karl


Craig White wrote:
On Mon, 2006-01-02 at 22:24 -0600, Eric Hines wrote:
At 01/02/06 21:37, Adam Nielsen wrote:
I'm having trouble connecting to my Samba server.  The immediate
symptom is that I cannot see my Samba server in my Windows Network
Neighborhood, and so I cannot connect to it to check my share
connections.
----
try 'wins support = yes' in smb.conf
----
You can still go Start | Run \\ip.address to connect to a 'hidden'
Samba server.
I get a "network path not found" error. However, when I do the same thing for each of the two subnets, I get invited to log in (my Samba error, I think--I may have not yet put anything into my tdbsam. I'm still trying to get the network itself to work.)

I can ping all by hostname, as well as by FQDN; although it appeared
that I could not ping sserver by hostname only until I added sserver
and its FQDN to the PC's host file (which it reads as though it were
an lmhosts file).  I say "it appeared" because it looked like the
forward and reverse look up files for sserver appeared in the PC's
resolver cache before I made this addition, but I got too fast with a
ping test and contaminated that datum.
It sounds like "nmbd" isn't running, or more likely, it's only running
on one subnet.  There are all sorts of issues using NetBIOS names
across different subnets, but Google will tell you all about that.
I do have only one instance of nmbd running, and two of smbd. How do I get another nmbd instance to run?
----
not needed
----

If running \\samba.ip on a Windows box works, then this is definitely
the problem.
Additional data, from an error log I have named.conf generating, keeping in mind that I have dynamic dns turned on. I'm getting messages to the effect that my test1 dot biz dot hosts dot jnl file (test1 dot biz dot hosts is the forward lookup file that, among other things, defines the points of contact for my two subnets) cannot be created due to a permission denied error. My test1 dot biz dot hosts forward lookup table lives in /var/lib/named/master directory, with permissions rw-r--r--, and it's owned by root:root. Further, even though I have ddns running, this test1 dot biz dot hosts file remains unchanged from the day I created it--not a thing has been added to it. Should there have been by now, or am I exposing my ignorance here? Further, my named and dhcpd are running in separate chroot jails. Is this causing problems with updating this file--or any other of my forward lookup files?
----
on most systems, named runs as user named and thus cannot make changes
to files owned by root:root and cannot create journal files in folders
unless owned by named:named and chmod 775
----
Finally, what do the error messages mean, and what do I need to do to correct that?
----
probably follow some of the best documentation available and resist the
temptation to shortcut it.

http://samba.org/samba/docs/man/Samba3-ByExample/

this might be just the chapter you are looking for...
http://samba.org/samba/docs/man/Samba3-ByExample/Big500users.html

Craig

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Reply via email to