search for: 50001

...n *nat -F COMMIT *mangle -F COMMIT *nat -X COMMIT *mangle -X COMMIT *nat -N test_POSTROUTING -I POSTROUTING -j test_POSTROUTING -N test_OUTPUT -I OUTPUT -j test_OUTPUT COMMIT *mangle -N test_POSTROUTING -I POSTROUTING -j test_POSTROUTING COMMIT *nat -I test_POSTROUTING -p udp -s 192.168.1.5 --sport 50001 -d 192.168.1.5 --dport 40001 -j SNAT --to 192.168.1.1:60007 -I test_POSTROUTING -p udp -s 192.168.1.5 --sport 40001 -d 192.168.1.5 --dport 50001 -j SNAT --to 10.76.50.70:60007 COMMIT *mangle -I test_POSTROUTING -p udp -s 192.168.1.5 --sport 40000 -d 192.168.1.5 --dport 50000 -j DSCP --set-dscp 46 C...

When there are multiple (two in my case) member servers on the same domain, should the following be the same values across all member servers? idmap config * : backend = tdb idmap config * : range = 50001-80000 << same value on all member servers idmap config SAMDOM : backend = rid << same value on all member servers idmap config SAMDOM : range = 10000-40000 << same value on all member servers As I read the wiki pages, I believe I am understanding this correctly? --...

...always moving forward. Sorry if I am misunderstanding you but, your saying invert them, listing the SAMDOM first followed by the "*"? like this example? idmap config SAMDOM : backend = rid idmap config SAMDOM : range = 10000-40000 idmap config * : backend = tdb idmap config * : range = 50001-80000 On Sun, Sep 23, 2018 at 2:27 PM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Sun, 23 Sep 2018 14:10:59 -0500 > Robert Wooden via samba <samba at lists.samba.org> wrote: > > > When there are multiple (two in my case) member servers on the same...

...; >>> After restoring the member server and re-running the improved "4-setup-samba4-MEMBER-wheezy.sh" script I am still having the same issue. W7 client still not allowed to access the member server. Administrator still has a uidNumber: getent passwd Administrator administrator:*:50001:50006::/home/samba/DTS***M/users/administrator:/bin/bash I have added a couple is test admin users (must have done it wrong.) Joined them to the 'Domain Admins' group and they cannot access the member server either. wbinfo -u output is: adminrob administrator dns-dtdc02 dns-dtdc01 adminnew...

...n group read-only domain controllers group policy creator owners ras and ias servers domain controllers enterprise admins domain computers cert publishers dnsupdateproxy domain admins domain guests schema admins domain users dnsadmins root at dtmbr01:~# getent passwd Administrator administrator:*:50001:50006::/home/samba/DT***RM/users/administratorSERNAME%:/bin/bash Say what, "administratorSERNAME%"? After running the 'generation one' script to create the member server, I have changed nothing except the suggestions that have been made on this mailing list. Attempting to gain...

...mber server and re-running the improved > "4-setup-samba4-MEMBER-wheezy.sh" script I am still having the same > issue. W7 client still not allowed to access the member server. > > Administrator still has a uidNumber: > > getent passwd Administrator > administrator:*:50001:50006::/home/samba/DTS***M/users/administrator:/bin/bash > > > I have added a couple is test admin users (must have done it wrong.) > Joined them to the 'Domain Admins' group and they cannot access the > member server either. > > wbinfo -u output is: > adminrob &gt...

...amba/%m.log #log level = 4 max log size = 50 security = ads password server = testdomain.TEST.COM encrypt passwords = yes domain master = no preferred master = no wins server = 130.208.165.55 dns proxy = no # idmap uid = 50001-550000 # idmap gid = 50001-550000 client ntlmv2 auth = yes #client use spnego = yes winbind separator = + winbind nested groups = Yes winbind enum users=yes winbind enum groups=yes template shell = /bin/false winbind use default...

