Member Avatar for The Ticket

I am trying to setup a print server to be used in a remote site from my PC at the host site just to have it ready when I get to the remote site as recommended by my hardware vendor. I have the print server in my hand and I am trying to set it up on my PC and then carry it to a remote site to be used. I used the install wizard disk that came with it and hooked a Genicom 3840(a big dot matrix) printer to it. The print server allows a parallel printer with an RS232 connection to be used in an ethernet environment. My question is: Am I actually assigning a static IP address to the print server itself so that any printer attached to it will work? The drivers for this printer reside on the main server and not on the PC's. I used the default gateway address of the remote site. By using that default gateway for this setup, will this keep me from pinging this print server from my PC at the host site?? This is all going into an AIX operating system(our host server).
Thankx

  • 2 Contributors
  • 1 Reply
  • 418 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by jimlaver

Dani AI

Generated

Brief summary and practical guidance for and : the JetDirect is a network appliance that keeps its own IP and presents the attached printer as a network endpoint. The AIX host must send jobs to that network address and the server-side print queue must use the correct driver for the actual printer model (so ’s point about drivers remains central).

Gateway/subnet behavior and reachability: assigning the JetDirect an address and gateway that belong to the remote site while the device is physically on the host LAN will usually make the device unreachable from the host unless routing to that remote subnet already exists. A device uses its configured subnet mask and gateway to decide whether traffic is local or must be routed; if the assigned address doesn't sit in the host network, pings will fail. Two sane approaches for pre-deployment are: (a) configure a temporary IP that belongs to the host subnet for testing, then reconfigure at the remote site; or (b) leave the JetDirect to obtain an address via DHCP at the remote site and ask the remote admin to reserve the MAC-to-IP mapping so the final static address is predictable.

Recommended step-by-step checklist:

  • Decide whether to preconfigure or configure on-site.
  • If testing at the host site, set an IP/subnet/gateway valid on that LAN, verify no IP conflict, then create the AIX print queue to point at the JetDirect IP (use raw socket or LPD as appropriate) and ensure the Genicom driver is installed on AIX.
  • Verify connectivity with basic tests: ping <print-server-ip> and a raw-port check such as telnet <print-server-ip> 9100.
  • Move to the remote site and either apply the reserved static address or let DHCP provide the reserved lease.

Troubleshooting cautions: confirm the JetDirect model/adapter supports the Genicom's interface (serial vs parallel), avoid duplicate IPs at the remote site (coordinate with remote IT), and check firewalls for printing ports (9100/515). If jobs print incorrectly, re-check the server-side driver/queue protocol rather than the JetDirect itself.

Member Avatar for jimlaver

My question is: Am I actually assigning a static IP address to the print server itself so that any printer attached to it will work?

I believe so, yes. Keep in mind that if you change the printer connected to the server, you must use the new printer's driver or you'll probably have a stack of scrap paper instead of a single document.

I used the default gateway address of the remote site. By using that default gateway for this setup, will this keep me from pinging this print server from my PC at the host site??
Thankx

I'm not sure about this one, but i don't think you'll have problems pinging.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.