Rland VP-540 strange ethernet cable problem

Have you tried a different ethernet cable?

 

Check the following IP settings: VP-540 through the panel menu, setting for printer in Versaworks, and the computer network card. You can check the computer IP setting 2 ways - CMD - ipconfig, or in the network properties for the network card through the control panel. If your IP configuration in the network card is set to Automatic, it's possible your system has changed its default IP and no longer matches the printer and Versaworks. CMD - ipconfig will let you know the settings you will need to update in the printer and Versaworks. Hopefully, you just have a mismatch here...

 

good job jim

monomo
your router probably "gave away" your ip address

you can download "advanced ip scanner" and see what the ip's of all the devices on your network are. (40 have over 40 on ours, so we need the program to keep track

you will probably see that something else has your ip, and is returning that ping

when you see the ip of your roland, you will have to change the ip in versaworks to match the current configuration

 

Roland VP series printers have known issue for Ethernet on the mainboard. Most likely you will be needing a new mainboard which is discontinued. We did put one in a few months back. It has to be special ordered. I am sure other people have talked about this issue.

 

Yeah I have same doubt for your mainboard sadly.

 

Thanks! That's about the limit of my networking expertise though... I like AngryIP as a sniffer also...

Let's eliminate the obvious before we start replacing hardware...

 

premier colour & jim

i am not certain that a few of these condemned boards have not been misdiagnosed
(it can be difficult to talk an end user through network diagnosis)



i will certainly volunteer an hour of my time with OP to be sure we can't pull this one out.

there are many other things that give this type of issue. do to my mis-spent youth i have over 30 years experience diasnosing this type of issue on many types of equipment

i have learned a lot from signs101 and like to give back where i can

if monomo messages me, i can give him my cell or we can do a teamviewer if he is comfortable with that

i just hate to see a roland die before it's time & will be happy to work with any of our members just to be sure it truly is a bad board

both you know more about these machines than i ever will, but when we wonder into the area where i am comfortable, i like to offer help

 

You're on! I will help where I can. Since we think he was able to ping the printer, I'm assuming from the command prompt, then I'm going to assume the mainboard is ok. So let's see after the IP addresses are confirmed to be correct.

 

jim,
i am not sure the device he is pinging is the printer
possible something else got that ip

that is one of the things i want to verify

routers can be stupid stubborn devices

we fight thissame battle with zebra label printers all the time

they use the hp manufactured print servers that use the same chip as many of the rolands

i just. like to be sure, before we condemn a machine, it has to be a major expense for anyone, replacing the printer

 

Agreed. I will watch this thread...

 

What happens if you power up the printer with the network cable plugged into a different computer? The other computer doesn't need to have Versaworks. Just want to eliminate the computer as the cause of the power up issue first.

 

It's starting to look like you have an issue with the network section of the mainboard. Let's get Netsol to chime in on this also...

 

Check the contacts on the network connector on the mainboard and make sure they are even and not bent or damaged...

 

monomo,
when you are connected directly with a cable, printer to pc, can you still ping?

i just want to be sure another device isn't returning the ping.

what are the ip, subnet & gateway of the pc?

example

192.168.1.103. ip
255.255.255.0. subnet
192.168.1.1. gateway

also, how many devices are connect to your network? (cell phones, tablets, printers)

just want to be thorough, before you drop a couple grand (it certainly is sounding more like a bad component on the system board)