I have 2 subnets. Subnet 1 has an NT WINS server. Subnet 2 has a Samba server acting as domain master browser and local master browser for a workgroup. If I view the network neighborhood from a Win 95 PC on Subnet 1 (call it PC_A), I can see all the hosts in the workgroup on both subnets. If I view the network neighborhood from a Win 95 PC on Subnet 2 (call it PC_B), I cannot see PC_A. I CAN 'map a network drive' on PC_B for a directory that has been shared by PC_A. Both PCs are in the same workgroup (which happens to be the same workgroup as the Samba server). What might be the reason(s) that I can map a network drive of a PC, but cannot see it in the network neighborhood?
Hi all, I'm fighting with cross-subnet browsing with the samba PDC I'm trying to set up. I've got all the settings in the smb.conf set correctly, I think my problem lies in not completely understanding how browsing really works and how domain logins are related. In my current environment, the domain we log into is controlled from an NT PDC outside of my facility. Directed broadcasts are not enabled on any of the routers here, and there are no wins servers on any of the subnets within the building. Yet domain logins work fine, as do browsing the domain. My assumption as to why this all worked, was that each win95 client uses DHCP to boot and is handed both a primary and secondary WINS server IP address. This would allow the booting clients to identify which system was the domain logon system, log onto the domain, then browse the domain. So, I set up my Samba PDC and got everything working while the client was connected to the same subnet. I could log onto my new domain, run the logon script, and browse the server in Network Neighborhood. When I moved my client to a different subnet, things broke. I have the client settings all set up correctly. The Samba PDC is also the master browser, etc., and the client has the IP address of the server as it's primary WINS server. Yet, now I can't even log into the domain. I get the "No domain server was found to authenticate you" error. Obviously all the docs state that you need to have local browse masters on each subnet to sync with the PDC, etc. But my question is why does this work in the "NT" domain but not in the "Samba" domain? Am I misinterpreting the meaning of the client "Primary WINS Server" setting? Is there something else I'm missing, or is there something fundamentally different wrt the way NT and Samba deal with cross-subnet browsing? I'd like to be able to do this without needing a WINS server on every subnet. Since the IS group is doing this with their NT PDC for their domain, shouldn't I be able to accomplish the same thing with Samba? Here's the configuration I have so far wrt the browsing options: os level = 33 domain master = yes local master = yes preferred master = yes wins support = yes Thanks for any clarification anyone can provide. -- Seeya, Paul ---- plussier@baynetworks.com Broadband Technology Division - Bay Networks (now a Nortel Company, Eh? :) If you're not having fun, you're not doing it right!
Hanns-Peter Ermert
1999-May-25 19:45 UTC
Problem samba-2.0.4b - NT-ACLs and Winframe 1.6/1.7 "the paranmeter is incorrect"
With NT 4.0 machines ACLs can be looked up as described in the samba docu. But with Winframe/Wincenter (NT3.51) when we try to access ACLs in Filemanager->Security ->Permissions then I get the message: "the parameter is incorrect" . The owner-Information using Filemanager->Security->Owner works correct. The pull-down menu (Filemanager->Security) shows selectable entries only if a file is selected whereas all entries are grayed out if a directory is selected. This happens with samba-2.0.4b on solaris 2.6 , sparc ultra-4 . Probably we will get same results on different platforms. Anybody out there who has similar experience? Regards Peter Ermert -- Ing. Buero Ermert, Dipl. Inform Hanns-Peter Ermert, 10715 Berlin email: Hanns-Peter.Ermert@alcatel.de / Alcatel SEL AG,ZNBIT 12099 Berlin,Colditzstrasse 34-36,Tel:+49-30-7002-4766/4788
Hi all, we have a lot of PCs running Win95 (several versions) and WinNT (3.51, 4.0, SP3, SP4, ...). Is it possible to restrict the server access only to PCs running a specific OS (Win95 OSR2.5 or NT4 SP4) and deny access for all the "older" clients? I think one way to do this is to use an include file, which contains the OS in the filename, but I believe the variable "%a" is not specific enough. In the logfile I saw the entries: "... NativeOS=[Windows 4.0] NativeLanMan=[Windows 4.0]" "... NativeOS=[Windows NT 1381] NativeLanMan=[]" How can I use this information in the smb.conf? My second question: Is it possible to restrict the server access only to PCs with a given mask(!) for the NetBIOS-name. The "hosts allow"-parameter is only useful for IP-masks, but I can?t specify a NetBIOS-mask like "pc[0-9][0-9][0-9][0-9]". But I want to suppress the server access for PCs called "MyComputer", "MyPC", "Room1", "Bob?sPC" or so. On the other hand I can?t list all possible and allowed NetBIOS-names in a list, because there are more than 2.000 correct NetBIOS-names and I think this would slow down the samba server. -- Thanks for all comments.
Hi ! Here`s my configuration: - Linux (P133 32Mb 2Gb HD RedHat 5.2 kernel 2.2.4, samba 2.0.3) - 5 Windoze 98 clients When i copy files from Wind. to samba, my file-server halts. I can`t even write anythnig from command line. Only way out is to switch off the power :( Any suggestions Daniel ---------------------------------------- - Hiroszima 45 Czernobyl 86 Windows 95 - ----------------------------------------
Hi, I'm trying to get cross-subnet browsing to work and am getting hopelessly confused at the moment! We have the following (simplified) network configuration: Serveral NT4 & Win95 machines on a token ring network. This includes a PDC, BDC, WINS server and DNS server (MS-DNS). Ethernet segment with a few Linux boxes on it; I'm trying to set up Samba on one of these (Redhat 5.2, Samba 2.0.7) NT4 machine doing the routing between the two networks. I've created a server account for the Linux machine on our PDC. Now, if I configure Samba on the Linux box with user level security I can access shares on it, but I can't see the server in the network neighbourhood on one of the windows machines on the token ring network. I can get to it using 'net view' from a DOS shell however, or via 'find computer' in explorer. I've added the IP of our token-ring-based WINS server into the Samba configuration on the Linux system, then I turned DOMAIN-level security on - I still don't see the server in network neighbourhood though, and using net view gives me an "unknown username or bad password" error. (behaviour with Samba 2.0.3 was similar but with slightly different error messages) Any ideas? I've only configured this via SWAT so far - are there things I need to add to the smb.conf file which SWAT doesn't configure in this case? Do I need to set up a WINS server or something on the ethernet (I hope not, I don't think our sysadmin guys would be too happy with that)? please email any ideas... cheers Jules
Possibly someone somewhere can help with this... I am in the process of moving our companies major network from a switched and shared network, to a routed and switched network. At the moment we are in a very hybrid state which is likely to continue for some time. I will try to explain what we have. --cut-- I did try writing an explanation but couldn't keep it brief. If someone thinks they can help I'll be happy to give you further details. The LMB for one of our routed networks doesn't seem to be collecting the browse list from our DMB (also PDC). Also we seem to be getting entries in nmbd's log to say that the LMBs of these remote nets are claiming that they are LMB of the local net. They _are_ LMBs but of _their_ Local net. So why is nmbd then having elections on the local net. If you think you can follow the following log snippet, (it's easier to follow that the above!) then maybe you can help. I've over a hundred PC users going mental at the moment so any ideas whether tried already or not are more than welcome. Here's the log.... process_local_master_announce: Server LISA at IP 192.168.10.130 is announcing itself as a local master browser for workgroup GFMNET and we think we are master. Forcing election. unbecome_local_master_browser: unbecoming local master for workgroup GFMNET on subnet 10.0.0.3 ***** Samba name server GFMNET01 has stopped being a local master browser for workgroup GFMNET on subnet 10.0.0.3 ***** send_election_dgram: Sending election packet for workgroup GFMNET on subnet 10.0.0.3 send_election_dgram: Sending election packet for workgroup GFMNET on subnet 10.0.0.3 send_election_dgram: Sending election packet for workgroup GFMNET on subnet 10.0.0.3 send_election_dgram: Sending election packet for workgroup GFMNET on subnet 10.0.0.3 send_election_dgram: Sending election packet for workgroup GFMNET on subnet 10.0.0.3 run_elections: >>> Won election for workgroup GFMNET on subnet 10.0.0.3 <<< become_local_master_browser: Starting to become a master browser for workgroup GFMNET on subnet 10.0.0.3 ***** Samba name server GFMNET01 is now a local master browser for workgroup GFMNET on subnet 10.0.0.3 ***** ------------- Many thanks. Con Harte.