error msg

[Ned Dixon]

I am trying to add an Oce plotter (from our windows print server) to our unix. From windows, I can ping and even print test sheets. However, I cannot get it added in SAM. When I try to add - I get an error msg (will attach to this thread)
Any help would be GREATLY appreciated!! Thank you in advance.

[Ned Dixon]

By the way - I am VERY new to Unix - so please be patient and explain in "moron terms"

-Thanks!

[Court Campbell]

Before looking into that issue do you have print services for unix installed on the windows print server?

[A. Clay Stephenson]

Well, you could look for and apply the latest SAM and lp patches but the smater approach would be to attempt to add the printer manually using lpadmin; you then have a much more direct link to any underlying problems. I honestly can't remember the last time I used SAM to add a printer; it's just too klunky for me.

[Ned Dixon]

Do you mean the LPR printing protocol?

[Rita C Workman]

The error is pretty self explanatory.....the name is too long.
Can you do an nslookup for a shorter (alias) version of the name ?

You could try setting it up in your hostfile and putting something like pthfs04 as the alias. Then if your nsswitch.conf goes to FILES first and DNS second it would be able to resolve to a shorter name.

Just a quick thought,
Rita

[Ned Dixon]

Clay and Rite - you make it sound so easy!! haha However, for a Unix idiot like myself, it sorta sounds like greek to me....sorry! Any chance you can break it down to simple terms?
Thanks!!! I really do appreciate your help!

[Court Campbell]

Ned,

Unless you have print services for unix setup on the windows print server i do not see how you are ever going to be able to forward requests from unix to it.

[Ned Dixon]

I have the LPR printing protocol set up. Is that not what I need? If not, can you point to what I may need to setup?

[Court Campbell]

Ned,

Unless you have print services for unix setup on the windows print server i do not see how you are ever going to be able to forward requests from unix to it. I realize you got an error in sam, but by knowing if you have unix print services setup on the windows box is important to know otherwise adding the remote print queue on your hp-ux box will be in vain.

[Court Campbell]

look at this link and let me know if you have done these steps on the windows server.
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/printservicesunix.mspx

[Ned Dixon]

As it turns out - I do have Print Services for Unix installed on my print server...

[OldSchool]

1. Have the system admin add the IP of the Oce in DNS or /etc/hosts w/ an alias, something like tds1.

2. If I remember correctly, Oce provides the Winders box and you can't do any config on it, just run there print / copy mgt package, correct?

3. Alternate to (1) is supply the IP instead of the printer name (I seem to recall thats what I did)

4. Routing / netmask must be correct on the Oce

Not sure what else might be involved, as I only set up 2 similar models about 4 years ago

[Court Campbell]

Sorry I am not familiar with Oce. I guess in the end I would skip pointing the windows server and pint straight to the printer. It more than likely has a lpd on it. As mentioned add a host entry in /etc/hosts, and then add the printer through SAM using the hostname you used in the /etc/hosts file and the print queue name that is on the printer. A lot of the newer printers have a web interface in which you can find this info. Sorry if I confused you earlier. I sometimes make things more complex than they need be. I am my own worst enenmy.

[Court Campbell]

Sorry I am not familiar with Oce. I guess in the end I would skip pointing the windows server and pint straight to the printer. It more than likely has a lpd on it. As mentioned add a host entry in /etc/hosts, and then add the printer through SAM using the hostname you used in the /etc/hosts file and the print queue name that is on the printer. A lot of the newer printers have a web interface in which you can find this info. Sorry if I confused you earlier. I sometimes make things more complex than they need be. I am my own worst enemy.

[Ned Dixon]

Court,
I do appreciate your help - as with everyone that replied to this thread. I am going to go see what I can do with our network admin to work out the long name issue and see if that helps.
Again - thanks to you and everyone else here! If nothing else - I've learned a few things today!
Best Regards,
Ned

[OldSchool]

In my earlier response, i mentioned short name / alias for the oce.

what i was referring to was to create a short alias in either dns or /etc/hosts for the windows controller.

IIRC, this wasn't really too tough an install. Oce tech support seemed to be pretty good when I needed it, but thats been a few years ago now. Unfortunately, I don't have access to any docs for this now, but I seem to remember that it was set up as a simple lpr device.

Can you access it properly from a PC running Print Exec LT?

[Ned Dixon]

I've actually got it resolved and am able to print from Unix now to the Oce. Turns out it was a name issue. From what I could tell - the name of the printer on our print server had a space in the name. Once I removed that space - it seemed to set up no prblem within SAM. That's not to say that maybe our network admin didn't do something behind the scenes that helped - but as far as I know - that's all it was. I do very much appreciate your time and attention to helping me out!!!!! From now on, when I have a Unix issue, this forum is going to be my first stop!! I'm very impressed with all the help everyone offered and how quickly everyone responded!!!!
Again - thank you!!

[OldSchool]

yes...unqouted spaces would be an issue.

the problem is that much of sam is built around shell scripts and spaces are / will be treated as delimiters between arguments. that explains the "extraneous arguments" ignored.