HP Gate and DNS error
Andrew
HP Gateway 2.10a were not printing. They had been working fine for months.
I was getting the following error message on the server console "HPGATE Ill
formed IP address or invalid DNS name.". I unloaded and reloaded
everything an still nothing. I finally deleted all the printers and
recreated them using the IP ADDRESS and not the DNS NAME and they all
started working again. For some reason the latest gateway or something on
the Novell server is unable to resolve DNS names with regard to the HP
Gateway. Oh, all printers work fine with NT print servers using DNS names
and printers are on the latest 8.32 firmware.
Timothy Biles
similar issues. My printers will work fine for a while then they do
exactly what you are describing. I've been seeing lots of other issues
as well like my server hanging and abends related to NDPS. As of today,
I have applied all the available patches (NDP2XP5 and PHPDS2X2), as well
as the DPLSV386 from tech support). I've also applied all post SP6a
patches and a filesys.nlm patch, and turned off client side file caching
(which may have been causing my hangs).
They suggested I use IP on my printer agents too, which I'm not exactly
in favor of doing, because I prefer to use the more descriptive DNS
name, and if the IP changes, I don't need to go in and change my printer
agent every time.
Something interesting I saw the last time this happened. I went into
the NDPS Manager. All my HP printer agents were reading "needs
attention". Stoping and starting the agent did nothing. 3 printer
agents (non-hp printers) are using LPR through the Novell gateway, and
they were fine (also using DNS names). We could ping dns names from the
console, so DNS name resolution on the server was still working. We
tried unloading the manager and broker (which abended my server), so we
had to reboot.
I changed one of my HP printers back to using an IP address so I hope to
make a comparison the next time this problem happens. One of the new
features of the 2.10a gateway was the ability to use DNS names. I have
a hunch, though I can't prove it, that there is some glitch with the HP
Gateway and DNS resolution.
Like you, NDPS worked fine for about 6 months on SP5a. I started having
hanging problems at the end of January, and started patching, and things
are not looking good. I was slowly adding more printers over time.
Once I got past about 10, I starting having issues. I have changed the
default gateway settings to handle more threads and processes as well.
It helps performance, but stability is still an issue.
Comments/suggestions? If you find out anything, I'd sure appreciate
hearing from you.
--
Timothy M. Biles voice:(218) 726-6959
ITSS - Systems Administrator fax:(218) 726-7674
University of MN-Duluth
MWAH 147
10 University Drive e-mail: tbiles @ d.umn.edu
Duluth, MN 55812
Hamish
Make sure that the sys:etc\hosts file on the server has an entry for itself, and
that the IP address is correct.
--
Hamish Speirs
NSC Sysop.
Timothy Biles
this. It didn't make any difference.
In the past, rebooting has helped for a while, but I can't be rebooting
every time this service breaks. I changed them to IP addresses for now,
until I can figure out what is wrong. I know name resolution works,
because I can ping from the console the same printer address that the
manager reports as "Needs Attention". Non-HP Gateway printers continue
to work fine with DNS names.
Strange...
--
Hamish
Yep - server has hosts/dns entry for itself. Came accross the following tids looking
at a similar problem for some else:
http://support.novell.com/cgi-bin/search/tidfinder.cgi?10028008
http://support.novell.com/cgi-bin/search/tidfinder.cgi?10018056