search for: schaubroeck

...mge-evolution] driver = newhidups port = auto vendorid = 0463 productid = ffff desc = "MGE evolution ups,in de installatieruimte ter test" Did anyone experience this before or has some advice? Thanks, Stijn Gruwier **** DISCLAIMER **** http://www.schaubroeck.be/maildisclaimer.htm -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20070613/5531be80/attachment.htm

...g samba 3.2.14-40 and on the windows server 2008, the SP2 is installed. The windowsservers name is WIN2008 and I can ping to WIN2008 from the linux server, so the DNS is correct. Can anyone tell me what the problem can be, or what I can do to resolv this problem? -- Kind regards, Thomas Six Schaubroeck informatica Tel 0032 9 389 0526 **** DISCLAIMER **** http://www.schaubroeck.be/maildisclaimer.htm

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 5105 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20020509/3678dd89/attachment.gif

I have problems installing the latest release of Samba on Caldera (SCO) Openserver 5.0.6 I have downloaded the source and ran "./configure" fine. I get an error " line 664: Syntax error " when I run "make". If I run " ./configure --with-winbind", then run "make", I get the error "Compiling smbd/server.c include/includes.h, line 885:error:

Is there a way to pass along the document name when printing to a shared Windows printer from Unix with smbclient. There doesn't seem to be any arg to smbclient to send a document name to Windows. All documents printed with smbclient are named "Remote downlevel document". This is not very nice to say the least.

We have a strange problem with some printers on a Windows XP host: When we print a testpage from the linux server (RedHat 8), there's no problem. But when we configure the printer on our Windows XP client and we want to print a testpage: nothing happens and we get the "windows troubleshooter". When we print a Word document to the same printer on the same Windows XP client, the