samba - Oct 1997 - Browsing problems

Hi to all,

I've this problem:

When I start browsing in Explorer from my NT 4.0 SP3 Server, the 
SAMBA Server don't respond to the broadcasting.

ThanX for sugestions

---------------------------------
Ezio Bove
C.I.R.A. scpa
Italian Aerospace Research Centre
Informatics Dept.

Via Maiorise snc
81043 Capua (CE)
Italy

phone :+39 (0)823 62 3718
fax   :+39 (0)823 62 3126
mailto:e.bove@cira.it

http://www.cira.it
---------------------------------

Hello,

I installed Samba 2.0 on my OSF 4.0D server a couple of days ago, and
connecting to shares works just fine.

However, browsing the server does not seem to work.

We have a network with mostly NT 4.0 clients, plus some Win95.

Network Neighborhood on an NT client shows the server; double-clicking it
produces the error message "RPC Error".

Here is the GLOBAL section from my smb.conf:

        workgroup = Alcatel
        netbios name = Atunfs
        server string = ATUNFS Samba Server
        interfaces = 146.112.129.100/225.225.224.0
        bind interfaces only
        security = domain
        encrypt passwords = Yes
        password server = attdcp attnt1 attnt2 attnt3
        username map = /usr/local/samba/lib/smbusers
        password level = 9
        username level = 9
        log level = 5
        log file = /var/log/samba/log.%m
        max log size = 50
        socket options = TCP_NODELAY
        printcap name = /etc/printcap
        local master = No
        wins support = Yes
        printing = bsd
        case sensitive = Yes
        guest account = nobody
        browseable = Yes

Any help would be appreciated.

-- 
W. N. Paul/KSS(sun) * Alcatel Austria * Scheydgasse 41 * A-1210 Vienna, Austria 
wnp@aut.alcatel.at * +43-1-277-22 x5523 (voice)/x1118 (fax) * +43-1-774-1947 (h)

Stephen L. Arnold <arnold.steve@ensco.com> writes,
> When the world was young, Wolf Paul carved some runes like this: 
> 
> > However, browsing the server does not seem to work. 
> > 
> > We have a network with mostly NT 4.0 clients, plus some Win95. 
> > 
> > Network Neighborhood on an NT client shows the server; double-clicking
it
> > produces the error message "RPC Error". 
> 
> Are you sure you want WINS support = yes? Isn't one of your NT 
> boxes providing the WINS service? What about the results of the 
> test steps in diagnosis.txt? Browsing is a function of nmbd (not 
> smbd)... I've never seen the "RPC error" (but we only have
one NT4
> workstation machine on the LAN). More Info? 
No, we don't have another WINS server in our network; but no, I am not
sure that I want SAMBA to provide that functionality either. Our network
seems to work fine without it.

The reason I turned it in is just in case my browsing problem is a name
resolution problem and this might just help  ... but I am nowhere near sure.

In fact my network administrators and the NT platform admins would prefer
that my SAMBA server only talk when directly spoken to, and does not 
respond to broadcasts since they are afraid that this might confuse the
genuine NT servers/clients.

More info:

The exact error message was not "RPC error" but as I said in a later 
message,

	"\\Atunfs is not accessible. The remote procedure call failed." 

Variously, as I specify different options for "guest account" or 
"local master", "os level", etc, the error message changes;
sometimes
prompting me for a password and then (regardless of the password given)
complaining about a wrong password for the IPC$ service. (This
seems the standard error when trying to browse from a Win98 machine).

I just went through the tests in DIAGNOSIS.txt, and here are the results:

   Test  1:  testparm does not report any errors.

   Test  2:  ping works both ways.

   Test  3:  smbclient -L atunfs prompts for a password, and
            after pressing ENTER (= empty password) provides the list
            of shares.

   Test  4:  nmblookup -B atunfs __SAMBA__ works.

   Test  5:  nmblookup -B clientpc '*' works.

   Test  6:  nmblookup -d 2 '*' works, producing reams of IP addresses

   Test  7:  connecting to shares with smbclient using explicit paths works

   Test  8:  net view \\atunfs does NOT work, produces the error msg,
            "System error 1726 has occurred". 
            "net helpmsg 1726" produces, "The remote procedure
call failed".

   Test  9:  connecting to shares with "net use" using explicit paths
works.

   Test 10:  Browsing from File Mangaer& My Computer Map Network Drive
             or from Network Neighborhood does not work but says either
             "\\Atunfs is not accessible. The remote procedure call
failed."
             (Network Neighborhood) or "The remote procedure call
failed."
             (My Compter & File Manager Map Network Drive).

The above results for Tests 8 and 10 applies to NT 4.0; from a Win98 client
on the same network both Tests 8 and 10 succeed; similarly from a Win95 client.


All of this is independent of whether SECURITY is set to SERVER or to 
DOMAIN, and whether WINS is enabled or disabled on the Samba server.
For the sake of completeness here is my GLOBAL section again:

        workgroup = ALCATEL
        netbios name = ATUNFS
        server string = ATUNFS Samba Server
        interfaces = 146.112.129.100/19
        security = DOMAIN
        encrypt passwords = Yes
        password server = attdcp attnt1 attnt2 attnt3
        username map = /usr/local/samba/lib/smbusers
        password level = 9
        username level = 9
        log level = 3
        log file = /var/log/samba/log.%m
        max log size = 50
        name resolve order = host bcast
        socket options = TCP_NODELAY
        printcap name = /etc/printcap
        lm announce = True
        local master = No
        printing = bsd
        case sensitive = Yes
        guest account = pcguest

   
       

