One other thing to note - if possible, FFCore should have a static IP address. If you use DHCP and the lease expires then you will see problems with connectivity to the DFEs. You would recover from those via reboot. That may also by why connectivity is suddenly restored after install.
In most cases DHCP is not a problem since leases for a server that's always available on the network would not expire. However, it is recommended that you use a static IP address to be on the safe side.
I have installed the upgrade 188.8.131.52 on two FF Core 184.108.40.206.
After reboot impossible to connect IPP Print server and Fiery.
I have reinstalled 220.127.116.11 under the 18.104.22.168 (without error message).
After reboot I have reconnect all IPP machines.
My license is always 22.214.171.124.
I think there is a bug with IPP with 126.96.36.199 version....
I'm pre sale analyste from France and I get exactly the same difficulties.
I have reinstall FFCore on a new installation Windows 7 with MS SQL and I get the same problem.
I can connect to printers (iGen150 and DC260) with the IP address in the web browser without problem.
My colleague can connect to the same printers without problem and has the same OS and FFCore configuration.
If you have solution to that, it's welcome.
Trying to add a D110 FFPS Ver 9.0 90.B4.22B.86
Also tried a EFI Print Server connected to a 570 - Command WS vers 188.8.131.52
Both give the same error
Unable to establish connection with the printer.
Either the printer is not responding or the DNS name or IP address is invalid.
Error encountered connection to the device specified.
Verifiy your device is online and able to accept internet and network connections.
Could it be something with the license? Im using a Xerox ionternal license
I am having the same problem with a new V4.0 install in our demo room.
SNMP is running on the FFPS - I can ping the FFPS using the DNS name and IP.
Any suggestions? It's tough to demo when it doesn't work. TiA
Just to close this out... It must have been some sort of network issue (maybe a router on our network) as all of a sudden, things started working again.
Have you tried to use DNS name of the printer?
I use that on my FreeFlow printservers without any problems.