print server

Brian K. White brian at aljex.com
Mon Oct 10 14:33:59 PDT 2005


----- Original Message ----- 
From: "Don Coleman" <dcoleman at dgcreact.com>
Cc: "filepro-list1" <filepro-list at celestial.com>
Sent: Monday, October 10, 2005 2:22 PM
Subject: Re: print server


> Kenneth Brody wrote:
>
>>Quoting gliderman.one (Mon, 10 Oct 2005 13:18:32 -0400):
>>
>>
>>>A customer has installed a print server, Trendnet  TE-100 and installed
>>>a tcp/ip address on each Windows computer.
>>>
>>>what do we tell filePro in order to print from each computer to the
>>>printer?
>>>
>>
>>The same thing that you tell filePro for any other network printer:
>>
>>    win:printername
>>
>>where "printername" is the name by which Windows knows the printer.
>>
>>--
>>KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
>>http://www.hvcomputer.com
>>http://www.fileProPlus.com
>>_______________________________________________
>>Filepro-list mailing list
>>Filepro-list at lists.celestial.com
>>http://mailman.celestial.com/mailman/listinfo/filepro-list
>>
>>
>>
>>
>
> When using the WIN: syntax for a printer attached to USB001 which is 
> shared on a network do you use the full Windows printer name (usually 
> rather long with imbedded spaces) or the Windows share name?  TYIA.

"Yes."

whichever you want.

win:local pc windows printer name
works if the printer has been installed in windows and shows up in "printers 
& faxes"

\\server\share
works if you know the server computer name and the share name regardless if 
that same printer is installed in your local windows or not

A few advantages to the win: syntax:
you can put "win:laser" in fp and then any printer you name "laser" becomes 
your filepro printer
it might start out as a network printer, later be switched to some other 
network printer, to a local usb printer, etc...
IT/ISP guys don't have to know how filepro works, they can make changes to 
the network all they like, like changing the servers name during a swap-out 
or upgrade, changing the share name during a replacement, etc... they'll 
know enough to get things working again in windows after any changes, but 
won't know that what they did broke fp, or how to fix it. This way, they 
don't have to. Merely naming the printer o the client side fixes it again.

Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro  BBx    Linux  SCO  FreeBSD    #callahans  Satriani  Filk!



More information about the Filepro-list mailing list