I have no smbpasswd file (since I use security=DOMAIN); I have a 
usermap file which maps NT users to UNIX users (this works when 
connecting a share using the explicit path \\atunfs\sharename);
for all but a handfull of system accounts my UNIX passwd info comes via
NIS; the guest user "pcguest" is one of the local users in
/etc/passwd,
with a '*' in the password field. (This is a change from yesterday, to
make things clearer I changed the guest account from nobody to pcguest.)

Hi,

I have exactly the same problem with samba 2.0 and my NT4 clients. When I try 
to browse the shares in the Network Neighborhood, I get the error message:
 
	\\server is not accessible. The remote procedure call failed.

No problem with samba 1.9.x or Win95.

The only thing that make browsing works is to reduce the number of browseable
shares and/or the length of the corresponding "comment=" lines. For
me, with ~ 50 shares it works with ~ 70 I get error message... But this is not
an acceptable fix it.

I am interested by any idea to correct this problem...

Maurice.


Wolf Paul <wolf.paul@aut.alcatel.at> wrote: 
> Hello, 
> 
> I installed Samba 2.0 on my OSF 4.0D server a couple of days ago, and 
> connecting to shares works just fine. 
> 
> However, browsing the server does not seem to work. 
> 
> We have a network with mostly NT 4.0 clients, plus some Win95.

> \\server is not accessible. The remote procedure call failed.
...
> The only thing that make browsing works is to reduce the number of
browseable shares and/or the length of
> the corresponding "comment=" lines. For me, with ~ 50 shares it
works with ~ 70 I get error message...
> But this is not an acceptable fix it.
This is a known problem which has already been fixed for 2.0.1, to be
released soon.

Indeed reducing the length of share comments is a valid workaround.

Cheers,

    Matt (Samba Team)

Hi!

I have the following topology of
my LAN:

  --------     eth1  -----------------------
 | A Win95|---------|Samba WINS Server 2.0.6|
  --------           -----------------------
                        | eth2
                        |
                        |
                       ---------
                      | B Win95 |
                       ---------

 Two Win95 host in the same work group
 Samba Server in different. Win95 boxes
 use Samba Server as WINS server.
 In such situation host A never sees 
 host B in "Network Neighbourhood" because
 neither host A nor host B becomes DMB, only LMB.

 Is there any solution for this problem without 
 rediretion of broadcast traffic between segments
 of LAN on Server?

 Thank you for any answers!

   - Best Regards,
	  NSC KIPT
	  Network Operation Center
	  Andrew A. Razdolsky

Hi, I'm hoping someone can help with this - we're having some spurious 
Win95/98 browsing problems and although I'm continuing to experiement 
with things, I'm really not sure whats causing the problem. I've read 
the docs and various Samba books, but I'm no closer to a solution at the 
moment.

We currently have three subnets and five workgroups in our network, 
arranged like this:

Subnet 1:
workgroup 1
workgroup 2
workgroup 3
workgroup 4

Subnet 2:
workgroup 5

Subnet 3:
workgroup 1

So workgroup 1 spans two subnets.
Subnet 1 is the main subnet. Subnet 3 routes through subnet 2 to reach 
subnet 1 (does that make sense worded like that???)

Workgroup 1 - Samba LMB, Win9x workstations.
Workgroup 2 - Samba WINS server, Samba LMB, plus two other Samba print 
servers, configured NOT to be browse masters.
Workgroup 3 - Samba DMB (controlling domain logons.
Workgroup 4 - Win2000 server(!!!), Win9x workstations.
Workgroup 5 - Samba LMB, Win9x workstations.

I hope that makes sense! SO, here's the problem:
WIndows clients in subnet 1/workgroup 1 can browse all five workgroups. 
The only problem they have is not seeing the machines on subnet 3 (same 
workgroup).
The Win200 server in workgroup 4 can only browse its own workgroup.
WIndows clients in subnet 2/workgroup 5 can browse all workgroups EXCEPT 
workgroup 1 (this results in a "share name not found" error)
WIndows clients in subnet 3/workgroup 1 can only browse machines on that 
subnet.

smbclient -L localhost -U% on any samba machine returns a correct list 
of servers and master browsers.

All Samba servers and Windows clients are configured to use the WINS 
server and there's no problem accessing shares either by mapping drives 
or using net use in DOS. I'm not sure of two things though - maybe the 
Win2000 server is interfering with the Samba servers? and maybe I 
misunderstood the Samba browsing docs :o)

If anyone has any pointers for this I'd be most grateful - I know 
browsing can be a pain in the backside, and it isn't exactly essential, 
but it would be nice if I could get this working.

Many thanks in advance
Matt Claridge
I.T. Systems Officer
BBNPA

Hello,

I have some trouble with getting samba the master browser of a domain. Samba
is already the PDC of this domain and there is a Win 2000 Server which is
only a file- and databaseserver. In the smb.conf I switched every
browsing-options to true (local master, prefered master, domain master). The
Win 2000 Server is configured not to be the master broweser. But always the
Win 2000 Server wins every election. Has anybody an idea whats wrong?
By the way: The OS-level is set to 80.

Thanks,
H. Acker