Note that I am using static address and not DHCP for my xp box since it is the gateway system.

Ok, here goes, The URI I did for IPP is: IPP://0.0.0.0/printers/hprint where my ip address is for the xp box and the hprint is name of the printer for sharing in xp box.

URI for Samba:smb://MSHOME/usernameassword@0.0.0.0/hprint where the ip address is for xp box and MSHOME is name of the workgroup in xp box The username and password is from linux box.

URI for LPD:lpd://0.0.0.0/hprint, ip address is for xp box also.

I got most of the info for all this from: http://www.swerdna.net.au/linhowtosambaprint.html


-bhert

I don't see anything wrong with any of the formats you have tried. So, I'm running out of ideas. I did look at the cups documentation, and saw the following:

This is for HP deskjet printers, and I found it by doing a search in the cups admin area for URI.

At this point, we think we have the correct driver installed in linux, we know the printer works when plugged into the linux system.

It appears, the print files go to XP, but don't print.

It might be worth some time if you go to M$ support ( their knowledge base ) and look for any fixes for problems like this. I'm not at all sure we have a linux/samba/cups problem.

You could also try one of the other URI's, although I don't think that is the problem.

Been a while since I did anything with XP. Can you see the print file arrive at the print queue in XP?

Have you had a look at this thread?

http://forums.suselinuxsupport.de/in...howtopic=41382

I looked at the site you provided and used yast to configure the printer and tested samba and it did connect to the xp printer.

I then proceeded to print a test page and looked at the xp's queue and the same thing happened. The file name, owner, ipaddress, file size showed right except for the page size which was N/A again of course. I have to turn off the printer to delete the file stuck in the job queue. So no go.

As a test, I had my mom bring her xp laptop and configured it so her box can print remotely to the other xp box connected to the printer and it printed beautifully.

I don't know how the xp to xp printing works but linux to xp printing does not?

I don't know if the fault lies at the xp print server

I am pretty much out of ideas too. Sucks big time.


-bhert

I agree. I'm about out of ideas also. I'll do some more looking around, and post back if I can find something.

One thought, what flavour is your XP system? Home, or Pro?

Here are some links I found. Not sure they tell us much we don't know, but they are worth a look.

http://www.idevelopment.info/data/Un...LinuxSMB.shtml

http://www.faqs.org/docs/Linux-mini/....html#packages

I know these are different distros, but printing is the same beyond the gui's different distros provide. The Debain one has some nice stuff covering samba as well as packages you must have.

Did you create an account on XP as the Red-Hat example shows?

One more How-to...

http://www.linux.org/docs/ldp/howto/...o_windows.html

Have a look here, if all else fails. It may help define the problem.

http://www.linux.org/docs/ldp/howto/...eshooting.html

Hey Camorri, Sorry for taking so long to respond. I was out town for a few days. Thanks for the links you posted here. I tried all these things and it didn't work. As a last ditch effort, I decided to try something else. I reinstalled cups and then tried samba and magically, it worked. I don't know how. The config file in cups must have been wrong or something. No matter, I am glad that it's working perfectly now. The problem I had about the page N/A in the window queue before now shows page 1 and the fact that it's printing beautifully!

Thanks again for sticking with me through the problem

In case you were wondering, I am using XP home.


-bhert

Now this is interesting, I found this thread:
http://www.linuxquestions.org/linux/...d_from_Windows

I wonder if it would have worked for my printer also. It's mainly for hp printers with exactly the same problem. It has to do with HP and the shockwave file monitoring the printer port. I will keep that info as it may come in handy sometime in the future.

-bhert

Thank-you for posting the information on the windoze side.

I'm happy you had success.

Camorri, My significant other rebooted windoze cause of the slowdown and then I tried to print from my suse box, and how about that? The same old "won't print" happened again.

I then figured the link I added 2 posts above this about HP printer port problem might be put to good use.

I know it was made for suse 10.0 and a different HP printer than mine.

The file names to be changed and deleted were different with my HP printer files but it can be easily figured out. I messed with the registry and the system files in windoze and after that, it seemed to have worked with no problems.

I then rebooted both machines to make sure that it's not playing with me.

Yay, printing still works fine for me.

The link above should be made available to anyone that has problems getting HP printers to work remotely, maybe make it a sticky.

Apparently HP printers are popular and used by most. Should the mods be notified to make the link a sticky to make people that have HP printers lives easier? What do you think?

-bhert

Sounds like that would be a good idea. So more people can find this thread we ca tag it. That helps with search engine on the board.