Thanks for the input, Corion. I am not opposed to writing a scraper, but since there is a multi-step manual process to generate the page(s) I'd prefer to investigate other options first. In addition, not all of the information that I want is presented on the pages so it would not be accessible.

I'll definitely put Wireshark in my back pocket. I have no prior experience using a packet sniffer so there would likely be a learning curve.

I've done some more reading on SNMP and I installed a few related modules from CPAN. I am starting to think that might be the most efficient route. The trick now is finding out what variables to request from the printer.

I've used Wireshark to avoid understanding overly convoluted web pages. It turned out to be far easier than I expected. It will help to filter on the IP address of the printer either in capturing transactions or in analyzing them. Once you know what requests are being made, you may find wget to be useful to test requests that the GUI application won't generate.

SNMP::NPAdmin is one of the several modules that I am investigating (and the most promising, by the way). Unfortunately the PPM installation failed and when I used the manual approach (nmake) it broke on the space in "Program Files"^*. I will pursue the installation issue when I return after the holidays. In the meantime, I think I will install Wireshark on my laptop and give it a test drive.

If anyone has any ideas about how to determine which MIB is used by this printer, I'd really appreciate it. My efforts have been unsuccessful thus far and I will need the variable names (or OIDs) to make calls to NPAdmin.

^*This is a huge pet peeve of mine, given Windows' finicky shell quoting and the difficulty of third party software to handle it correctly. Why "they" decided to put a space in the name of the root directory used for programs is beyond me.</rant>