...Trophy wrote: After restoring the member server and re-running the improved "4-setup-samba4-MEMBER-wheezy.sh" script I am still having the same issue. W7 client still not allowed to access the member server. Administrator still has a uidNumber: getent passwd Administrator administrator:*:50001:50006::/home/samba/DTS***M/users/administrator:/bin/bash I have added a couple is test admin users (must have done it wrong.) Joined them to the 'Domain Admins' group and they cannot access the member server either. wbinfo -u output is: adminrob administrator dns-dtdc02 dns-dtdc01 adminnew...

...vpn3 ACCEPT loc vpn3 ACCEPT net vpn3 ACCEPT vpn1 loc ACCEPT vpn3 loc ACCEPT vpn3 net ACCEPT vpn3 fw ACCEPT where tunnels entry is openvpn:50001 net 216.x.y.z vpn3 and similar policies on homefw, loc vpn4 ACCEPT fw vpn4 ACCEPT net vpn4 ACCEPT vpn4 loc ACCEPT vpn4 fw ACCEPT vpn4 net...

...randomForest to do some predictions. The test-harness for our code is pretty straightforward: library ('randomForest'); data202 <- read.csv ("random.csv", header=TRUE); x<- data202[1:50000,1:6]; y<- data202[1:50000,8]; y<- y[,drop=TRUE]; x2 <- data202[50001:60000,1:6]; y2 <- data202[50001:60000,8]; y2 <- y2[,drop=TRUE]; RFobject <- randomForest(x,y,na.action=na.roughfix); p <- predict (RFobject, x2); In this case, the CSV contains 10 columns, of which 1-6 are numeric in nature (day of week, week of month, etc...) and column 8 is...

...local/etc/rc.d/samba start I test the installation with: # net ads testjoin # wbinfo -u # wbinfo -g # pw user show -a And I can see all users with their uids set on the SFU PDC If I comment out the following lines from config file I still get the same problem: idmap backend = ad idmap uid = 50001 - 100000 idmap gid = 50001 - 100000 I hope you can help me resolve this issue. Please let me know if you need any additional info. Thanks, Vladimir Orlic # more /var/db/ports/samba3/options _OPTIONS_READ=samba-3.0.35,1 WITH_LDAP=true WITH_ADS=true WITHOUT_CUPS=true WITH_WINBIND=true WITH_ACL_S...

...change that, i did only some tests from windows. >> and i dont never set uid/gid to Administrator. >> >> -- Changed in the old script. >> >> but remember, you should NEVER set UID/GID for adminstrator, >because... >> >> Now administrator has uid 50001 ... >> and this should be 0 ( root ) >> This is why we also use the user mapping !root = >"DOMAINAdministrator" .... >> >> Always create a new user and add this one to the group >"Domain Admins" >> >> Also, i have set profile/uid...

...ion group read-only domain controllers group policy creator owners ras and ias servers domain controllers enterprise admins domain computers cert publishers dnsupdateproxy domain admins domain guests schema admins domain users dnsadmins root at dtmbr01:~# getent passwd Administrator administrator:*:50001:50006::/home/samba/DT***RM/users/administratorSERNAME%:/bin/bash Say what, "administratorSERNAME%"? After running the 'generation one' script to create the member server, I have changed nothing except the suggestions that have been made on this mailing list. Attempting to gain acc...

...b backend = ldapsam:ldaps://ldap.marlboro.edu ldap ssl = yes ldap suffix = dc=marlboro,dc=edu ldap user suffix = ou=people ldap admin dn = "cn=smbadmin,ou=People,dc=marlboro,dc=edu" ldap delete dn = no ldap filter = (|(&(objectclass=posixAccount)(uid=%u)(|(gidNumber=50001)(gidNumber=50003))(!(eduMarlboroNetworkAccess=false)))(&(objectclass=posixAccount)(uid=%u)(!(gidNumber=50001))(!(gidNumber=50003))(eduMarlboroNetworkAccess=true))) obey pam restrictions = yes I've tried setting SSL to no and the backend to "ldapsam:ldap://ldap.marlboro.edu",...

