search for: rensburg

...itch/winbindd_util.c:get_domain_info(137) getting trusted domain list [2002/02/11 07:17:59, 1] libsmb/cliconnect.c:cli_establish_connection(867) failed tcon_X [2002/02/11 07:18:08, 1] nsswitch/winbindd_util.c:get_domain_info(137) getting trusted domain list Any ideas? Thank you, Jan van rensburg

I am having difficulty getting Netatalk to authenticate using NT Domain via Winbind. I have Samba successfully installed, and winbindd is working and running. (Tested via wbinfo) I have placed pam_winbind.so in the /usr/lib/security directory, and have installed netatalk with the --with-pam option, but I still cannot seem to get it working. Any help would be appreciated. John Helt Systems

Hi, I'm looking for a solution to access pop mails (sendmail in linux) securely. Most of the access would be from window clients (outlook express etc). Is there a way to encrypt the password (like ssh2) when authenticating with sendmail? Any info is greatly appereceiated. Thx. Regards, Wong.

...;npc"), inflect = TRUE, curvature = -1) grid.text(label, x = unit(6, "char"), y = unit(0.5, "npc"), just = "left", hjust = "center") #popViewport() upViewport() } Any suggestions whatsoever are most welcome. Kind regards, Stefan Janse van Rensburg [[alternative HTML version deleted]]

...epiuse-com -r GA -U w2kadmin Password: Joined domain US-EPIUSE-COM. And all looks well. However when I start nmbd and then winbindd I get the following error in the winbind log: "Could not connect to a dc for domain US-EPIUSE-COM". I'd really appreciate any help. Regards, Jan van Rensburg

Hi, I get these compilation problems with today's CVS on Solaris configured with winbind: /usr/local/bin/gcc -O -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -o nsswitch/winbind_nss_solaris nsswitch/winbind_nss_solaris.c nsswitch/winbind_nss_solaris.c:14: includes.h: No such file or directory In file included from nsswitch/winbind_nss_solaris.c:15: nsswitch/winbind_nss_config.h:30: config.h:

Using Wireshark I can see that ZoIPer always send a 160 byte payload. First few payloads contain 20 bytes of data (what I believe to be a mode 3 frame, ie first byte in 0x18 - 0x1F range), followed by 0x7B (21st byte), ie. 5 bit 0x0F terminator padded with 011. ... and then zeroes all the way up to 160 bytes. ... but then after a few payloads there are more following these 21 bytes ...