similar to: Domain MEmber Groups

I've posted about this problem several times but so far nothing has worked. Whenever I restart my samba servers the member server refuses to authenticate users. Sometimes is will only authenticate some users on some shares. Usually by fiddling with it I can eventually get it to work but I can't identify the solution so I can replicate it. Once it finally starts to work it works

I need help understanding what is happening and trouble shooting. I have two servers running Samba 2.3.3, one as a Domain Controller one as a Member Server. Both are running Ubuntu 8.10. smbd, nmbd and winbindd using the tdb back end are running on both. I have two shares on the member server and as far as I can tell they are identical. [Projects] works as expected but [Windows] always asks

I'm running out of things to check. I have two servers running Samba 2.3.3, one as a Domain Controller one as a Member Server. Both are running Ubuntu 8.10. smbd, nmbd and winbindd using the tdb back end are running on both. On the Member Server when I access the [Projects] share everything works as expected. When I access the [Windows] share I get prompted for a user name and password

I have having problems with what should be a fairly simple configuration. I have a PDC and a Member server accessed by several windows workstation. The PDC seem to be working fine, but every time I restart the network (usually for an update) all users have problems accessing the shares on the Member Server. Sometimes only a few share are accessible. sometime none. I have been able to get it

I have two servers running Samba, one as a Domain Controller one as a Member Server. Both are running Ubuntu 8.10 and running smbd, nmbd and winbindd using the tdb back end. I am having a problem understanding ID mapping. The mapping is not the same on both machines. On the Domain Controller > root at thelma:/etc/init.d# wbinfo -i 'ATLANTA\rob' > rob:*:1000:2003:Robert

I have two servers running Samba 2.3.3, one as a Domain Controller one as a Member Server. Both are running Ubuntu 8.10. smbd, nmbd and winbindd using the tdb back end are running on both. I am don't understand the results. As far as I can tell I have everything configured as it should be. The basic globals for the DC [global] workgroup = ATLANTA time server = Yes

I have a problem with a Member Server on Samba 3.0.28a running on Ubuntu Heady. Both systems were recently upgraded using Ubuntu's automated upgrade. It's also possible I broke a working configuration by accident. The shares on the Member server are visible on the XP clients and some users can authenticate properly. At least one user on one XP desktop cannot. The shares are visible

I've had a long running problem with two servers. One is the PDC of a NT style domain one is a Member Server. Sometimes when I restart the servers after maintenance some users lose connections to the Member Server. Sometimes it takes several hours for the problem to show up (today it took about 16 hours). I have been unable to determine the cause but I can usually solve it by restarting

I have a problem with accessing two share. Sigma works as expected one Windows always asks for a login name even though their smb.conf entries are the same; I even tried adding public to the Windows share with no success. [Sigma] Comment = Sigma Design Data path = /files/Lucretia/Sigma writeable = yes browseable = yes create mask = 0764 directory

I have two samba servers running Ubuntu 10.04 Samba Version 3.4.7 One server acts as domain controller and stores user ids in a .tdb Somehow I've ended up with a duplicate user name. On the Domain Controller # pdbedit -w -L|grep debbie debbie:1005:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:84DEC6FE3B018B0FB977EDDF5009742C:[U ]:LCT-4D4B086F: On the other Server running winbind I get #

On Sun, 24 Feb 2019 13:08:07 -0500 Robert Steinmetz <rob at steinmetznet.com> wrote: > Rowland Penny via samba wrote: > On Sat, 23 Feb 2019 19:55:03 -0500 > Robert Steinmetz via samba <samba at lists.samba.org> wrote: > > I ungraded my Linux Operating system from Ubuntu 16.04 LTS to 8.04 LTS > > Samba will not start after an upgrade to 18.04. My samba is running

I may have a clue. I have two servers running Samba 3.2.3, one as a Domain Controller one as a Member Server. Both are running Ubuntu 8.10. smbd, nmbd and winbindd using the tdb back end are running on both. On the Member Server when I access the [Projects] share everything works as expected. When I access the [Windows] share I get prompted for a user name and password but no combination

I ungraded my Linux Operating system from Ubuntu 16.04 LTS to 8.04 LTS Samba will not start after an upgrade to 18.04. My samba is running as an NT style member server server with smbd nmbd and winbindd all running. None of them will start. It worked this morning. This morning it was running Version 4.3.11-Ubuntu This afternoon after the upgrade it's Version 4.7.6-Ubuntu The logs in

Thanks for the response. I think  found and fixed the problem, but I need to do some more testing tomorrow. It seems that the "handle_name_resolve_order: WARNING: Ignoring invalid list value 'hosts'  for parameter 'name resolve order'" is not really a warning and it causes testparm to stop processing the smb.conf. I think that is also what caused the daemons to fail.

Use the command bellow to check if is Asterisk opening the port. netstat -nap | grep 4569 You need to see something like this output, otherwise your asterisk is not opening the port. udp 0 0 0.0.0.0:4569 0.0.0.0:* 10244/asterisk Att, H?lvio Junior dCAA - Digium Certified Asterisk Administrator SafeId - Gest?o de identidades e Acessos +55 41 | 9

I think you need to increase verbose output and search in /var/log/asterisk/full for any error message related to IAX2 registration or simil. 2017-06-05 17:12 GMT-03:00 <thelma at sys-concept.com>: > No, I don't think it is IP table issue, I've not upgraded dd-wrt for a > while and it was zoiper was working OK with my previous version of > asterisk. > > After upgrade

You can use tcpdump in your server to verify if it is receiving the packets. tcpdump -ni any port 4569 So you have more than one ip in the server? On 5 Jun 2017 9:13 pm, <thelma at sys-concept.com> wrote: > No, I don't think it is IP table issue, I've not upgraded dd-wrt for a > while and it was zoiper was working OK with my previous version of > asterisk. > >

Another might be to make sure iptables isn't blocking the connection. You can run iptables -L -n -v To see if its set to block any ports. On June 5, 2017 9:06:55 AM EDT, thelma at sys-concept.com wrote: >I'm getting: >netstat -a |grep 4569 >udp 0 0 0.0.0.0:4569 0.0.0.0:* > >Should I be getting localhost IP? > >Thelma > >On 06/05/2017

Top posting... While I don't really see any details that indicate this is the problem, systemd-resolved causes the packaged 18.04 samba to fail to start [at least in a full AD setup.] That's because system has a full DNS resolver, and Samba also has it's own DNS resolver. When they both try to start on the same port, the first running wins [systemd] and Samba exits. Since you're

Hi, I am performing GEV analysis on temperature/precipitation data and want to use the ks.boot function but I am unsure of how to implement it using the pgev distribution. For example: ks.test(data,pgev,shape,location,scale) ks.boot(data,(distribution parameters?),alternative="pgev",nboots=1000) Any advice? Apologies in advance if I have used the wrong email address. Regards, Louise