0

Trying to set up a Lexmark C543dn laser printer onto our office wired network.

Our office is around 60 computers, all connected to a server, each PC has a static IP. (Some IP's aren't allowed full web access, just certain sites).

First worry is that on plugging in the ethernet the green lights don't illuminate. I can print directly from a computer if using USB.

I'm trying use a manual IP and netmask/gateway. (10.0.0.103, 255.255.0.0, 10.0.0.1)

The network report page you can print out states: Status: Not connected

Checked already: Ethernet cable isn't damaged Ethernet port is active I've tried installing drivers onto PC and connecting USB, this works fine, but obviously the idea is to have it on the network. Did a complete reset of printer.

Just completely out of ideas now, so if anyone can get this sorted

  • 1
    What exactly are you connecting the printer to? (Make and model, if possible. I'm thinking MDI/MDIX mismatch.) – David Schwartz Aug 20 '12 at 09:48
  • Draytek Vigor 2920 router, with server stacks. All the ports around the building connect to these server stacks, which then use the draytek router. – Alexander Wigmore Aug 20 '12 at 09:56
  • 1
    So it's connected to one of its 4 LAN ports? That seems an odd waste of a Gigabit port on the gateway device for a network with 60 computers! – David Schwartz Aug 20 '12 at 09:58
  • Sorry no - the printer is connected to one of the wall ports - which is wired to the server. – Alexander Wigmore Aug 20 '12 at 09:59
  • 1
    Wired to the *server*? Why are you connecting a network printer to a server? It should be connected to the network. (Or am I misunderstanding you? What do you mean by a "server stack"?) What exactly is the printer connected to? (Make and model if possible.) – David Schwartz Aug 20 '12 at 10:00
  • That's just my jargon... you know it's just those standard ethernet ports that are on the walls of offices, which yes, I suppose I mean network. – Alexander Wigmore Aug 20 '12 at 10:03
  • 1
    Okay, right, so what does that port connect to? (Make and model, if possible.) I'm thinking [MDI/MDIX](http://en.wikipedia.org/wiki/Medium_Dependent_Interface#MDI_vs._MDIX) mismatch. – David Schwartz Aug 20 '12 at 10:03
  • 1
    *That's just my jargon... you know it's just those standard ethernet ports that are on the walls of offices, which yes, I suppose I mean network.* - and those ports are wired to..... what? – Rob Moir Aug 20 '12 at 12:29

2 Answers2

1

It seems to me that the green light should light whether or not you actually obtain a valid IP address or whatever. So it sounds like the media is not connected. Could it be that you have a 100mb card plugged into a 10mb switch or vice-versa? Could it be that you need/do not need an ethernet crossover cable?

That's where I'd start looking.

Looking at the user's manual for that printer, there are instructions to software-activate the wired network port. Have you done that?

HopelessN00b
  • 53,385
  • 32
  • 133
  • 208
Bob
  • 597
  • 2
  • 8
  • 1
    Looking at the user's manual for that printer, there are instructions to software-activate the wired network port. Have you done that? http://images.lexmark.com/publications/pdfs/2007/c54x/html/en/index.html – Bob Aug 20 '12 at 12:16
  • I have tried the manual software setup, but the software can never see the printer, as I guess it's not finding the network at all. – Alexander Wigmore Aug 20 '12 at 13:09
  • 2
    It appears to me that you're supposed to connect via USB, then turn on the wired network port then proceed from there... – Bob Aug 20 '12 at 18:08
  • 1
    @Bob: Where do you see any documented method to turn on the wired network port via USB? The directions clearly state to connect the printer to the wired network and then tell the PC software to look on the network for the printer. There's no previous step to configure the printer. (Although setting up by USB is the procedure to configure for wireless printing.) – David Schwartz Aug 21 '12 at 01:35
0

It's fixed now - turns out the port was dead, even though our IP based phones powered up through it (which is usually the test we do to see if a port is active) it turns out that, that port wasn't fully networked between everything.

Sorry for the hassle - and thanks for the help guys :).