A good choice, from my point of view.
Hm, queues are typically selected by a name, not by a number. Might it be that that application always prints to “the default printer”?
[QUOTE=momayet10;10652]Now i have that que configured via the print server and i am able to print a test page. but cant print from the app
It seems the job goes to the printer but nothing prints. the printer doesnt even make a noise its stays in standby.[/QUOTE]
That’s a good starting point for debugging this.
Just for a common understanding: The application on the Linux host prints to a printer queue - once the job is spooled to the queue, the job’s done from the application’s point of view.
The print queue processor may have to convert the print job’s content to the proper format.
Then the processed content is spooled to the printer - from Linux’ point of view, that’s the print server box, not the printer itself. That print server then will spool (or directly feed) the job to the actual printer.
As the test page prints fine, we can cut short 
The scenario I see is that either the jobs are still queued for some reason, or the jobs failed for a post-processing reason.
Are you familiar with CUPS administration through the browser interface? If you have a browser on the Linux server machine, go to “http://127.0.0.1:631” to connect to the CUPS server - from there, you can click to the printer(s) and see what jobs are pending/finished for which queue.
When you need to access via a remote browser, things may be more complicated since AFAIK the default CUPS setup is limiting admin access to the local host and therefore would need modification.
Another way (rather than browser access) to see at least all currently queued jobs would be to invoke “lpq -a” on the server. If you see all your jobs there, then we’ll have to check why the jobs aren’t spooled to the printer (server). Although I doubt that: since the test page prints fine queuing should work, too.
When it comes to printing errors (when no waiting jobs could be found, then the jobs seem to have aborted for some error), debugging will include checking the log & error files in /var/log/cups - i.e. using “more”, you’d have to give some feedback on how you get along.
[QUOTE=momayet10;10652]Before all of this i had the printer connected to a xp pc and the que configured to the xp machine. All works well with xp.
Just cant seem to understand y it doesnt work as well with windows 7 i would have thought all u neeeded to do was change the pc name in the printers url
I have followed guides, changed firewall settings, and network settings, just no luck
I hope myy explanation above helps[/QUOTE]
Yes, it seems I got a pretty good idea of what you’re trying to do. I’ve avoided printing via Windows systems for obvious reasons, so I cannot tell why the switch from XP to Win7 gave you so much trouble. But OTOH, as you now have a print server, let’s rather get that working 
With regards,
Jens