开云体育

One thing to try, if you have not already, is to turn off auto negotiate in the Ethernet settings.
Doesn't matter much which speed/duplex setting you use but it should be consistent.

Tray


Sent from my Samsung Galaxy Note???, an AT&T LTE smartphonetoritian <toritian@...> wrote:
Has anyone else experience weird network connection problems between Crestron equipment with recent updates?

I have had DM Router issues, where it will show the DM Router as being offline until I reboot the DM and then it pops back up online in the IP Table.

This happened in multiple locations with multiple programs/DMs.

On another site I have CP2E running lights talking to another CP2E and I'm having a hell of a time getting them to talk to each other over an EISC.

A reboot of both will usually connect them up for a while, but then they will stop talking.

One processor is showing a status of "UNKNOWN" and the other shows a connection status of "NO_NETWORK", which I don't remember seeing before.

I gave up using Direct Sockets because they seem broke, but this is just basic Crestron 101 falling apart.





[Non-text portions of this message have been removed]

One thing to try, if you have not already, is to turn off auto negotiate in the Ethernet settings.
Doesn't matter much which speed/duplex setting you use but it should be consistent.

Tray


Sent from my Samsung Galaxy Note???, an AT&T LTE smartphonetoritian <toritian@...> wrote:
Has anyone else experience weird network connection problems between Crestron equipment with recent updates?

I have had DM Router issues, where it will show the DM Router as being offline until I reboot the DM and then it pops back up online in the IP Table.

This happened in multiple locations with multiple programs/DMs.

On another site I have CP2E running lights talking to another CP2E and I'm having a hell of a time getting them to talk to each other over an EISC.

A reboot of both will usually connect them up for a while, but then they will stop talking.

One processor is showing a status of "UNKNOWN" and the other shows a connection status of "NO_NETWORK", which I don't remember seeing before.

I gave up using Direct Sockets because they seem broke, but this is just basic Crestron 101 falling apart.

Good one, forgot about that. I have not had to mess with that setting in a while.

There is other info really needed also. What DM firmare. Are you on your own network or the clients? What else is on the network. If it is multiple system with similar problems, do those systems have the some of the same equipment. It could be a device is just killing the network.

Honestly it sounds like a network loop issue since it will work for a bit and then stop/drop offline, do a reboot and work again. That has been my experience with the older firmware DM's where a DM is connected to another DM. I have not had that issue since the 1 IP address firmware.

--- In Crestron@..., trayschaeffer <trayschaeffer@> wrote:

One thing to try, if you have not already, is to turn off auto negotiate in the Ethernet settings.
Doesn't matter much which speed/duplex setting you use but it should be consistent.

Tray


Sent from my Samsung Galaxy Note???, an AT&T LTE smartphonetoritian <toritian@> wrote:
Has anyone else experience weird network connection problems between Crestron equipment with recent updates?

I have had DM Router issues, where it will show the DM Router as being offline until I reboot the DM and then it pops back up online in the IP Table.

This happened in multiple locations with multiple programs/DMs.

On another site I have CP2E running lights talking to another CP2E and I'm having a hell of a time getting them to talk to each other over an EISC.

A reboot of both will usually connect them up for a while, but then they will stop talking.

One processor is showing a status of "UNKNOWN" and the other shows a connection status of "NO_NETWORK", which I don't remember seeing before.

I gave up using Direct Sockets because they seem broke, but this is just basic Crestron 101 falling apart.





[Non-text portions of this message have been removed]

Has anyone else experience weird network connection problems between Crestron equipment with recent updates?

I have had DM Router issues, where it will show the DM Router as being offline until I reboot the DM and then it pops back up online in the IP Table.

This happened in multiple locations with multiple programs/DMs.

On another site I have CP2E running lights talking to another CP2E and I'm having a hell of a time getting them to talk to each other over an EISC.

A reboot of both will usually connect them up for a while, but then they will stop talking.

One processor is showing a status of "UNKNOWN" and the other shows a connection status of "NO_NETWORK", which I don't remember seeing before.

I gave up using Direct Sockets because they seem broke, but this is just basic Crestron 101 falling apart.

Are you using static IPs in your IP Tables, or hostnames?

--- In Crestron@..., "eagrubbs" <eagrubbs@> wrote:

Good one, forgot about that. I have not had to mess with that setting in a while.

