Need Help ROLAND VERSAWORKS DEVICE NOT FOUND HELP!

[Adam24]

Hi guys stressing out today our PC which held our RIPS etc gave in so instead of replacing the RAM it was cheaper to buy another. I managed to get versaworks from the hard drive and installed it.
We currently have 3 ROLAND printers. I have managed to successfully connect two of our RE-640's
however the XC-540 does not want to connect
The IP Address on our machines are as follows;
RE-640 1 - 169.254.253.030
RE-640 2 - 169.254.253.090
XC-540 169.254.253.060.

These were what they were set on old computer and worked fine.. On the new computer when I try click verify it says "Device not found or status not acquired correctly from the device."
I changed the IP Address end i.e 060. to 010. but to no avail. I changed it a few times to different endings but not done the job. Not great at all with IPS etc so please let me know in more detail what to do also they are all running on a switch circuit.

What I have tried:
On another computer with Versaworks (2 work fine just that 1 again)
Different ethernets.
Different ports on the circuit
Checked all subnet gateways etc
Changed the Protocol on the computer for the IV4 I think it was.

 

[player]

Turn off all anti-virus software.

 

[Adam24]

Turn off all anti-virus software.

Hi Tried that as the computer 2 we tried it on turned everything off on that.
Strange how 2 work perfectly.

 

[Joe House]

Can you ping the XC?

 

[Adam24]

Can you ping the XC?

Sorry how do I do that? Need further guidance step by step sorry not good at all with ips

 

[Joe House]

Sorry how do I do that? Need further guidance step by step sorry not good at all with ips

Depending on your OS - Windows 10, right click on your Windows icon in the lower left corner and select Windows Powershell (Admin) - or previous windows versions, go to the start menu and type CMD in the run window.
When the black box pops up type in "Ping 169.254.253.060" (without the quote marks). You should get one of 3 results:
1: No Reply
2: Reply from (your computers IP Address) unable to connect
or
3: Reply from 169.254.253.060: Bytes = 32 time<1ms TTL=64

And you'll probably get 4 lines of the same or very similar messages. If you get a reply from the printer's IP address, then your computer can talk with your printer and you need to focus on getting the software to communicate with the Printer. If you get option 1 or 2 (or something similar) your computer isn't able to talk with the printer and you need to sharpen you networking protocol skills.

If you are unable to connect still, while in the Command or Powershell window, type in "IPCONFIG" and post what your ethernet adapter IPV4 settings are.

Good Luck,

Joe

 

[Adam24]

Depending on your OS - Windows 10, right click on your Windows icon in the lower left corner and select Windows Powershell (Admin) - or previous windows versions, go to the start menu and type CMD in the run window.
When the black box pops up type in "Ping 169.254.253.060" (without the quote marks). You should get one of 3 results:
1: No Reply
2: Reply from (your computers IP Address) unable to connect
or
3: Reply from 169.254.253.060: Bytes = 32 time<1ms TTL=64

And you'll probably get 4 lines of the same or very similar messages. If you get a reply from the printer's IP address, then your computer can talk with your printer and you need to focus on getting the software to communicate with the Printer. If you get option 1 or 2 (or something similar) your computer isn't able to talk with the printer and you need to sharpen you networking protocol skills.

If you are unable to connect still, while in the Command or Powershell window, type in "IPCONFIG" and post what your ethernet adapter IPV4 settings are.

Good Luck,

Joe

Cheers getting this -

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\Users\user> ping 169.254.253.060

Pinging 169.254.253.48 with 32 bytes of data:
Reply from 169.254.161.106: Destination host unreachable.
Reply from 169.254.161.106: Destination host unreachable.
Reply from 169.254.161.106: Destination host unreachable.
Reply from 169.254.161.106: Destination host unreachable.

Ping statistics for 169.254.253.48:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
PS C:\Users\user>

Seems no comms from printer what so ever.

 

[Adam24]

