search for: workgoup

...dundant too). Here is the idea: ----------- | GbE | PCs ------------| switch |------------ | | ----------- | | ----------------- ----------------- ---| Workgoup Switch | | CentOS/Asterisk | | ----------------- ----------------- | | ----------- | VoIP ------------| GbE |------------ Phones | switch | -...

...what is the point? I can just as easily specify workgroup = wkgrp security = domain and do a net join Instead of doing realm = wkgrp.krb.realm workgoup = wkgrp security = ADS and doing net ads join Are there performance benefits/better security...what?? I think that maybe my understanding of the kerberos setup is a bit flawed. thanks for any replies, Mark Le Noury

...d connected to console... Strange thing is, that in that screen it shows on username in "samba_realm\username" format (realm in uppercase), not "samba_WORKGROUP\username" format, that I actually supplied (realm is, how it is called in smb.conf - ad.company_name.blaah while workgoup is COMPANY_NAME). -- Virgo P?rna virgo.parna at mail.ee

...es = lo eth0 192.168.10.254/24 127.0.0.1/8 bind interfaces only = yes remote announce = 192.168.20.254/GROUP1 remote browse sync = 192.168.20.254 hosts allow = 127. 192.168.10. 192.168.20. The problem is that a machine in Group1 can see all the machines in it's workgoup, plus the network for Group2 appears in network neighborhood, but the machines and shares in Group2 do not. To troubleshoot, I ran smbtree with debug level 5. What I picked out from all the output was: Cannot find master browser for workgroup GROUP2 How can I resolve this? Tawanda

...ystem. [root@appgen root]# nmblookup caja querying caja on 192.168.5.255 192.168.5.42 caja<00> [root@appgen root]# smbclient //caja/c added interface ip=192.168.5.50 bcast=192.168.5.255 nmask=255.255.255.0 Connection to caja failed if I could resolve _why_ some Win systems have _two_ Oteima workgoups (one to which I can connect to _all_ listed systems and one to which I cannot connect to any) I could resolve this dilemna. I've tried: changing workgroup name (all lowercase, all uppercase, mixed upper/lower case); encrypt passwds yes/no. Changing protocol mins and maxs (from CORE to NT1)....

...refering to WINS aso. I took the radical way and reinstalled Samba with the same configs but with a different domain name. That solved the problem for once. But it leaves a general problem: It looks as if you can render a PDC unusable if you introduce a machine into its network, that is in a workgoup of the same name as the domain. So my question is: How do I configure the Samba PDC that clients within the same network know who is the master of the universe and who is just an impostor? Especially the PDC itself should not get confused about this! The relevant entries (I think) in my smb.co...

Hi, I am a new member of this list and I couldn't find and message to help me in the Samba archives. We're migrating from a FreeBSD 4.0 server with Samba2 to a FreeBSD 5.3 server with Samba 3.0.12_1,1. These too servers are on the same network, but workgoups are different (old server is DESQ-Samba and the new one is NDESQ). Our network have Windows 95, 98, NT, 2k and XP! This old server uses the master.passwd to authenticate users, I tried to do the same with the new one, but I couldn't get a passwd backend (plain text) to do this, so I moved t...

On 22.01.2025 12:38, Virgo P?rna via samba wrote: > On 22.01.2025 12:25, Rowland Penny via samba wrote: >>> >>> ????After this started happening, I did try setting same password >>> again for user with smbpasswd in linux. >> >> Try using samba-tool to set a new password for the user. > > ????I'l try it. Did try it, did not work. >

...> > ????Strange thing is, that in that screen it shows on username in > "samba_realm\username" format (realm in uppercase), not > "samba_WORKGROUP\username" format, that I actually supplied (realm is, > how it is called in smb.conf - ad.company_name.blaah while workgoup is > COMPANY_NAME). > > > Hi Virgo, I assume you use freerdp ver. 3 for connecting to the Windows 11 24H2 desktop remotely. It is very particular about how you enter domain and user name. There seems to be only two accepted ways Either /d:<domain.name.net> /u:<user name&gt...

...main master=yes preferred master=yes local master=yes os level=65 Note that if your other workgroups are on separate subnets, this gets trickier, involving WINS, etc. Steve Litt At 09:09 PM 02/16/2000 +1100, you wrote: >Hi all, >can anybody explain why win9x (or i think also NT) from other workgoup >than samba can not see shares through network neighbourhood? Guest account >exists and when i win9x reconnect to same workgroup everything is o.k. >Else win client wants password to IPC$. > >Same problem from one NT works to other. I'm logged in on local and i can >not se...

...om this list. Please excuse my newbie-ness! My problem is: When trying to logon from the Win98 machines we get a dialog box coming up with the title Microsoft Networking and the text: 'Incorrect Parameter'. A posted answer was: > > Most often this is seen when the netbios name and workgoup > parameters in your smb.conf have the same parameters. > Can someone define "workgroup parameters"? I am already using different a netbios name and workgroup name. What else is there?? Thanks, Bill

...ws always tells me "invalid parameter" (or > similar, german windows) although username, password and servername > are right and i have a logon share on my samba server. Can anybody > tell me whats wrong? thanks, Harald Stangl Make sure that the Samba host's netbios name and workgoup value are not the same string. Cheers, jerry ---------------------------------------------------------------------- /\ Gerald (Jerry) Carter Professional Services \/ http://www.valinux.com/ VA Linux Systems gcarter@valinux.com http://www.samba.org/...