There is other info really needed also. What DM firmare. Are you on your own network or the clients? What else is on the network. If it is multiple system with similar problems, do those systems have the some of the same equipment. It could be a device is just killing the network.

Honestly it sounds like a network loop issue since it will work for a bit and then stop/drop offline, do a reboot and work again. That has been my experience with the older firmware DM's where a DM is connected to another DM. I have not had that issue since the 1 IP address firmware.

--- In Crestron@..., trayschaeffer <trayschaeffer@> wrote:

One thing to try, if you have not already, is to turn off auto negotiate in the Ethernet settings.
Doesn't matter much which speed/duplex setting you use but it should be consistent.

Tray


Sent from my Samsung Galaxy Note???, an AT&T LTE smartphonetoritian <toritian@> wrote:
Has anyone else experience weird network connection problems between Crestron equipment with recent updates?

I have had DM Router issues, where it will show the DM Router as being offline until I reboot the DM and then it pops back up online in the IP Table.

This happened in multiple locations with multiple programs/DMs.

On another site I have CP2E running lights talking to another CP2E and I'm having a hell of a time getting them to talk to each other over an EISC.

A reboot of both will usually connect them up for a while, but then they will stop talking.

One processor is showing a status of "UNKNOWN" and the other shows a connection status of "NO_NETWORK", which I don't remember seeing before.

I gave up using Direct Sockets because they seem broke, but this is just basic Crestron 101 falling apart.





[Non-text portions of this message have been removed]

Just FYI, I just finished fighting the same type of issues. All of the sudden I had the same network problems with multiple, non-connected, systems. Come to find out, there were two main issues. First, I had ADMS's at both locations and both were a major contributor to the problem. I could unplug them and the problems went away, plug them back in and the problems would return. Also, another culprit was the 4.007 firmware update. And, finally, the center point of the problem was a Netflix 8 port gigabit switch. I switched it out for a cisco 16 port gigabit switch and all is well. I still get errors on the 4.007 firmware but they are not killing my systems anymore. By the way, you can get rid of the 4.007 errors by rolling back the firmware to the previous version. I hope something in my babbling will help.

Take Care,
DAVE

--- In Crestron@..., "toritian" <toritian@> wrote:

Has anyone else experience weird network connection problems between Crestron equipment with recent updates?

I have had DM Router issues, where it will show the DM Router as being offline until I reboot the DM and then it pops back up online in the IP Table.

This happened in multiple locations with multiple programs/DMs.

On another site I have CP2E running lights talking to another CP2E and I'm having a hell of a time getting them to talk to each other over an EISC.

A reboot of both will usually connect them up for a while, but then they will stop talking.

One processor is showing a status of "UNKNOWN" and the other shows a connection status of "NO_NETWORK", which I don't remember seeing before.

I gave up using Direct Sockets because they seem broke, but this is just basic Crestron 101 falling apart.

Just FYI, I just finished fighting the same type of issues. All of the sudden I had the same network problems with multiple, non-connected, systems. Come to find out, there were two main issues. First, I had ADMS's at both locations and both were a major contributor to the problem. I could unplug them and the problems went away, plug them back in and the problems would return. Also, another culprit was the 4.007 firmware update. And, finally, the center point of the problem was a Netflix 8 port gigabit switch. I switched it out for a cisco 16 port gigabit switch and all is well. I still get errors on the 4.007 firmware but they are not killing my systems anymore. By the way, you can get rid of the 4.007 errors by rolling back the firmware to the previous version. I hope something in my babbling will help.

Take Care,
DAVE

--- In Crestron@..., "toritian" <toritian@> wrote:

Has anyone else experience weird network connection problems between Crestron equipment with recent updates?

I have had DM Router issues, where it will show the DM Router as being offline until I reboot the DM and then it pops back up online in the IP Table.

This happened in multiple locations with multiple programs/DMs.

On another site I have CP2E running lights talking to another CP2E and I'm having a hell of a time getting them to talk to each other over an EISC.

A reboot of both will usually connect them up for a while, but then they will stop talking.

One processor is showing a status of "UNKNOWN" and the other shows a connection status of "NO_NETWORK", which I don't remember seeing before.

I gave up using Direct Sockets because they seem broke, but this is just basic Crestron 101 falling apart.

Also, I have had similar networking issues with using the LAN's PoE switch to supply PoE power to DMCO-55 cards, when connected, I would intermittently loose connection to CP2E, then disconnect PoE feeds to output cards and it cleared up. Also throughput on the LAN dropped significantly. Using PoE injectors solved the problem.


