search for: workgoups

Hi all, I am trying to come up with an architecture that has some redundancy. The idea is to hook up the two GbE LAN interfaces of a CentOS server to two Gigabit Ethernet switches. In case one switch goes down, there is a redundant path (the server is redundant too). Here is the idea: ----------- | GbE | PCs

Hi, I'm getting confused about the role that kerberos authentication plays. What exactly is the point of using kerberos to join a samba server to an AD domain? If using kerberos still requires you to rely on winbindd for all the nsswitch stuff then what is the point? I can just as easily specify workgroup = wkgrp security =

Hi, I am configuring a network with two subnets with a different workgroup in each subnet. My aim is to have users being able to view and access shares on both workgroups. I have a Samba server in each subnet/workgroup, configured as both the domain and local master for each workgroup. Each server is also the WINS server for its subnet. The setup is like this: Subnet1: network -

...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)....

Hello everybody! I finally managed to set up a Samba 3.0.1 PDC that ran perfectly in the test-environment. Problems arose, when I installed it in a real bureau network. On a prepared w2k client that was already a domain member one could log on to the domain with the administrator's account, but trying to add other w2k clients failed with error msgs like: "Domain controller not

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 to...

I think you need a DMB and LMB. Assuming you have no NT servers in your network, try these in [global]: domain 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

Hi all, I need a little more detail to a previous response from 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

When I run smbclient 1. smbclient //LINUX01//homes -U test password is requested, I enter the password, and I get in 2. smbclient //LINUX01//homes -U Jane password is requested, I enter the password, and I cannot get in (ERRSV - ERRbadpw (Bad Password - name/password pair in a Tree Connect or Session Setup are invalid) 3. smbclient