Displaying 20 results from an estimated 6000 matches similar to: "Workgroup name too long"
2015 Feb 26
1
Workgroup name too long
>> From: schulz at adi.com (Thomas Schulz)
>> To: durwin at mgtsciences.com, h.reindl at thelounge.net,
> samba at lists.samba.org
>> Date: 02/25/2015 06:39 PM
>> Subject: Re: [Samba] Workgroup name too long
>> Sent by: samba-bounces at lists.samba.org
>>
>>>> From: Reindl Harald <h.reindl at thelounge.net>
>>>> To: samba at
2015 Feb 25
2
Workgroup name too long
I have searched for this and the solutions I found were for instances
where the workgroup name *was* too long. However, my workgroup name is
*not* too long. The spaces between PEGASUS and ^[ are part of the
message, I did not add them. If you count them there are 16 total
including ending ^[. I can't figure out where the spaces are coming from.
This is the same for every Samba
2015 Feb 25
2
Workgroup name too long
Am 25.02.2015 um 22:48 schrieb Miguel Medalha:
>> I have searched for this and the solutions I found were for instances
>> where the workgroup name *was* too long. However, my workgroup name is
>> *not* too long. The spaces between PEGASUS and ^[ are part of the
>> message, I did not add them. If you count them there are 16 total
>> including ending ^[. I
2018 Feb 05
5
nmbd error: workgroup name is too long
I found a similar thread in this mailing list from a few years ago, but it looks like there was never a clear resolution. (https://lists.samba.org/archive/samba/2015-February/189450.html).
I’m fairly frequently receiving the following error in my logs:
Feb 5 11:16:22 hal nmbd[19333]: [2018/02/05 11:16:22.889584, 0] ../source3/nmbd/nmbd_workgroupdb.c:57(name_to_unstring)
Feb 5 11:16:22 hal
2015 Feb 25
0
Workgroup name too long
samba-bounces at lists.samba.org wrote on 02/25/2015 02:51:28 PM:
> From: Reindl Harald <h.reindl at thelounge.net>
> To: samba at lists.samba.org
> Date: 02/25/2015 02:52 PM
> Subject: Re: [Samba] Workgroup name too long
> Sent by: samba-bounces at lists.samba.org
>
>
>
> Am 25.02.2015 um 22:48 schrieb Miguel Medalha:
> >> I have searched for this and
2018 Feb 06
0
nmbd error: workgroup name is too long
Open a random text editor.
Goto this line : workgroup = COOMBS
Press end and remove the spaces behind COOMBS, keep removing untill the line below it moves one up.
Then hit enter and restart samba.
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Kirk
> Coombs via samba
> Verzonden: maandag 5 februari 2018 20:47
2018 Feb 06
0
nmbd error: workgroup name is too long
Hi Kirk,
> I found a similar thread in this mailing list from a few years ago, but it looks like there was never a clear resolution. (https://lists.samba.org/archive/samba/2015-February/189450.html).
>
> I’m fairly frequently receiving the following error in my logs:
>
> Feb 5 11:16:22 hal nmbd[19333]: [2018/02/05 11:16:22.889584, 0]
2016 Dec 23
0
domainname is too long error
I noticed the following in system logs and on the server console.
The server is a PDC server in classic domain , DomainA. Samba
4.4.5. Trusts are setup with Domain A and C.
#:/var/adm# tail -100 messages
Dec 23 08:46:25 xxx nmbd[1784]: [ID 702911 daemon.error] [2016/12/23
08:46:25.095399, 0] ../source3/nmbd/nmbd_workgroupdb.c:56(name_to_unstring)
Dec 23 08:46:25 xxx nmbd[1784]: [ID
2018 Feb 07
3
nmbd error: workgroup name is too long
> On Feb 6, 2018, at 12:22 PM, Denis Cardon via samba <samba at lists.samba.org> wrote:
>
> what do you get if you increase you log level at 4 or 5 and restart your samba ?
> log level = 5
With log level = 5, the error always appears immediately after the following entry:
[2018/02/06 18:29:09.090976, 5]
2003 Apr 11
2
Samba / Windows workgroup master browser problem
I admit theres a LOT about the windows networking I dont understand -
and even though this may NOT be a SAMBA issue per se, I thought I'd post
it here.
Have a 400gb samba server thats been working well (am upgrading to
current patches today, btw).
I've got 3 Win2k workstations, on two subnets, that have drives mapped,
and connect every morning on startup just fine. All the machines
2000 Jun 12
1
ssh -R option
Dear list,
I'm relatively new to using ssh. I'm trying to use the -R option to set
up a forwarded port between two machines. Specifically I'd like to be
able to ssh to machineB from machineA and then have a port on machineB
that I can connect to machineA with. If my understanding is correct I'd
need a command like:
machineA> ssh -R 10000:machineA:23 machineB
This should
2010 Jan 27
2
Configuration of hosts
I'm probably doing something I'm not supposed to even try, but I'm trying
for "proof of concept" before physically setting up a distant network
because of logistical issues.
Anyway, I have tincd running as a service on two windows machines on the
same lan. I'm trying to establish a connection between those two computers
on the vpn ip's (10.20.30.1 and 10.20.40.1).
2008 Oct 09
1
rsync backup permissions
I had a quick look for an answer to what I'd presume is a common Q but
failed so wondering if somebody here would point me in the right
direction, please & thanks?!
I wish to use rsync to backup users' home dirs from machineA (Debian) to
machineB (Fedora). I have a script, say backup.sh, in my own home dir
and linked to from /etc/cron.daily and have set up the ssh keys so
2004 Sep 21
2
login from XP
Hello,
I'm having a problem logging in to the Samba domain from an XP machine. The machine is added to the domain but after reboot I can't login. I've done the signorseal registry hack but I'm still not able to login. The error I get when logging in is this:
"Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or
2000 Mar 13
2
Win2k Domain logons
Hi everyone. I just got a copy of Win2k in and have been messing with it.
Have a question, and have searched the archives for the answer, but didn't
find it. Can Win2k domain logon to a pre-3.0.0 samba server? Or di I
need to get TNG running? I can get NT4.0 boxes to authenticate and login
fine (Samba pre-3.0.0), but Win2k keeps complaining:
"The following error occurred validating
2004 Sep 14
1
Workgroup Browsing Issue and wins on 3.0.6
Hi,
I am having an issue browsing my work group, i have made the samba
server the master browser and it wins the elections. As far as i can
tell from the nmbd.logs it is also collecting hosts for the workgroup
but when you try to list the workgroup this error is recorded in the
messages log :
nss_wins[7417]: [2004/09/14 09:54:23, 0]
smbd/service.c:make_connection_snum(570)
nss_wins[7417]:
2005 Jun 11
3
[Homes] on two machines, possible?
Hi,
I have a smb pdc running which works quite well so far, and would like to
know if this feature is possible.
I have two locations, and I want all users to authenticate on Machine A.
Howver there are some users that are closer to machine B, and I would like
to be able to have the homes of those users on machine B rather than
machine A (they should authenticate on machine A anyway).
Is this
2003 Feb 07
2
Problem with rsync from one machine
I am not sure where to begin so I will be as verbose as I can to explain the
problem.
I have 3 servers. Their specs are:
Machine A: Redhat 7.1 kernel 2.4.9-34 openssh 3.1p1-5
Machine B: Redhat 7.3 kernel 2.4.9-31 openssh 3.1p1-5
Machine C: Debian Woody kernel 2.4.18-bf2.4 openssh 3.4p1 rsync 2.5.6
I am running an rsync over ssh from Machine C to Machine B with the
following:
rsync --verbose
2006 Sep 21
1
current master browser = UNKNOWN / failing WINS test #1 on 3.0.23c
I am having trouble with one of my samba PDC's. It does not recognize
itself as the domain master browser even though it is set to be so. I
can not add machines to this domain and I suspect this is why. Has
anybody seen this or know what causes it? Notice this:
DOMAIN_ALBANY(3) current master browser = ALBANY_PDC
DOMAIN_NYC(2) current master browser = NYC_PDC
2003 Aug 25
6
PDC + LDAP + W2K-SP4 Domain logon
Dear all,
___Setup:
- several wINDOWS 2000 workstations on SP4 (reg-patches applied, they
worked on 2.x-stable)
- Samba PDC (CVS 3.0.0rc2) (machine accounts added aswell as users in
unix & samba)
- OpenLDAP (2.1.12) <-- (Not really relevant since I tried without ldap
too, so no info about that from this point)
- Linux <HOSTNAME> 2.4.19 #1 Fri Jun 13 15:22:09 UTC 2003 i686