Xerox DC-260 Fiery controller unable to ping

[jpat]

My xerox Docucolor 260 bustled controller doesn't connected with router and I am unable to ping it, although the network card as well as router shows the green light.
Try to assigned the static IP address in controller panel still no luck.
Any quick help will be greatly appreciated.

Thanks

[bojans]

Re: Xerox DC-260 Fiery controller unable to ping

Did you put good IP address? It must be in the same range. For example If your printer has address 10.0.0.1 your comp must have 10.0.0.X, only last number is changing. It also must have same subnet mask.
Just a thought.

[jpat]

Re: Xerox DC-260 Fiery controller unable to ping

IP address I have assigned was 192.168.1.9 and gateway was 192.168.1.1
still no sign of connectivity!
Unable to understand this problem, tried restart couple times.... No luck

[bojans]

Re: Xerox DC-260 Fiery controller unable to ping

IP address I have assigned was 192.168.1.9 and gateway was 192.168.1.1
still no sign of connectivity!
Unable to understand this problem, tried restart couple times.... No luck

What's the printer IP adress?

[jpat]

Re: Xerox DC-260 Fiery controller unable to ping

The controllers IP address is 192.168.1.9
Can we add the additional network port card to controlle, linux lilo compatible?

[bojans]

Re: Xerox DC-260 Fiery controller unable to ping

The controllers IP address is 192.168.1.9
Can we add the additional network port card to controlle, linux lilo compatible?

It's simple.
Print configuration.
YOu'll find this:
IP Address: 192.168.1.9
Subnet Mask: 255.255.255.0 (for example) could be other numbers

On your computer set
IP address 192.168.1.10
Subnet Mask: 255.255.255.0 (if it's not this type numbers from configuration)

Ping 192.168.1.9

[jpat]

Re: Xerox DC-260 Fiery controller unable to ping

No luck doing this as well.
somehow the controller is not showing in activity with router.
I have tried dirctly hooking to my desktop but same problem... no pinging.

[rthonpm]

Re: Xerox DC-260 Fiery controller unable to ping

Kind of an obvious question, but are you using a good network cable?

[jpat]

Re: Xerox DC-260 Fiery controller unable to ping

I have tried another cable as well, looks like port on mob is a issue.

[jpat]

Re: Xerox DC-260 Fiery controller unable to ping

Any further help or expert comments from anybody?
Appreciate for your time and suggestions.

Thanks

[ddude]

Re: Xerox DC-260 Fiery controller unable to ping

Use the computer and a crossover cable direct to the printer, with IP addresses within range-

(printer)
IP Address: 192.168.1.9
Subnet Mask: 255.255.255.0 (for example) could be other numbers

On your computer set
IP address 192.168.1.10
Subnet Mask: 255.255.255.0 (if it's not this type numbers from configuration)

ping from computer. This will tell you if the printer nic is working.

[jpat]

Re: Xerox DC-260 Fiery controller unable to ping

I tried exactly how you explained.
Still no luck....
I suspect the network port on motherboard is dead and the IP addresses stuck to that somehow, the new network cards has been picked up by system and shows the green light also but not picking up the new IP addres assigned through the copier control panel.
Please see if anyone has any idea to make that NIC work with the new IP address.

Thanks

[xcopytech]

Re: Xerox DC-260 Fiery controller unable to ping

Did you tried to reload system software to fiery?

[jpat]

Re: Xerox DC-260 Fiery controller unable to ping

I have v.2 disc part 2 only. misplaced the first one.
Is there any reset option for firey software?
Tried factory reset with no luck.

[ddude]

Re: Xerox DC-260 Fiery controller unable to ping

........

but not picking up the new IP addres assigned through the copier control panel.

.......

So you program the new IP address through the control panel, yet when you print out a config page the new address is not shown?


I know from experience that when you are programming a fiery, you must maneuver through a complicated tree of commands in the proper sequence before any selections are preserved-and you must have a valid password in order to change any settings- you may need to look at your fiery command sequence.

Try changing one simple item in the Fiery console, like the printer name, or the DNS, then exit, and print a config page to see if your change was accepted- this will show you that you do have the ability to make changes-

I am sorry if this sounds basic, but your symptoms point to a 'rights issue' or an acceptance problem with the Fiery. Let us know so we can help you-