ClobalCache WF2IR connection problem

controlfreakberlin All Messages By This Member #181011 I want to establish a connection between a Crestron control processor and a WF2IR unit. Everything is set up and the TCP connection works when I use either a terminal client on my PC or a CommandFusion UI on my mobile to connect to the WF2IR but I can't connect to the WF2IR with the Crestron system as a TCP client on port 4998. Do you have any ideas what else I could try? Even all other devices in the network communicate with each other without problems (Crestron<->PC, Crestron<->CommandFusionDevice...) so I doubt it's a network problem... Even checked it with a second processor and a plain SimpleWindows programm with just the TCP client in it... Thanks in advance! Markus
Chip #181043 Have you connected to your processor with the Toolbox Command Line tool and tried pinging the box from your processor - just to be sure they can "see" each other? What happens when you try to connect to the IP & Port with a TCP/IP Client symbol? What values does the analog status output of the symbol change to after enabling the symbol? - Chip toggle quoted message Show quoted text --- In Crestron@..., "controlfreakberlin" <markusdvorak@...> wrote: I want to establish a connection between a Crestron control processor and a WF2IR unit. Everything is set up and the TCP connection works when I use either a terminal client on my PC or a CommandFusion UI on my mobile to connect to the WF2IR but I can't connect to the WF2IR with the Crestron system as a TCP client on port 4998. Do you have any ideas what else I could try? Even all other devices in the network communicate with each other without problems (Crestron<->PC, Crestron<->CommandFusionDevice...) so I doubt it's a network problem... Even checked it with a second processor and a plain SimpleWindows programm with just the TCP client in it... Thanks in advance! Markus
controlfreakberlin All Messages By This Member #181052 Thanx Chip! You're right: the QM-RMC couldn't ping the WF2IR. I checked a different Wifi router (linksys WRT54GL) and the connection worked! Back on the original router it worked to. So I don't really know what the caused/solved the problem but your idea to blame the network was right... toggle quoted message Show quoted text --- In Crestron@..., "Chip" <cfm@...> wrote: Have you connected to your processor with the Toolbox Command Line tool and tried pinging the box from your processor - just to be sure they can "see" each other? What happens when you try to connect to the IP & Port with a TCP/IP Client symbol? What values does the analog status output of the symbol change to after enabling the symbol? - Chip --- In Crestron@..., "controlfreakberlin" <markusdvorak@> wrote: I want to establish a connection between a Crestron control processor and a WF2IR unit. Everything is set up and the TCP connection works when I use either a terminal client on my PC or a CommandFusion UI on my mobile to connect to the WF2IR but I can't connect to the WF2IR with the Crestron system as a TCP client on port 4998. Do you have any ideas what else I could try? Even all other devices in the network communicate with each other without problems (Crestron<->PC, Crestron<->CommandFusionDevice...) so I doubt it's a network problem... Even checked it with a second processor and a plain SimpleWindows programm with just the TCP client in it... Thanks in advance! Markus
kaybee302 All Messages By This Member #181053 Make sure you have it's IP address listed in the tcpip client. That always gets me. I'm sure you already checked that. And I think you can change the port to something else on the global cache side just to try it. Although the default has always been fine. Is there a firewall in the way? Client isolation on your access point enabled? Sorry just throwing out ideas. Nick Sent from my eMail. toggle quoted message Show quoted text On Jun 17, 2013, at 7:19 AM, controlfreakberlin <markusdvorak@...> wrote: I want to establish a connection between a Crestron control processor and a WF2IR unit. Everything is set up and the TCP connection works when I use either a terminal client on my PC or a CommandFusion UI on my mobile to connect to the WF2IR but I can't connect to the WF2IR with the Crestron system as a TCP client on port 4998. Do you have any ideas what else I could try? Even all other devices in the network communicate with each other without problems (Crestron<->PC, Crestron<->CommandFusionDevice...) so I doubt it's a network problem... Even checked it with a second processor and a plain SimpleWindows programm with just the TCP client in it... Thanks in advance! Markus [Non-text portions of this message have been removed]
Jeremy Weatherford All Messages By This Member #181060 I believe the GlobalCache wireless devices are 802.11b, which is a dying breed and may not be supported by newer wireless routers unless you enable 11b compatibility (which slows down 11g). On Tue, Jun 18, 2013 at 4:03 AM, controlfreakberlin < markusdvorak@...> wrote: Thanx Chip! You're right: the QM-RMC couldn't ping the WF2IR. I checked a different Wifi router (linksys WRT54GL) and the connection worked! Back on the original router it worked to. So I don't really know what the caused/solved the problem but your idea to blame the network was right... --- In Crestron@..., "Chip" <cfm@...> wrote: Have you connected to your processor with the Toolbox Command Line tool and tried pinging the box from your processor - just to be sure they can "see" each other? What happens when you try to connect to the IP & Port with a TCP/IP Client symbol? What values does the analog status output of the symbol change to after enabling the symbol? - Chip --- In Crestron@..., "controlfreakberlin" <markusdvorak@> wrote: I want to establish a connection between a Crestron control processor and a WF2IR unit. Everything is set up and the TCP connection works when I use either a terminal client on my PC or a CommandFusion UI on my mobile to connect to the WF2IR but I can't connect to the WF2IR with the Crestron system as a TCP client on port 4998. Do you have any ideas what else I could try? Even all other devices in the network communicate with each other without problems (Crestron<->PC, Crestron<->CommandFusionDevice...) so I doubt it's a network problem... Even checked it with a second processor and a plain SimpleWindows programm with just the TCP client in it... Thanks in advance! Markus ------------------------------------ Check out the Files area for useful modules, documents, and drivers. A contact list of Crestron dealers and programmers can be found in the Database area. Yahoo! Groups Links -- Jeremy Weatherford
George Sakellaris All Messages By This Member #187392 I am confronting these same issues. What were your end results and recommendations? Thanks, ? ---In Crestron@..., <crestron@...> wrote: Thanx Chip! You're right: the QM-RMC couldn't ping the WF2IR. I checked a different Wifi router (linksys WRT54GL) and the connection worked! Back on the original router it worked to. So I don't really know what the caused/solved the problem but your idea to blame the network was right... toggle quoted message Show quoted text --- In Crestron@..., "Chip" <cfm@...> wrote: > > > Have you connected to your processor with the Toolbox Command Line tool and tried pinging the box from your processor - just to be sure they can "see" each other? > > What happens when you try to connect to the IP & Port with a TCP/IP Client symbol? What values does the analog status output of the symbol change to after enabling the symbol? > > - Chip > > > --- In Crestron@..., "controlfreakberlin" <markusdvorak@> wrote: > > > > I want to establish a connection between a Crestron control processor and a WF2IR unit. Everything is set up and the TCP connection works when I use either a terminal client on my PC or a CommandFusion UI on my mobile to connect to the WF2IR but I can't connect to the WF2IR with the Crestron system as a TCP client on port 4998. Do you have any ideas what else I could try? Even all other devices in the network communicate with each other without problems (Crestron<->PC, Crestron<->CommandFusionDevice...) so I doubt it's a network problem... > > > > Even checked it with a second processor and a plain SimpleWindows programm with just the TCP client in it... > > > > Thanks in advance! > > Markus > > >

Previous Topic Next Topic

开云体育

ClobalCache WF2IR connection problem