On 2007-02-19 12:53, kanenas wrote:

Well, today was the first time i tried to print from my 64 bit standard install 10.2 to a windoze printer. tried both name and intranet ip for the windoze machine adress, nothing worked. tried a new install on harware and fired up the cups web admin tool, all showed kosher and recognized and installed....but... no print. no it is not pwords, AND, even if it were, it should not be. fired up vmware inside my running linucs, opened up a windoze xp virtual os, moved the file i wanted to the shared folder in my linucs, virtual windoze found the hp7350 on the other windoze computer right away and...printed the job very quickly. if my son finds out that i printed the job from vmware but my native linucs failed, there will be no end to the harassment. I know that there must be a logical explanation for this, but that's not the point. finding a printer in another computer in a dynamically allocated ip addressing scheme should be as simple as in windoze, simpler if possible. that clearly is not the case for my biostar amd64 mobo, 3800+ chip, 2 gb ram, 10.2 STANDARD installation plus kernel source and gcc to compile vmware. coupled with the other headaches already in place, this is coming really close to closing the lid on 10.2. if i wanted windoze behavior, i would have bought windoze... now i must decide if i want to standardize on 10.0 or 10.1... any suggestions? tia, d --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org

It IS more simple in linux, I have a cups server, with slp services, any (linux) machines will find the printers with zero config, they are just there after a new install. You may look at how your windows box share it's printers. If it does share for windows only, why are you surprised it works better with windows clients ? I can't believe you blame a linux system for having problem with something designed to NOT work with linux. Either we have people that are babbling about how hard it is to use a windows printer from linux, or has problems to use a linux printer from windows, and they all blame linux for it, even if cups is far more advanced and better then smb print, and is fully documented standard, free to implement for all, even for Microsoft. It was not long ago they refused to use TCP/IP , but had to give up in the end, and eventually joined the Internet, and now we can see Bill Gates on TV , taking credits for inventing the Internet :-/ IPP will be _THE_ standard even for windows, linux is just 10 years ahead as usual, and it takes long time for Microsoft to figure out how to implement a standard so it works their way, eg. the server must be windows based, or the clients refuse to use it. In Windows 2000 - XP at least, IPP works so well, so they don't tell you , or it by default. And printer services for UNIX is not selected by default, you must install it yourself. So the "ridiculocities of the day" is to believe that Windows is standard with anything else at Enterprise level. /birre --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org