ok, seen it.. "administratorSERNAME%"? I'll change that, i did only some tests from windows. and i dont never set uid/gid to Administrator. -- Changed in the old script. but remember, you should NEVER set UID/GID for adminstrator, because... Now administrator has uid 50001 ... and this should be 0 ( root ) This is why we also use the user mapping !root = "DOMAIN\Administrator" .... Always create a new user and add this one to the group "Domain Admins" Also, i have set profile/uid/gid/nis for the Domain Administrator. And if you set a other...

...29.118 LEN=1300 TOS=0x00 PREC=0x00 TTL=127 ID=64571 DF PROTO=TCP SPT=10305 DPT=16224 WINDOW=64396 RES=0x00 ACK URGP=0 Sep 11 14:31:01 (none) kern.warn kernel: UNMARKED Packet: IN= OUT=vlan1 SRC=192.168.1.105 DST=24.176.137.55 LEN=1300 TOS=0x00 PREC=0x00 TTL=127 ID=64572 DF PROTO=TCP SPT=1983 DPT=50001 WINDOW=65320 RES=0x00 ACK URGP=0 Sep 11 14:31:01 (none) kern.warn kernel: UNMARKED Packet: IN= OUT=vlan1 SRC=192.168.1.105 DST=81.178.115.37 LEN=1300 TOS=0x00 PREC=0x00 TTL=127 ID=64573 DF PROTO=TCP SPT=1553 DPT=60546 WINDOW=65269 RES=0x00 ACK URGP=0 Sep 11 14:31:01 (none) kern.warn kernel: UNMAR...

After restoring the member server and re-running the improved "4-setup-samba4-MEMBER-wheezy.sh" script I am still having the same issue. W7 client still not allowed to access the member server. Administrator still has a uidNumber: getent passwd Administrator administrator:*:50001:50006::/home/samba/DTS***M/users/administrator:/bin/bash I have added a couple is test admin users (must have done it wrong.) Joined them to the 'Domain Admins' group and they cannot access the member server either. wbinfo -u output is: adminrob administrator dns-dtdc02 dns-dtdc01 adm...

...acls = yes acl compatibility = auto acl check permissions = yes acl map full control = yes dos filemode = yes # Use inherited ACLs for directories nt acl support = yes # inherit acls = yes # map acl inherit = yes # Config domain security ;idmap backend = ad ;idmap alloc config: range = 50001 - 100000 idmap uid = 50001 - 100000 idmap gid = 50001 - 100000 ;idmap config MYDOMAIN:default = yes ;idmap config MYDOMAIN:backend = ad ;idmap config MYDOMAIN:range = 10000 - 50000 ;idmap config MYDOMAIN:schema-mode = sfu hosts allow = 192.168.xxx., 192.168.xxx., 127., 10.8.xxx....

...ion group read-only domain controllers group policy creator owners ras and ias servers domain controllers enterprise admins domain computers cert publishers dnsupdateproxy domain admins domain guests schema admins domain users dnsadmins root at dtmbr01:~# getent passwd Administrator administrator:*:50001:50006::/home/samba/DT***RM/users/administratorSERNAME%:/bin/bash Say what, "administratorSERNAME%"? After running the 'generation one' script to create the member server, I have changed nothing except the suggestions that have been made on this mailing list. Attempting to gain acc...

...; ras and ias servers > domain controllers > enterprise admins > domain computers > cert publishers > dnsupdateproxy > domain admins > domain guests > schema admins > domain users > dnsadmins > > root at dtmbr01:~# getent passwd Administrator > administrator:*:50001:50006::/home/samba/DT***RM/users/administratorSERNAME%:/bin/bash > > > Say what, "administratorSERNAME%"? > > After running the 'generation one' script to create the member server, I > have changed nothing except the suggestions that have been made on this > m...