Remote Printing Stopped working

[Ron Murphy_1]

I have a workstation running HP-UX 10.20 and recently changed the IP address on this workstation as well as every PC and server on our network. The workstation is configured to print to a remote Lexmark C910 colour laserjet printer whose IP address also changed. When I run lpstat -t it shows the printer as disabled and Error 1 returned. At the end of the output it shows unknown host SENTINEL (wich is the name of one of the Windows servers and the print server). How can I go about having making the necessary changes to th printer to allow printing to resume? It worked fine before the IP change.

[xyko_1]

Hi Ron

this is a Linux forum and your environment is HP-UX and windows. But let's try to help you.

Did you reconfigured the print queue for the new ip of the remote print server ? If the print queue was configured with host name, not ip adress, I suggest you to delete and recriate it. I'm not a HP-UX user but I guess if the system doesn't save any information using ip adress when the print queue is created and it's wrong now, after the ips where canged.

regards,
Xyko

[Trond Haugen]

HP-UX 10.20 has been out of support for more than a year and I would suggest upgrading.

Your description ofthe problem sounds like a hostname problem. does 'nslookup sentinel' return the correct hostname?
If not /etc/hosts or DNS needs to be corrected. If DNS is used and correct you should check /etc/resolve.conf and /etc/nsswitch.conf.

Regards,
Trond

[Ron Murphy_1]

Sorry about that. I thought I posted in HP-UX. I checked the hosts file and there is an entry there for SENTINEL. nslookup does not retrieve the host name and resolve.conf and nsswitch.conf do not exist. If you have any ideas I'd appreciate it but I'm going to repost in HP-UX. Thanks for your help.

[Trond Haugen]

Apreciation can also be shown by giving points.
No resolv.conf indicates that DNS isn't used. BUT I made a typo (the e) in my previous response so please re-check.
If you fint the file to be there you need fallback to the hostfile and can create nsswitch.conf with one line:
hosts: dns [NOTFOUND=continue] files

Regards,
Trond

[Ron Murphy_1]

Sorry about that. Points submitted. I checked for the resolv.conf file and it does not exist. So if DNS is not used shouldn't it read the hosts file entries. The only two entries it seems to resolve in their are the twor UNIX workstations. When I use nslookup with the other entries, which are all windows servers, it responds with Looking up FILES, no address information is available for 'hostname'. Any idea how to resolve this or why it would have worked previous to the IP sitch?

[doug mielke · Accepted solution]

It could be an issue with the /etc/hosts file itself.

You could add the sentinal entry before the entries for the 2 workstations that do resolve correctly to see.

remember that the file is read sequentialy, and only the first entry of duplicates will be read.

[Trond Haugen]

Moving the line is a good advise.
I would suggest doing it by re-typing it. There COULD be some non-visable caracters in the line that would also breake the lokup.
Do you know how the IPaddresses in the host-file was altered? Could it be that some script put some illegal characters in there?

Regards,
Trond

[Ron Murphy_1]

Hi guys. Thanks for your assistance. I typed the entry at the top of the hosts file and now it is resolving. The old entry was remmed out with the '#' symbol, as I'm used to seeing it. Should there be a space after this? Maybe it was still reading this entry and not going to the valid one. Anyway, I'll make the changes for the other host entries as well. Thanks again.

[doug mielke]

the space shouldn't matter after a # entry.

I'd look for some corruption or bad charaters in one of the entries prior to the old 'sentinal' location.

You can use od or hd to read the files for non prtable charaters, or, if the hosts file is short, just type a new one.

[Ron Murphy_1]

I'll give that a try. Thanks again for helping resolve the problem.

[Ron Murphy_1]

Closing thread as problem solved from previous posts.