search for: qzhou

...168.88.166) from any machine in my server lan, 192.168.88.0/24, all packets timed out, and nothing received by the client. Any ideas? Thanks! Regards, Quan Zhou +------------------------+ |pub [expires 2015-09-05]| |44D2 0307 1643 E80F 2E31| |F081 FAFA 6643 7F9F D46F| +------------------------+ |qzhou at live.de | |https://keybase.io/qzhou| +------------------------+ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: Message signed with OpenPGP using GPGMail URL: <http://www.tinc-vp...

...nc connect can be established, but the tun1 on tinc server(host:nrj1) didn?t get IP address. Could be anything I missed in my configurations? Regards, Quan Zhou +------------------------+ |pub [expires 2015-09-05]| |44D2 0307 1643 E80F 2E31| |F081 FAFA 6643 7F9F D46F| +------------------------+ |qzhou at live.de | |https://keybase.io/qzhou| +------------------------+ Exhibit 1(server confs, nrj1): ----------------------------------------------------------------------- root at nrj1: ~# ifconfig tun1 tun1 Link encap:Ethernet HWaddr 8e:10:69:58:48:29 inet6 addr: fe80::8c1...

I know there is the command "wbinfo -t". But when it says that "could not check secret", how do I know it's the secret is bad, or something else wrong, like winbind went crazy maybe? Also, sometimes I saw problems like "wbinfo -t" just says "secret is bad", when all the daemons were running. It sure was good at some point before. So my

When I change file property - security from Windows, I can see both from packet sniffer and Samba code, that there are 4 types of "security information": Owner ID Reference Primary Group ID Reference Discretionary ACL Reference System ACL Reference So if I want to change the primary group name on a file, by right click on the file->property->security->advanced->select

I am using samba 2.2.5, and the following patch Jerry outlined in his 2.2.7 release notes. I tested it against a W2k server (in mixed mode) which had a simple one char admin password, worked fine. Recently I found that if the password is longer than 1 char, using "smbpasswd -j dom -r svr -U admin", and then input password, I get NT_STATUS_LOGON_FAILURE. If I remove the patch,

Hello, all, I can not easily find an answer to this question: why do we need samba 3.0 to join an ADS, if samba 2.x can join the ADS domain just as well, even though the PDC is in native mode? What's the benefit for samba 3.0 to be a member of ADS? What restrictions I have if joining samba 2.x to the domain as an NT4 server? I bet people on this list should know better than me. Can

I need help to resolve this issue. I saw that Andrew put a patch by Antti to enable users without full admin access to join samba into an AD domain. I am playing with it and always get "Insufficient access". Using the same user, I can join a Windows box into the domain just fine. The user is a member of "domain users", but not "domain admins". I can use a

I can't make it work although both sign&seal and restrictanonymous are set to 0. My setup is: w2k sp2 as PDC, w2k sp3 as client, samba 3.0a21 joined into the PDC domain as an ADS member. The scenario is, from the w2k sp3 client, connect to a share hosted by samba, create a file, then use property->security->add tab to add an ACE, then the browsing user/group windows appears