Quote:
|
Originally Posted by Gadget  cool - thanks for the ideas, unfortunatly I can cross off most of them:
The subnet mask is a simple 255.255.255.0, and if it was wrong, the cross-cable connection shouldn't work (should it?)
The Gateway should only be used to connect to an external network or internet (and is correct anyway) {... hmmm, need to see if I can access it through the gateway - long shot, but...  nope.}
The network is running on hubs; 10/100 hubs, so the connection shouldn't matter {... but it gives me something else to look at I hadn't thought on  ... actually, you may be onto something...}
It's fixed addresses and I have no idea how to look for the printer's MAC address across the network (I've never had any occasion to even look at it on the printer before) |
Problems like this are usually down to physical or MAC layer stuff, not IP problems.
Definitely worth checking the port status on the switch with the printer attached - that's usually the problem. See if you can force the port speed on the hub to 10MBit. That fixes a problem where the two ends of the link are failing to negotiate a port speed. That's happened to me in the past.
If the port is definitely "up", then chase out the MAC address forwarding table on the switch. Most likely by that time you'll have the problem fixed. BTW If you're on a windoze system, you can look at your ARP cache with "arp -a" from a cmd window (if you weren't aware.)
Good luck.