--- In Crestron@..., "innoventgroup" <innoventgroup@> wrote:

Just FYI, I just finished fighting the same type of issues. All of the sudden I had the same network problems with multiple, non-connected, systems. Come to find out, there were two main issues. First, I had ADMS's at both locations and both were a major contributor to the problem. I could unplug them and the problems went away, plug them back in and the problems would return. Also, another culprit was the 4.007 firmware update. And, finally, the center point of the problem was a Netflix 8 port gigabit switch. I switched it out for a cisco 16 port gigabit switch and all is well. I still get errors on the 4.007 firmware but they are not killing my systems anymore. By the way, you can get rid of the 4.007 errors by rolling back the firmware to the previous version. I hope something in my babbling will help.

Take Care,
DAVE

--- In Crestron@..., "toritian" <toritian@> wrote:

Has anyone else experience weird network connection problems between Crestron equipment with recent updates?

I have had DM Router issues, where it will show the DM Router as being offline until I reboot the DM and then it pops back up online in the IP Table.

This happened in multiple locations with multiple programs/DMs.

On another site I have CP2E running lights talking to another CP2E and I'm having a hell of a time getting them to talk to each other over an EISC.

A reboot of both will usually connect them up for a while, but then they will stop talking.

One processor is showing a status of "UNKNOWN" and the other shows a connection status of "NO_NETWORK", which I don't remember seeing before.

I gave up using Direct Sockets because they seem broke, but this is just basic Crestron 101 falling apart.

We have had the same issues at a clients house with a CP2E talking to a Pro2 and a Pac2mini. We have been working with Crestron engineers on the issue and they sent us a BETA firmware that seems to have fixed the issue. We were running the 4.007.00 fimware on both with the same UNKNOWN in the IP table.

Crestron said the "root of the problem is a network link that is going down and back up very quickly … in very short amount of time. This causes us to overwrite the link-up state with the link down state. We will have a firmware that addresses this tomorrow, so this is an option. We could also put the switch on a UPS if all the Crestron processors are connected to the same switch. This would presumably prevent this short cycling. The FW will be a pre-release and it will take some time for this to work its way through our Full QE (Quality Engineering) testing cycle and become incorporated into a released version. Please first explore adding a UPS to the switch (they can do that right now), but if we need to employ the pre-release FW we can do that when its available later this week."

I would contact support regarding the issue and see if they will give the firmware to try.

Eric
Xen Technology Group, LLC

--- In Crestron@..., "jac777888" <jchelton@> wrote:

Also, I have had similar networking issues with using the LAN's PoE switch to supply PoE power to DMCO-55 cards, when connected, I would intermittently loose connection to CP2E, then disconnect PoE feeds to output cards and it cleared up. Also throughput on the LAN dropped significantly. Using PoE injectors solved the problem.


--- In Crestron@..., "innoventgroup" <innoventgroup@> wrote:

Just FYI, I just finished fighting the same type of issues. All of the sudden I had the same network problems with multiple, non-connected, systems. Come to find out, there were two main issues. First, I had ADMS's at both locations and both were a major contributor to the problem. I could unplug them and the problems went away, plug them back in and the problems would return. Also, another culprit was the 4.007 firmware update. And, finally, the center point of the problem was a Netflix 8 port gigabit switch. I switched it out for a cisco 16 port gigabit switch and all is well. I still get errors on the 4.007 firmware but they are not killing my systems anymore. By the way, you can get rid of the 4.007 errors by rolling back the firmware to the previous version. I hope something in my babbling will help.

Take Care,
DAVE

--- In Crestron@..., "toritian" <toritian@> wrote:

Has anyone else experience weird network connection problems between Crestron equipment with recent updates?

I have had DM Router issues, where it will show the DM Router as being offline until I reboot the DM and then it pops back up online in the IP Table.

This happened in multiple locations with multiple programs/DMs.

On another site I have CP2E running lights talking to another CP2E and I'm having a hell of a time getting them to talk to each other over an EISC.

A reboot of both will usually connect them up for a while, but then they will stop talking.

One processor is showing a status of "UNKNOWN" and the other shows a connection status of "NO_NETWORK", which I don't remember seeing before.

I gave up using Direct Sockets because they seem broke, but this is just basic Crestron 101 falling apart.