New network printer: how to NET USE and install methods 1

[dbMark]

I'm installing my first network printer in the hp4000 family. I plugged it into the nearest switch and it works. It picked up an IP address from DHCP, I installed it on my Windows Millenium and printed from it. Since I have a DHCP network, the DHCP server assigned it a random address within that scope's range. I plan to reserve an IP address that has been specifically excluded from the randomly assigned range so that it will always have the same IP address.

From what I've been able been able to see, the printer was assigned a somewhat meaningless network device name: "NPI" plus last 3 bytes of MAC address. I will change that to a more meaningful name. Which way is better to have other computers install it - by IP address or by name? I mean, what method does the Install printer process use, its name or address? From what I can tell, it doesn't even ask which. What would cause me to have to reinstall the printer - changing IP, changing host name, or either?

I know about the usual IP and mask, but why or to what should I assign the Syslog Server (LG), and Default Gateway (which it picks up from the DHCP server)? (I use NAT internally so I don't think I can log on to it from home...)

This is my most urgent question: So far I have been unable to connect to it by NET USE. I have some older DOS programs where we call NET USE to assign a shared printer to LPT2. I've tried many combinations but simply cannot get NET USE to make a connection. How can I do that?

Does JetAdmin 7.5 work only on the Windows NT/2000/XP/2003 family? I'm still using Windows Millenium, is there any way to run something like it on WinMe?

Helpfult hints:
thread697-791030 - ARP can remotely assign printer an IP excluded from DHCP range
thread697-643331 - Adjust CFG TCP/IP=YES, BOOTP=NO settings in printer's Control Panel menus so IP address can be manually assigned if desired

 

[bluegroper]

I think the dos command NET USE is strictly for connecting to windows shared resources ("shares"). So install the networked printer on your first windows computer, and then tell that computer to share the printer. Give it a share name.
Now you can go to your second computer and NET USE \\whatever\printer. I know its not an ideal solution, because it forces your first computer to be tied up acting as an unnecessary print server, but it works.
HTH
- BG

 

[dbMark]

Yes, I knew about that, since that's how we've been sharing printers for the DOS programs until now. I'd been hoping to solve 2 problems in one fell swoop:

1. printers need to be placed where there aren't computers such as a print room and central areas

2. printers that are independent of a computer providing it as a shared resource for DOS programs

I knew #1 worked, but was hoping someone could help me figure out #2 as well. Looks like it's just another reason to rewrite those old programs.

dbMark

 

[Rearview]

Assign the printer a static IP address (and a statis gateway and subnet mask). You can give it a more meaningful name, but I have never found this overly useful.

You can do one of two things: Create an HP JetDirect port (or probably a standard TCP/IP port) on your workstations to print directly to the printer (these are installed as a local printer, and work across all user profiles) or install the printer via a HP JetDirect port on a print server, share it, and use "net use" to connect your workstations (users) to the shared printer on the print server.