Depending on your OS - Windows 10, right click on your Windows icon in the lower left corner and select Windows Powershell (Admin) - or previous windows versions, go to the start menu and type CMD in the run window.
When the black box pops up type in "Ping 169.254.253.060" (without the quote marks). You should get one of 3 results:
1: No Reply
2: Reply from (your computers IP Address) unable to connect
or
3: Reply from 169.254.253.060: Bytes = 32 time<1ms TTL=64

And you'll probably get 4 lines of the same or very similar messages. If you get a reply from the printer's IP address, then your computer can talk with your printer and you need to focus on getting the software to communicate with the Printer. If you get option 1 or 2 (or something similar) your computer isn't able to talk with the printer and you need to sharpen you networking protocol skills.

If you are unable to connect still, while in the Command or Powershell window, type in "IPCONFIG" and post what your ethernet adapter IPV4 settings are.

Good Luck,

Joe

IP CONFIG SETTINGS
C:\Users\user>ipconfig

Windows IP Configuration


Ethernet adapter Ethernet 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::dda2:7d2b:7902:a16a%16
Autoconfiguration IPv4 Address. . : 169.254.161.106
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : home
IPv6 Address. . . . . . . . . . . : 2a00:23c4:8121:1500:fcdc:fbe9:7b46:3ee2
IPv6 Address. . . . . . . . . . . : fdaa:bbcc:ddee:0:fcdc:fbe9:7b46:3ee2
Temporary IPv6 Address. . . . . . : 2a00:23c4:8121:1500:9d48:2d9c:883a:a1da
Temporary IPv6 Address. . . . . . : fdaa:bbcc:ddee:0:9d48:2d9c:883a:a1da
Link-local IPv6 Address . . . . . : fe80::fcdc:fbe9:7b46:3ee2%14
IPv4 Address. . . . . . . . . . . : 192.168.1.97
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::ae3b:77ff:fe0c:ca69%14
192.168.1.254

C:\Users\user>

 

[Joe House]

Hmm... I've run into this before. You give the command to ping one address and it tries to ping another.

PS C:\Users\user> ping 169.254.253.060

Pinging 169.254.253.48 with 32 bytes of data:

I would go into the ethernet adapter settings and manually configure the IP address to a completely different range like 10.1.1.100, with the subnet mask set to 255.255.255.0. No gateway is necessary.
Then configure your printers to something like 10.1.1.110, 10.1.1.120 and 10.1.1.130 respectively and make sure that their subnet masks areset to 255.255.255.0 as well.
Make the appropriate changes to your RIP software to match the addresses above. You should be good to go.
If not, the next step would be to replace the switch with a router.

Good luck

 

[Adam24]

Hmm... I've run into this before. You give the command to ping one address and it tries to ping another.


I would go into the ethernet adapter settings and manually configure the IP address to a completely different range like 10.1.1.100, with the subnet mask set to 255.255.255.0. No gateway is necessary.
Then configure your printers to something like 10.1.1.110, 10.1.1.120 and 10.1.1.130 respectively and make sure that their subnet masks areset to 255.255.255.0 as well.
Make the appropriate changes to your RIP software to match the addresses above. You should be good to go.
If not, the next step would be to replace the switch with a router.

Good luck

Perfect this fixed it cheers!!

 

[CSOCSO]

Whatever i tried It did not work for me. I have restarted dhcp client. released and renewed the ip in cmd. I have set up the ip and subnet mask manuall under ipv4.. Nothing helped.
subnet was stuck on 255.255.0.0 and ip was 169.whatever.
I had the computer connected to the modem via the mobo and had the printer connected to the same machine with a usb3-lan adapter. I have internet. That ethernet picked up everything the right way. i swapped cables and the internet was working on the usb3-lan adapter but the printer had the same exact issue when i connected it to the mobo. I was googling for an hour and tried everything i could online and didn't work. I COULD NOT get rid of the 169 ip address. I had enough and connected the printer to my modem / router. It started to work immediately.

I have no clue why. how. So its not the cable. Its not the printer nor the settings on the printer. i don't get it but finally it works.