Postscript is a language/file format that is designed for printers to use. So if you have a 'postscript' printer you should be able to feed the printer a postscript file and it will print it.
However most printers that are cheap and attatch through the USB are designed so that the hardware that would normally handle the postscript stuff is replaced by software that runs on your computer's CPU. Sort of like emulated hardware.
Like a 'winmodem' vs a 'real' modem. To make them cheaper they remove hardware and replace it with special software drivers.
That is why when you plug a printer directly into your computer you need special drivers to run it.
However when you share out a printer over the network you don't need those special hardware-replacing drivers.
What you need generally is something called a 'postscript printer description' file. These things have the 'ppd' extension. This is a file that contains the information needed by the operating system to know what sort of features and capabilities and any special stuff your printer can do. These things are the 'traditional' driver. It's just a text file though.
Now normally you can just select a generic printer description 'driver' and will work normally, but you miss out on features like color, nice resolutions, or being able to print on both sides of the paper and such things.
So that is the 'ppd' thingy.
The other part is that Windows uses a special network protocol for sharing out files and printers to other machines. The 'File and print services for Windows' stuff. This is often called 'smb' protocol for 'server messenger block'.
Now in order to gain compatability with windows file and print services in Linux you use a program called 'Samba', which should be installed by default or made easily aviable to you.
So _generally_ speaking you need samba to talk to the windows machines and you need a ppd file so that print stuff (usually something called cups) knows now to talk to the printer.
Now, unfortunately, this is one of the sucky things about Linux is that adding a printer is pretty difficult if it doesn't go well. There is realy no right way.
If that 'guinstall' program can be used to help setup network printers then I suppose you can use that.
How you go about setting up the printer can be different on different distros. I don't know much about it, unfortunately.
Sorry if I confused you.
That printer looks like a nice laserjet printer rather then the el-cheapo injet you get at walmart for a 100 bucks or so it's hardware is all there and you won't need special driver for that.
This guy got it to work with a directly connected printer with the ML-4500 gdi stuff. So try that. He said that the samsung drivers didn't work.
http://www.ubuntuforums.org/showthread.php?t=65111
Note with his stuff he had to install a couple other packages. Try like he did in the printer select GUI, but instead of selecting a local printer select a smb: printer.
It's kinda of a odd printer because it's not postscript printer.. It's a GDI printer which I've never ran into before. GDI is how the "Graphical Device Interface' from Windows. It's how the layout of the windows and stuff is done, and the printer can use that information directly. I think what that printer driver from samsung is designed to do is take postscript and transform it into something that the printer can use.
I am not sure how all that stuff works, unfortunately.
edit:
This guy used Fedora Core 5 with the ML-1710 driver to get it to work.
http://lists.freestandards.org/pipermail/printing-user-samsung/2005/001322.html
