I having difficulty getting browsing to fully work across two subnets. The subnets (having private addresses - 192.168.x.0) are connected by Linux boxes (RH6.1, one for each subnet) functioning as firewall, IP masquerade and router. On one subnet (call this one LEFT), there is an NT4.0 server as the PDC (also running WINS and DHCP) along with 50 or so clients and other servers (NT, Win9x) in several different workgroups. On the other subnet (call this one RIGHT), there is a single Win9x client. The Linux box on RIGHT is running dhcpd (which provides the IP address of the WINS server on LEFT for the netbios-name-server) and Samba with the following lines in the smb.conf: workgroup = MYWORKGROUP local master = yes perferred master = yes wins support = no os level = 65 wins server = <IP address of the PDC/WINS>>From the client on RIGHT, using Network Neighborhood I can see all of themachines in MYWORKGROUP on LEFT plus the other workgroups. I can only browse into certain of the clients (no common characteristics yet determined) but not others; the message says that the computer is not accessible. None of the other workgroups can be browsed into.>From a client on LEFT in MYWORKGROUP, all of the clients in the sameworkgroup can be seen and browsed into and the other workgroups can be browsed into as well. However, neither the shares on the Samba server on RIGHT nor the client machine on RIGHT can be seen in NN but both can be located by Find Computer and browsed into by that means. Is there something that I am missing or is this a limitation of the browsing services of Samba? Thanks
Hello, "Kinzer, Don" wrote:> >From the client on RIGHT, using Network Neighborhood I can see all of the > machines in MYWORKGROUP on LEFT plus the other workgroups. I can only > browse into certain of the clients (no common characteristics yet > determined) but not others; the message says that the computer is not > accessible. None of the other workgroups can be browsed into.One reason may be that there are some computers that are not registered in the WINS database, because they may be not configured to use WINS for NetBIOS name resolution. Is your DHCP working fine (and does it also assign the IP address of the WINS machine)? You can look at these computers (using "ipconfig /all" or "winipcfg") on the RIGHT whether they are really configured for using WINS.> >From a client on LEFT in MYWORKGROUP, all of the clients in the same > workgroup can be seen and browsed into and the other workgroups can be > browsed into as well. However, neither the shares on the Samba server on > RIGHT nor the client machine on RIGHT can be seen in NN but both can be > located by Find Computer and browsed into by that means. > > Is there something that I am missing or is this a limitation of the browsing > services of Samba?Perhaps there are other protocols than TCP/IP running on some machines on LEFT. So it might be possible that there is a "parallel" browse list which is built up using NetBEUI or IPX. If you don't really need IPX (e.g. for accessing Novell servers) or NetBEUI I suggest to disable these protocols on your clients. Another hint: Sometimes there is a "dummy0"-device set up on linux machines. This can also be the cause for troubles with browsing on samba machines. If not needed, disable "dummy0". Bye, Steffen
Apparently Analagous Threads
- XP clients cannot find Samba
- Samba4 Problem Rename
- Re: Samba 3.0.23c + Win2K AD, can't mount shares (PANIC: internal error)
- Unable to join samba server to a NT4 style domain/Sam ba-Guide feedback
- Samba 3.0.23c + Win2K AD, can't mount shares (PANIC: internal error)