This laser has no manual and a built in 10 base T ethernet interface in addition to the parallel port interface that (I assume) allows it to act like/be a print server)
The printer’s poorly designed LCD menu offers
TCP-IP on/off - set to on
DHCP -on/-off - set to on
IP address - set to 11.22.33.44
Subnet mask set to 255.255.255.0
Gateway address set to 000.000.000.000
The unit is on a Win 98/Win ME peer to peer network attached to a linksys router/hub that feeds the cable modem internet connection to all PCs and allows the PCs to share files etc across the network. Fairly simple setup.
The printer works perfectly as a parallel port unit but I can’t get the network to recognize it’s existence even if I plug it into the network (via the hub) with a known good cable.
I have my Win 98 TCP-IP drivers enabled. What else needs to be happening for the network to “see” this beast. Any advice appreciated.
You haven’t mentioned the model of laser printer you’re using so I can only give you generic advice.
First of all, you need to set the unit up with an IP address appropriate to your network. Find out your workstation’s IP address by running WINIPCFG. This will tell you your workstation’s IP address (more than likely something in the 192.168.xxx.yyy range) and subnet mask (more than likely 255.255.255.0). Once you’ve determined what subnet your workstation is on, you need to assign the printer with an IP address in the same subnet (eg if your workstation is 192.168.0.10, try setting the printer to 192.168.0.200). This address must be unique (must not already exist on your network). Then set the subnet mask (must be the SAME as your workstation’s subnet mask).
I notice you mention the printer is set for DHCP, and it thinks its IP address is 11.22.33.44. This is highly unlikely unless you really are on the 11.22.33.xxx subnet. Disable DHCP on the printer for the moment. At this stage manually setting the IP address is most likely to work for you.
Once you’ve set the IP address of the printer, save its configuration. It should take the config up straight away, but if it doesn’t, try restarting it.
At this stage, you should be able to establish some sort of communication with the printer. From your workstation, go to a command prompt and try to ping the printer (ping www.xxx.yyy.zzz - where www.xxx.yyy.zzz is the IP address you’ve assigned to the printer). You should get a reply. If you do not, the IP configuration on the printer is either wrong, or its ethernet interface is not working properly. Common problems include incorrectly configured TCP/IP, dodgy cable, a printer that is trying to talk 10MBps on a 100-only network… things of that nature. If there is a link light on the printer’s ethernet interface, make sure it is on (thereby indicating physical connectivity). If it’s off, there is a problem either with the interface itself, the cable, the hub, or the interaction between them all.
The second part of the problem is perhaps a little more challenging.
In a peer-to-peer environment such as the one you describe, it’s been my experience that the workstations need extra software loaded on them in order to talk to the printer (usually a bastardisation of LPR/LPD protocol). At this stage knowing the make and model of the printer would be of use as you would more than likely find said software on the manufacturer’s web site.
Anyway mate, get the IP configuration sorted, make sure you can ping the printer, and get back to me with the printer’s make and model (or find the software yourself). I’m happy to help you out via email if you like - max@maxxxie.net.
Another thought if you just can’t get it connected to the network:
(I’m no network expert, but this worked for me)
You might be able to have it print just fine from any computer WITHOUT hooking it up to the hub. You will be wasting the built-in ethernet connection the printer has, but if it works, who cares?
Connect the printer directly to one of the computers on the network through the normal printer port or USB connection, installed as a normal local printer.
Once you have done this (and it works from that computer), install the printer driver on a different computer also connected to the network. Somewhere in the process you can specify if the printer is a local or a network printer. Choose network printer, of course, and then find the printer by going to Network Neighborhood, then the computer the printer is connected to, then choose the printer.
If this works, you’ll then have to install the printer driver and go through the same process for each computer connected to the network.
I use this currently for a non-network enabled printer, and it works just fine. This method does not work for all printers (I’m assuming that it will for any newer printer, but I could be wrong), and I don’t know if you sacrifice anything as far as speed or reliability, etc., but if you can’t get it to work through the hub this may be an alternative.
Yep, totally agree with maxxxie, and a good call I must say. Make sure IP is working, get a ping, then get the specific software called for to run the (you are correct here) embedded print server built in to your printer.
But, um, your IP address seems to be the problem, that netblock, according to whois.arin.net, is assigned to:
DoD Intel Information Systems (NET-DODIIS)
Defense Intelligence Agency
Washington, DC 20301
US
I am sorry if that seems alarmist, and I agree with richardb, you could set it as a shared local printer. I realize this is a totally different question, but who in the wide wide world of sports sets their default IP range to the DOD INTEL INFORMATION SYSTEMS netblock???
I’d go with the sharing option that richardb described, except that you only need the drivers to set up the host machine; once the printer is functioning fine as a local printer, you share it, then on any of the workstations that you want to be able to print from, browse the Network Neighborhood, find the printer and right-click then select ‘install’ - Windows will yank the drivers across the network from the host machine.
(NB: this is also a good way of moving a local printer from one machine to another if you can’t find the driver disk).
Just thought I’d post a quick followup to describe the pros/cons of sharing vs using the internal print server… (mostly because I just can’t keep my mouth shut and I need to have the last word goddamit!!! )
Sharing:
Advantages: allows you to “network” the printer without having to tool around getting the ethernet interface working. Also (as mentioned by mangetout) allows you to install print drivers directly from the “server”.
Disadvantages: depending on the quality of the print driver, this can impact on the “server” performance when spooling print jobs. Also, means you have to have that particular PC on anytime you want to print something. This is a minor annoyance.
Built-in ethernet:
Advantages: Spooling of print jobs is done locally then spat out to the print server. There is no “server” - no other PC needs to be switched on just to facilitate printing. Also, depending on the complexity of your network (not a factor in this case from what I’ve read) - allows non-windows/non-SMB clients to print to the printer.
Disadvantages: Can be a pain in the butt to configure, needs special software (as mentioned before). Difficult to stop print jobs that have been spooled off to the print server.
Thank you all and especially Maxxxie, your clear instructions did the trick. I DL’d the appropriate print manager software and we’re in business.
RE the 11.22.33.44 address that’s what our tech used as a “fill in the blanks” address when the unit was previously on an NT server he set up from scratch. I’ll have to tell him what it really means.
