search for: officeserv

Wine 0.9.53, FreeBSD 6.3-PRERELEASE. When I installed Samsung OfficeServ Manager (OSM) for Samsung PBX, it works for OSM7200, but does not works for OSM 500. When I try to run it appear small error window with 'Run-time error 3633' and program closes. OSM ver. 3.17 at 2007.10.04. These lines appear in log file: fixme:spoolsv:serv_main (0 0x0) err:iphlpapi:g...

Samsung OfficeServ for OS500 PBX cannot run - 'Run-time error 3633' err:iphlpapi:getRouteTable Received unsupported sockaddr family 0x12 err:iphlpapi:getRouteTable Unexpected address type 0x10 err:iphlpapi:getRouteTable Unexpected address type 0x20 err:iphlpapi:getRouteTable Received unsupported sockaddr fam...

...roller: Windows 2003 SP1 The machine's joined to the domain and users are authenticating via SSH (/etc/nsswitch.conf is configured correctly) and to any of the non-[homes] shares they're entitled to access (ie shares that are specifically defined in smb.conf.) Proof of this working setup: officeserver:/home# wbinfo -t checking the trust secret via RPC calls succeeded officeserver:/home# wbinfo -u | head -2 adam administrator officeserver:/home# wbinfo -g | head -2 BUILTIN+system operators BUILTIN+replicators officeserver:/home# id tullettj uid=15003(tullettj) gid=15001(domain users) groups=150...

http://shorewall.net/pub/shorewall/Beta ftp://shorewall.net/pub/shorewall/Beta Problems Corrected since version 1.4.6: 1) Corrected problem in 1.4.6 where the MANGLE_ENABLED variable was being tested before it was set. 2) Corrected handling of MAC addresses in the SOURCE column of the tcrules file. Previously, these addresses resulted in an invalid iptables command. 3) The

Hi, We are trying to port over a PABX to our network. Both PRI's seem to be live however, whenever someone dials out from the PABX Asterisk happens to report : -- Extension '' in context 'samsungincoming' from '736327438' does not exist. Rejecting call on channel 0/31, span 2 If crc4 is turned off, it reports a yellow alarm. Any suggestions? Regards, Sahil

I just cranked up Samba 2.0.6 on NetBSD-sun3 1.4. The clients are Windows 98 (non-SE). I have had experience with earlier versions of Samba, so I was able to get 2.0.6 up and running without great difficulty. I exported a directory and was able to mount it on my Win98 machines fine. Using Explorer, everything looked like I expected it to: files were listed with their full names and I was able