Sco release 5 windows share printer

[TheCrick]

Hy

First im a total newb in unix server
We have a server here for work under sco openserver release 5

This server print on a windows lpt1 share printer under windows 98.

I have to change all the machine to a domain under windows xp
So i change this windows 98 machine, keep the same ip and name of the computer and the name of the share.

But the Sco can't print anymore.
With some test, i found that the workgroup is the probleme.
If i put the machine in the same workgroup the old machine was, everything is working

But i cant stay thing like that because i have to put all my machine under a domain.

Like i said, im a total newb in Unix server and i need some help

Thx

TheCrick

 

[motoslide]

On the Windows box, create a local user with printer access (doesn't have to be member of Administrators group). Give that user a password and prevent automatic password expiration. For example, create user "unixprint" with password of "unixprint".
On the SCO OpenServer box, try this command:

/usr/vision/bin/visionfs print //{pcname}/{sharename} --user unixprint --password unixprint

(Do not include the {} brackets, and replace those values with the correct PCname and Sharename)

You should get a status reply showing any active jobs. If this works, you will need to modify the credentials passed by the VisionFS print command. This could be in one of these places:
/usr/spool/lp/admins/lp/interfaces/{printername}
or
/usr/vision/etc/vfsprinters

In the first case, the "visionfs print //pcname/sharename" might be near the end of the printer's interface script. In the second case, vfsprinters is a parameter file for one or more printers.

"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[stanhubble]

what are you using on the sco system to "print" to the windows shares? if it is visionfs then motoslide's suggestion should stear you in the right direction. if it is samba then the commands will be based on smbclient.

But from the sound of it, it is a problem with the browse master of the domain/workgroup (or lack there of).

Try using the printservers ip instead of the netbios name,
and/or add the sco system to the domain.