Hello list.
This seems to be the only suse-list thats right 4 this question
If i'am browsing my network neighborhood i can see me workgroup
where my samba-server is the pdc 4 (W2K). On W9x nothing is to
see despite an error on clicking "whole network" -> "network
cant
be browsed" (or so - me german).
If i search the server directly all wents fine and i can use the
shares -> so everything but browsing the workgroups works.
snip
----
[global]
workgroup = MYGROUP
netbios name = MYSERVER
interfaces = 192.168.1.1/255.255.255.255
bind interfaces only = Yes
encrypt passwords = Yes
log level = 5
log file = /var/log/samba.%m
time server = Yes
logon script = start.bat
domain logons = Yes
wins support = Yes
kernel oplocks = No
socket address = 192.168.1.1
hide local users = Yes
guest account hosts allow = 192.168.1.0/255.255.255.0
veto oplock files = /*;.DBF/
level2 oplocks = No
dos filetime resolution = Yes
fake directory create times = Yes
----
snap
and log.smbd says :
snip
----
[2001/10/26 13:06:19, 4] nmbd/nmbd_workgroupdb.c:dump_workgroups(292)
dump_workgroups()
dump workgroup on subnet 192.168.1.1: netmask= 255.255.255.0:
MYGROUP(1) current master browser = MYSERVER
MYSERVER 400c9b2b ()
[2001/10/26 13:06:19, 4] nmbd/nmbd_workgroupdb.c:dump_workgroups(292)
dump_workgroups()
dump workgroup on subnet UNICAST_SUBNET: netmask= 192.168.1.1:
MYGROUP(1) current master browser = UNKNOWN
~~~~~~~
MYSERVER 40099b2b ()
---
snap
What to do ? Thanks in advance.
Michael
Bill Moran
2001-Oct-26 05:52 UTC
Cant browse - Network name not found - shares working fine
On Friday 26 October 2001 07:15, Info wrote:> If i'am browsing my network neighborhood i can see me workgroup > where my samba-server is the pdc 4 (W2K). On W9x nothing is to > see despite an error on clicking "whole network" -> "network cant > be browsed" (or so - me german).I've seen this a lot with win9x and have never found a definitive solution to it. So I'd be curious ot hear from others as to whether or not what I describe below is consistent with other people. Generally, the solution I've found is to tweak with the network settings and reboot the machine a bunch of times (on the Windows machines). No particular network setting, just turn things on/off - change the workgroup and reboot the machine in between each time. After a while, it will start working, and then it will continue working, so you can set the network settings back to what they should be and get on with your life. My guess is that the Windows NetBIOS/TCP/IP stack doesn't refresh or iniitially get it's browse list information correctly. Changing the settings and rebooting would force it try again. Eventually it seems to get it right. Again, I'd be curious to hear other people's experience with this problem, as I don't really like the solution I presented above. But in my testing, I've never been able to isolate a specific setting that causes this problem. -- Bill Moran Potential Technology technical services http://www.potentialtech.com